#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 |
-------------------------------------+-------------------------------------
Comment (by Isaac T.):
@Tomas: thanks for giving this a look.
I uploaded another set of console output using the command in this thread
to add `track_name` metadata to each stream.
Here's the excerpt from that output that ffmpeg reporting it successfully
added `track_name`'s to each stream:
{{{
Successfully opened the file.
Stream mapping:
Stream #0:0 -> #0:0 (copy)
Stream #0:1 -> #0:1 (copy)
[pcm_rechunk_bsf @ 0x7fa2e5704ac0] Setting entry with key 'r' to value
'24000/1001'
Automatically inserted bitstream filter 'pcm_rechunk'; args='r=24000/1001'
Output #0, mxf, to '/Users/isaacterronez/Movies/EditReady/test.mxf':
Metadata:
operational_pattern_ul: 060e2b34.04010101.0d010201.01010900
uid : adab4424-2f25-4dc7-92ff-000c00000000
generation_uid : adab4424-2f25-4dc7-92ff-000c00000001
company_name : Hedge
product_name : EditReady
product_version_num: 59.27.100.0.0
product_version : 24.4
application_platform: Lavf (darwin)
product_uid : adab4424-2f25-4dc7-92ff-29bd000c0002
toolkit_version_num: 59.27.100.0.0
material_package_umid:
0x060A2B340101010501010D00139F56AD52947134C99F56AD0052947134C99F00
timecode : 00:22:19:01
material_package_name: Isaac's Material Package Name
file_package_name: Isaac's File Package Name
reel_name : Isaac's Reel Name
encoder : Lavf61.5.101
Stream #0:0, 0, 1001/24000: Video: dnxhd (DNXHD), 1 reference frame,
yuv422p(bt709/unknown/unknown, progressive), 1920x1080 [SAR 1:1 DAR 16:9],
0/1, q=2-31, 23.98 fps, 23.98 tbr, 23.98 tbn
Metadata:
file_package_umid:
0x060A2B340101010501010D00139F56AD52947134C99F56AD0052947134C99F01
reel_umid :
0x060A2B340101010501010D00139F56AD52947134C99F56AD0052947134C99F02
reel_name : From EditReady 24.4
timecode : 00:22:19:01
track_name : Track 1
Stream #0:1, 0, 1/48000: Audio: pcm_s24le, 48000 Hz, stereo, s32 (24
bit), 2304 kb/s
Metadata:
file_package_umid:
0x060A2B340101010501010D00139F56AD52947134C99F56AD0052947134C99F01
reel_umid :
0x060A2B340101010501010D00139F56AD52947134C99F56AD0052947134C99F02
reel_name : From EditReady 24.4
timecode : 00:22:19:01
track_name : Track 2
}}}
> Also Avid Media Composer is notoriously picky about MXF as far as I
remember
You're right! Re-reading my last reply, I realized I forgot to attach that
screenshot of the ffprobe report on an OP1a MXF created by Media Composer.
I've uploaded it now and annotated it for so you can easily locate the
metadata needed to satisfy Media Composer's requirements based on my
obersvations:
1. `material_package_name` & `material_package_umid`
2. `file_package_name` & `file_package_umid` (per stream)
3. `track_name` (per stream)
4. `reel_name` & `reel_name_umid` (per stream)
5. `timecode`
--
Ticket URL: <https://trac.ffmpeg.org/ticket/11226#comment:2>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker_______________________________________________
FFmpeg-trac mailing list
[email protected]
https://ffmpeg.org/mailman/listinfo/ffmpeg-trac
To unsubscribe, visit link above, or email
[email protected] with subject "unsubscribe".
