[FFmpeg-trac] #11226(ffmpeg:new): Add Track Names to OP1a MXF files
FFmpeg
trac at avcodec.org
Fri Oct 4 17:31:50 EEST 2024
#11226: Add Track Names to OP1a MXF files
-------------------------------------+-------------------------------------
Reporter: Isaac T. | Owner: (none)
Type: enhancement | Status: new
Priority: normal | Component: ffmpeg
Version: unspecified | Resolution:
Keywords: MXF mxf | Blocked By:
avid op1a tracks metadata |
Blocking: | Reproduced by developer: 0
Analyzed by developer: 0 |
-------------------------------------+-------------------------------------
Description changed by Isaac T.:
Old description:
> Hello ffmpeg Team,
>
> My name is Isaac. Thank you for all your work on ffmpeg, but I think I
> found a bug worth addressing.
>
> I am trying to add Track Names to existing OP1a MXF files with ffmpeg.
>
> For context, I want to use these OP1a MXFs in Avid Media Composer as
> editorial media, not for exports or deliverables. If Track Names are
> available and uniquely named in an OP1a MXF, those MXFs become more
> useful in the conform stage of post-production between Media Composer and
> Blackmagic Design’s DaVinci Resolve.
>
> Given an existing OP1a MXF was transcoded from something like EditReady
> by Hedge, this is the exact command line I used to add track names to an
> OP1a MXF:
>
> {{{
> ~/Downloads/ffmpeg/ffmpeg -i ~/Movies/EditReady/P1810409.mxf
> -map_metadata 0:g -metadata material_package_name="Isaac's Material
> Package Name" -metadata file_package_name="Isaac's File Package Name"
> -metadata reel_name="Isaac's Reel Name" -metadata:s:0 track_name="Track
> 1" -metadata:s:1 track_name="Track 2" -c copy ~/Movies/EditReady/test.mxf
> }}}
>
> Although ffmpeg reports successfully adding a “track_name” to each
> stream, the resulting OP1a MXFs are unusable in Avid Media Composer.
> Adding the OP1a MXFs to one of Media Composer managed media folders
> results in an error – CM_LABEL_NOT_UNIQUE, tt:2, lnum:768 – the Bin
> Column labeled “Tracks” displays an inaccurate number of tracks, and the
> associated Clip won’t play. (See attached screenshots.)
>
> Also, using ffprobe on the resulting OP1a MXFs shows no “track_name”
> metadata was added to any of the streams.
>
> Attached is the full, uncut console output from “ffmpeg -v 9 -loglevel 99
> -i” I used with my OP1a MXF from EditReady.
>
> A few last bits on OP1a MXFs you may already know:
>
> Attached is a screenshot from ffprobe of a usable OP1a MXF transcoded
> with Avid Media Composer 2024.6.
>
> Based on this screenshot, all of these metadata items will exist in an
> OP1a MXF when used by Avid Media Composer:
>
> - `material_package_name` & `material_package_umid`
> - `file_package_name` & `file_package_umid` (per stream)
> - `track_name` (per stream)
> - `reel_name` & `reel_name_umid` (per stream)
> - `timecode`
>
> Here are my observations on how Media Composer treats OP1a MXFs with and
> without certain metadata:
>
> 1. If you don't define `material_package_name`, `file_package_name`, and
> `reel_name`, MC successfully indexes, opens, and plays back an OP1a MXF.
>
> 2. If you define, `material_package_name` and `file_package_name`, MC
> successfully indexes, opens, and plays back an OP1a MXF.
>
> 3. If you define `material_package_name`, `file_package_name`, and
> `reel_name`, MC fails to index an OP1a MXF with that error. MC will open
> that Clip without crashing, but won't playback anything. Apparently, MC
> expects `track_name` to be explicitly defined per stream.
>
> And if `reel_name` isn’t present in an OP1a MXF, DaVinci Resolve users
> have to find another way to match media files when doing a conform and
> round-trip back to Media Composer.
>
> I know Media Composer is difficult to use, so if needed, these articles I
> wrote may help with testing:
>
> - Prepping Dailies for Avid Media Composer Without… Buying Media
> Composer? - https://isaact.micro.blog/2024/08/26/prepping-dailies-
> for.html
>
> - What’s the Deal With Reel Names in Avid Media Composer Clips -
> https://isaact.micro.blog/2024/09/10/inspired-by-some.html
>
> - In Praise of OP1a MXFs for Editorial Use in Avid Media Composer -
> https://isaact.micro.blog/2024/09/17/in-praise-of.html
>
> Thank you for considering!
>
> -Isaac T.-
New description:
Hello ffmpeg Team,
My name is Isaac. Thank you for all your work on ffmpeg, but I think I
found a bug worth addressing.
I am trying to add Track Names to existing OP1a MXF files with ffmpeg.
For context, I want to use these OP1a MXFs in Avid Media Composer as
editorial media, not for exports or deliverables. If Track Names are
available and uniquely named in an OP1a MXF, those MXFs become more useful
in the conform stage of post-production between Media Composer and
Blackmagic Design’s DaVinci Resolve.
Given an existing OP1a MXF was transcoded from something like EditReady by
Hedge, this is the exact command line I used to add track names to an OP1a
MXF:
`~/Downloads/ffmpeg/ffmpeg -i ~/Movies/EditReady/P1810409.mxf
-map_metadata 0:g -metadata material_package_name="Isaac's Material
Package Name" -metadata file_package_name="Isaac's File Package Name"
-metadata reel_name="Isaac's Reel Name" -metadata:s:0 track_name="Track 1"
-metadata:s:1 track_name="Track 2" -c copy ~/Movies/EditReady/test.mxf`
Although ffmpeg reports successfully adding a “track_name” to each stream,
the resulting OP1a MXFs are unusable in Avid Media Composer. Adding the
OP1a MXFs to one of Media Composer managed media folders results in an
error – CM_LABEL_NOT_UNIQUE, tt:2, lnum:768 – the Bin Column labeled
“Tracks” displays an inaccurate number of tracks, and the associated Clip
won’t play. (See attached screenshots.)
Also, using ffprobe on the resulting OP1a MXFs shows no “track_name”
metadata was added to any of the streams.
[https://trac.ffmpeg.org/timeline?from=2024-10-04T17%3A03%3A55%2B03%3A00&precision=second
Attached is the full, uncut console output from “ffmpeg -v 9 -loglevel 99
-i” I used with my OP1a MXF from EditReady.]
A few last bits on OP1a MXFs you may already know:
[https://trac.ffmpeg.org/timeline?from=2024-10-04T17%3A21%3A02%2B03%3A00&precision=second
Attached is a screenshot from ffprobe of a usable OP1a MXF transcoded with
Avid Media Composer 2024.6.]
Based on this screenshot, all of these metadata items will exist in an
OP1a MXF when used by Avid Media Composer:
- `material_package_name` & `material_package_umid`
- `file_package_name` & `file_package_umid` (per stream)
- `track_name` (per stream)
- `reel_name` & `reel_name_umid` (per stream)
- `timecode`
Here are my observations on how Media Composer treats OP1a MXFs with and
without certain metadata:
1. If you don't define `material_package_name`, `file_package_name`, and
`reel_name`, MC successfully indexes, opens, and plays back an OP1a MXF.
2. If you define, `material_package_name` and `file_package_name`, MC
successfully indexes, opens, and plays back an OP1a MXF.
3. If you define `material_package_name`, `file_package_name`, and
`reel_name`, MC fails to index an OP1a MXF with that error. MC will open
that Clip without crashing, but won't playback anything. Apparently, MC
expects `track_name` to be explicitly defined per stream.
And if `reel_name` isn’t present in an OP1a MXF, DaVinci Resolve users
have to find another way to match media files when doing a conform and
round-trip back to Media Composer.
I know Media Composer is difficult to use, so if needed, these articles I
wrote may help with testing:
- Prepping Dailies for Avid Media Composer Without… Buying Media Composer?
- https://isaact.micro.blog/2024/08/26/prepping-dailies-for.html
- What’s the Deal With Reel Names in Avid Media Composer Clips -
https://isaact.micro.blog/2024/09/10/inspired-by-some.html
- In Praise of OP1a MXFs for Editorial Use in Avid Media Composer -
https://isaact.micro.blog/2024/09/17/in-praise-of.html
Thank you for considering!
-Isaac T.-
--
--
Ticket URL: <https://trac.ffmpeg.org/ticket/11226#comment:4>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list