search

kickermeister / wav2bw64

A simple tool (web-based & command line) to add basic ADM metadata to a WAV file, according to EBU Production Profile and export it as BW64 file.
3 stars 1 forks source link

Copy/move metadata from bext_chunk to respective ADM positions #6

Open WernerBleisteiner opened 3 years ago

WernerBleisteiner commented 3 years ago

BWF/RF64 in broadcaster's archives may have crucial metadata written in their bext_chunk, such as markers, regions infos (movements in classical music) or loudness values according to EBU R128 gained during the mastering process (however, only some DAWs so support the creation and export of this and it may not everywhere be applied in workflow regulations). As BW64 de facto abolished the bext_chunk, this metadata must not get lost during the transformation process. It should be preserved and go into the right places within ADM.

Subject to a possible toleration of use of the bext_chunk in BW64 (which is asked for), metadata is rather to be copied than moved.

kickermeister commented 3 years ago

That's certainly on the list. Ideal solution in my view would be to keep the bext chunk in the BW64 file but also to convert / copy the information to the axml chunk.

WernerBleisteiner commented 3 years ago

Still consider to point out to EBU that omitting bext_chunk in BW64 is possibly not a good idea as it not just contains loudness metadata but a lot of segmentation, chapter marks etc. that imho are not represented in ADM (so far). Mapping them into object metadata is definitely not the right place.