Feature Request for Bluetooth "Camera Control Protocol"

Ask software engineering and SDK questions for developers working on Mac OS X, Windows or Linux.
  • Author
  • Message
Offline

MarcusWolschon

  • Posts: 576
  • Joined: Sun Apr 14, 2013 6:59 pm

Feature Request for Bluetooth "Camera Control Protocol"

PostWed Nov 14, 2018 7:13 am

The Bluetooth API to the BMPCC4K and URSA Mini Pro has a lot of values to set but no way to ask what options this particular camera supports.
The only way to limit the selection is to detect the name of the camera-model and to hard-code the options.
But
  • For hard-coding the camera model, the API specification does not list the exact strings each camera identifies itself with. Currently only the URSA Mini Pro is given as an example.
  • For the supported Codecs this approach only works until the BMPCC4K gets support for BM-Raw via an update, since you can not ask the camera for it's firmware-version. (Only for the version of the Bluetooth protocol but the values and differences for these are not documented or api specifications for older versions linked.)
  • You can set the focal length in mm but not ask what the maximum focal length of the current lens is
  • You can not ask if the current lens supports power-zoom at all (only 2 Panasonic lenses have this feature. 14-45PZ and 45-175PZ)
  • The available resolutions and frame-rates obviously come to mind
  • but also if a second card-slow exists and should thus be presented for an independent selection of recording-media
  • Should SSD-drive be offered as a recording-media to choose?
With that a bluetooth app could be made so that it "just works" out of the box with any newly released camera and firmware update. (Any value written to 1.01[3] seems to be completely ignored on the BMPCC4K at the moment)

Also:
  • Metadata access via Bluetooth exists but is not documented yet
  • The BMPCC4K seems to broadcast a lot of Group 9 and Group>10 messages that are not documented
  • Knowing the remaining storage capacity on the loaded recording media would be great
  • Documenting if it makes a difference to subscribe for a notify or for an indication for a service would prevent a lot of headache
  • Also documenting the descriptors and not just the characteristics could make the API easier to implement
  • Document for the Realtime-clock what framerate is to be used for the "FF" part of the time. (in the case of M-rates and off-speed this is not made clear)
Last edited by MarcusWolschon on Thu Nov 22, 2018 5:03 pm, edited 1 time in total.
Offline

MarcusWolschon

  • Posts: 576
  • Joined: Sun Apr 14, 2013 6:59 pm

Re: Feature Request for Bluetooth "Camera Control Protocol"

PostThu Nov 22, 2018 12:48 pm

List updated. 10.1[3] and [4] are currently ignored and no read or write access to metadata is specified.

Return to Software Developers

Who is online

Users browsing this forum: Cameron Nichols and 2 guests