Camera Control: status and metadata command categories

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

redfield

  • Posts: 2
  • Joined: Sun Aug 18, 2019 3:57 pm
  • Real Name: Evgeniy Skuridin

Camera Control: status and metadata command categories

PostSun Sep 08, 2019 12:32 pm

Hi there! As a hobby project I'm writing an application to control Blackmagic cameras from a browser using bluetooth API. I noticed that categories 9 (status) and 12 (meta data) aren't documented, at least officially.

Is it because you don't want third party developers to use those APIs or it's not stable enough? I wandering if I should invest my time writing code around undocumented APIs. Could you help me with clarifying this, please?

Cheers!
Offline

MarcusWolschon

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

Re: Camera Control: status and metadata command categories

PostSat Sep 21, 2019 9:21 pm

Sadly there is quite a lot that is not specified and also a lot that is plain missing from the protocol altogether.

For example there is no version of the spec yet that contains the values to send to set the DCI 4K or any higher resolution (and no BMPCC4K firmware that supports DCI 4K on Bluetooth yet).

Or a list of exact values that UUID: 2A24 "Camera Model" will return.

And no way (it's not unspecified, it's missing) to find out what the connected camera supports
or at least what firmware version the camera has (so you could at least maintain a list of each camera and firmware and what resolutions, framerates, codecs,.. it supports with great effort. Especially for cameras you don't have.)

Return to Software Developers

Who is online

Users browsing this forum: No registered users and 3 guests