Edit Braw metadata?

Hi,

Is it possible to edit the metadata on a Braw file? I have to change the camera # and the clip name ID in the metadata for future relinking for the conform on a 13 multicam shoot.

Any hints?

Thanks!

It is in theory, but I'm not sure there are any off the shelf tools available currently that do it.

PM me, I can maybe help.

[CaptainHook]

In general you override metadata by creating/editing a sidecar file. However, camera ID cannot be overridden but camera number can.

Is there a list somewhere of all the metadata keys that currently can be overridden? It would be very neat if any and all keys could be set in sidecar and also new metadata key-value pairs injected, it could open up some interesting workflows for softwares that can do something with all metadata.

[CaptainHook]

You currently can set any metadata key you want in the sidecar, but there isn't currently a list public of what all the possible keys are. The most common ones you want have specific methods for setting/validating the values already. And there are some that would never be allowed to be overridden as it would cause decoding issues (wrong camera type etc) but we could look at adding the full list that is allowed to be overridden to the manual in the future.

Of course you can also use the metadata iterator in the SDK to get a list of all currently set metadata for a particular clip which is useful for showing metadata info UI lists etc, but could also be used to get the key names for overriding them in processing and/or entering into a sidecar. As mentioned though, many have preferred methods for doing this that provide you valid ranges/lists etc.

Thanks, I asked just because of these exceptions of what are not allowed to change (or vice versa).

As I understand it, injecting new keys that don’t exist in braw file isn’t possible and only overrides work? Is it something you plan to add later down the road?

[CaptainHook]

You can inject "keys" that may not be in the clip/file as long as they are already supported by the SDK/Blackmagic RAW in general. For instance if the user left some slate metadata blank on the camera like director, production name, camera operator, etc and it didn't get written to a file/clip you could add it to a sidecar later so that it shows in Resolve or whatever app.

But if you mean adding "custom" metadata we don't support that at the moment, no. How would you make use of it? It would require changes in Resolve too I think to be useful there as it currently only uses pre-defined metadata keys AFAIK.

But if you mean adding "custom" metadata we don't support that at the moment, no. How would you make use of it? It would require changes in Resolve too I think to be useful there as it currently only uses pre-defined metadata keys AFAIK.

This is what I meant, yes. For example there could be data that is stored during shoot but not in camera (because adding them in-camera takes time, logging happens somewhere else or there just isn't suitable keys available by default) or come from other sources, that could be merged into braw files later down the road either manually or in some automated way (from production management software etc) by creating sidecar files. It would create an application-independent way to transfer this metadata together with braw files and make it available anywhere where braw meta reading is implemented. If Resolve only reads a hardcoded set of metadata keys it is a bit limited implementation imho, why not read all keys that metadata iterator gives...

You can inject "keys" that may not be in the clip/file as long as they are already supported by the SDK/Blackmagic RAW in general. For instance if the user left some slate metadata blank on the camera like director, production name, camera operator, etc and it didn't get written to a file/clip you could add it to a sidecar later so that it shows in Resolve or whatever app.
.

It's exactly what I need to do. Just changing the CAMERA #

Can you give an example?


I've generate a .sidecar from ' update sidecar ' in COLOR Camera Raw
But wondering how to add the Key. Also, if I had a key and do an 'update sidecar' I'm assuming that will delete the new KEY?

Thanks for your help!
I've try

Code: Select all

{

"camera_number": "A",
}


But i doesn't work.

Code: Select all

{
   "tone_curve_contrast": 1.000000,
   "tone_curve_saturation": 1.000000,
   "tone_curve_midpoint": 0.409008,
   "tone_curve_highlights": 1.000000,
   "tone_curve_shadows": 1.000000,
   "tone_curve_black_level": 0.000000,
   "tone_curve_white_level": 1.000000,
   "tone_curve_video_black_level": 0,
   "highlight_recovery": 0,
   "post_3dlut_mode": "Disabled",
   "viewing_gamma": "Blackmagic Design Film",
   "viewing_gamut": "Blackmagic Design",
   "viewing_bmdgen": 4,
   "gamut_compression_enable": 0,
   "exposure": {
      "15:32:00:01": 0.000000
   },
   "iso": {
      "15:32:00:01": 1250
   },
   "white_balance_kelvin": {
      "15:32:00:01": 3500
   },
   "white_balance_tint": {
      "15:32:00:01": 0
   }
}

[CaptainHook]

Resolve will cache metadata in a project so you have to completely remove the file/clip from your media pool and re-import. Sometimes I've found I have to close/re-open the project or restart Resolve. The easiest way is to create a new project and import the clips after modifying the sidecar - have you tried that?

Resolve will cache metadata in a project so you have to completely remove the file/clip from your media pool and re-import. Sometimes I've found I have to close/re-open the project or restart Resolve. The easiest way is to create a new project and import the clips after modifying the sidecar - have you tried that?

Yes, I tried, but unfortunately it doesn't work.

Code: Select all

{
   "tone_curve_contrast": 1.000000,
   "tone_curve_saturation": 1.000000,
   "tone_curve_midpoint": 0.409008,
   "tone_curve_highlights": 1.000000,
   "tone_curve_shadows": 1.000000,
   "tone_curve_black_level": 0.000000,
   "tone_curve_white_level": 1.000000,
   "tone_curve_video_black_level": 0,
   "highlight_recovery": 0,
   "post_3dlut_mode": "Disabled",
   "viewing_gamma": "Blackmagic Design Film",
   "viewing_gamut": "Blackmagic Design",
   "viewing_bmdgen": 4,
   "gamut_compression_enable": 0,
   "exposure": {
      "15:32:00:01": 0.000000
   },
   "iso": {
      "15:32:00:01": 1250
   }

   "camera_number": "A"

}


[CaptainHook]

You need a comma after each metadata value to seperate before the next key and there's one missing after the ISO before the camera number. I would also move the camera number higher up or put it at the top so its with the other per clip metadata and keep all the per frame metadata like exposure/ISO etc together after it - just as a general rule to make the file easier to read for people.

I have a bit different question though: is it somehow possible to discover which processing parameters are overridden in sidecar without explicitly parsing the sidecar file myself? I'd like to try an idea with disabling UI knobs for those parameters and opening others to make sure some things are kept as I want and others can be manipulated by user.

Edit: at first I had problem with setting camera_number key from sidecar but it works as expected, I had an error in my own stuff, as usual

[CaptainHook]

I have a bit different question though: is it somehow possible to discover which processing parameters are overridden in sidecar without explicitly parsing the sidecar file myself? I'd like to try an idea with disabling UI knobs for those parameters and opening others to make sure some things are kept as I want and others can be manipulated by user.

I'd have to double check but I don't believe so - can you give me more of an idea of how/why you'd want to do this? Why would you want the user to not be able to change some of the metadata settings? The whole point is for users to be able to change it later.

The idea would be to use sidecar file as a deliberate ”lock” on some of the parameters in some specific workflows. I understand it deviates from reference implementation but it could have some uses. I’d probably have locking as an option (a tickbox) that makes it possible to signal and inform user about what parameters are set in sidecar.

[CaptainHook]

Just to understand more - you want the end user to be able to lock out changing certain parameters so that they aren't accidentally changed etc?

If so, let me think about that some more. We have added the "isReadOnly" parameter to the GetClipProcessingAttributeList and GetFrameProcessingAttributeRange etc methods so potentially we could allow users to define a processing attribute as "Read Only" via the sidecar since we have a lot of that in place already and then the SDK wouldn't allow it to be changed. Doing something similar for all metadata fields might be less likely though (have to think about it and discuss it more), but for processing attributes its more likely.

Yes, something like that. For example, lets imagine a workflow where lots of braw files get moved around and it wouldn't be efficient for whatever reasons to create plates from them in similar manner. What I could do is auto-generate sidecar files that lock some specfiic aspects, for example gamut, gamma and color science gen so that user doesn't have to do the somewhat error prone manual setup for each file. I'm currently pondering on this locking mechanism in specific application but it could in also be a feature of braw format itself, just as you suggest. Having an option to set sidecar file attributes as a read-only sounds exactly like this. It would be a soft constraint, removing or modifying sidecar would remove the lock, and very easy to create in automated manner.

[CaptainHook]

Okay, thanks for the feedback. We will discuss it and consider it for an update. Cheers.

But if you mean adding "custom" metadata we don't support that at the moment, no. How would you make use of it? It would require changes in Resolve too I think to be useful there as it currently only uses pre-defined metadata keys AFAIK.

I am coming late to this party, but as someone who has worked with database systems previously, it is exceptionally useful to have user defined data elements. It doesn't matter how many fields you put into a schema, users always want something that isn't there. Usually that elements is for classifying/categorising something, not for processing it. In the case of video metadata it is more like "shot" and "scene" than "codec" and "ISO". A similar function already exists in Fusion in the Custom node, and you can also add User Controls to each node as well. One Fusion User Control I frequently add is Sequence ID where I have a series of repeating elements and they need slightly different management e.g. the size of each successive elements increases by 20%.

One area that I would use Custom Metadata is with my drone footage. It produces Hi Res ProRes or CinemaDNG files on the SSD, and Lo Res mp4 on the SD. I am constantly looking for a way to link the two versions of the same video coming from a non-BMD camera.