hi,
Some avid generated mxf files store source timecode component on a
pulldown component in the physcial source package. This patch adds
support for reading source timecode from the pulldown component if it is there.
I was unable to find a pre-existing sample so I upload one to upload.ffmpeg.org.
pulldown_example.mxf
pulldown_example.txt
output from ffprobe with patch:
Input #0, mxf, from ‘pulldown_example.mxf':
Metadata:
uid : 72b39808-5b65-9e4c-a830-fc22493803e3
generation_uid : b6bcfcab-70ff-7331-54ed-4b7469de11d2
application_platform: AAFSDK (MacOS X)
modification_date: 2014-10-13 01:45:36
product_uid : acfbf03a-4f42-a231-d0b7-c06ecd3d4ad7
product_version : Unknown version
product_name : Avid Media Composer 8.1.0.34535
company_name : Avid Technology, Inc.
Duration: 00:00:00.04, start: 0.000000, bitrate: 100779 kb/s
Stream #0:0: Video: dvvideo, yuv411p, 720x480 [SAR 32:27 DAR 16:9], 24 tbr,
24 tbn, 29.97 tbc
Metadata:
reel_name : pulldown_example.mov
timecode : 12:34:56:13
mxfenc.c uses uses the MXFMetadataSetType enum values to generate InstanceUIDs
and thats why I had to update the fate-lavf-mxf tests. If I added
PulldownComponent to the bottom of enum in mxf.h the tests don't fail. AFAIK the
InstanceUIDs just need to be unique.
Mark Reid (1):
libavformat/mxfdec: read source timecode from pulldown component
libavformat/mxf.h | 1 +
libavformat/mxfdec.c | 31 +++++++++++++++++++++++++++++--
tests/ref/lavf/mxf | 6 +++---
tests/ref/lavf/mxf_d10 | 2 +-
4 files changed, 34 insertions(+), 6 deletions(-)
--
2.0.0
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
