Protocols

Diagnostics methods for cameras.

A camera authentication context represents a request for authentication from the camera. Responses are submitted via this context object.

A non-fatal connection warning.

The catch-all protocol for a camera object in CascableCore. Functionality is broken down into sub-protocols:

• CBLCameraCore for core functionality, such as connection/disconnection, supported functionality, etc.
• CBLCameraLiveView for operations involving live view streaming.
• CBLCameraFocusAndShutter for operations involving shooting images.
• CBLCameraProperties for operations involving getting and setting camera settings/properties.
• CBLCameraFileSystem for operations involving accessing the camera’s file system.
• CBLCameraVideoRecording for operations involving video recording.

Camera connection, disconnection and status methods.

Camera live view methods.

Camera property methods.

Camera filesystem methods.

Camera focus and shutter methods.

A video timer value. Only valid during video recording.

Video recording methods.

Camera discovery delegate methods.

The discovery service’s delegate protocol. Typically, this should not be interfered with.

A camera discovery service represents a camera that has been found on the network, but has not been connected to. A meta-camera, if you will.

A camera-initiated transfer is a request from a camera to transfer an image file (or at least, a representation of one such as a preview) to the connected host. This typically happens soon after a shot is taken, and can allow the previewing and transferring of images even if the camera currently doesn’t allow access to its storage.

Camera-initiated transfers can be time-sensitive as the camera moves on to newer images or flushes buffers — they should be dealt with expediently.

In some cases, the camera-initiated transfer to the host may be the only destination for an image. Commonly referred to as “tethered shooting” (or at least a variant of it), the camera might not attempt (or not be able to) save the image to its own storage. If this is the case, not correctly handling a camera-initiated transfer will case data loss. Check the -isOnlyDestinationForImage property — if that returns YES, not transferring and saving the original representation of the image will cause it to be lost.

The result of a camera-initiated transfer.

Result objects are stored entirely locally, and as such are not under the time pressure that the intial camera- initiated transfer object is. However, they can be fairly resource heavy (especially when the transfer is of a RAW image) so it’s recommended that they are dealt with reasonably quickly.

How this object manages its resources is an implementation detail, and any buffers of cache files it creates will be cleaned up when the object is deallocated. To take ownership of the transfer result, use the appropriate methods to extract representations into RAM or to disk.

Represents an autofocus area in a camera’s focus aspect. Typically rendered as a rectangle on top of the live view image.

Represents a single frame of a streaming live view image, along with any associated metadata.

Use the CBLCameraManualDiscovery object when you need to connect to a camera in situations where using automatic discovery protocols is neither available or desired. Typically, this is paired with user interface asking the user for the IP address and manufacturer of their camera.

Note that manual discovery is entirely separate from the automatic discovery provided by CBLCameraDiscovery.

An object for managing property value change notifications. When you add an observer to a property, store the returned token somewhere in order to keep the observation alive. To remove the observation, you can simply remove all strong references to its token, or explicitly call invalidate on it.

An object representing the values for a property on the camera.

A property that exposes its values as universal exposure values.

A property that exposes its values as universal video format description values.

A property that exposes its values as universal live view zoom level values.

A property value. This could either be the current value of a property, or something in the list of values that can be set.

A property value that exposes its values as universal exposure values.

A property value that represents a video format description.

A property value that represents a live view zoom level.

This protocol defines the protocol expected by CascableCore when loading your plugin via the information found in the plugin’s Info.plist keys.

Implement the CBLCoreCameraDiscoveryProvider protocol in order to provide custom cameras and camera discovery to CascableCore. You can then register your camera provider with CascableCore in the plugin entrypoint.

Implement the CBLCoreCameraManualDiscoveryProvider protocol in order to provide direct connections to your cameras via CascableCore based on user input (i.e., “connect to the camera at 192.168.1.46”). You can then register your manual discovery provider with CascableCore in the plugin entrypoint.

Methods to register your plugin with CascableCore.

Methods to deliver camera discovery changes to CascableCore.

Information about a connected camera.

Represents a file storage container in a camera, such as an SD card.

Represents a folder on a camera’s storage device.

An object containing video-specific metadata.

A filesystem item represents a file or folder on the camera’s storage.

Represents an autofocus state of the camera.

Represents an individual focus point.