----- Original Message ----- From: "Jaka Bac" <jaka...@gmail.com>
To: "FFmpeg user questions" <ffmpeg-user@ffmpeg.org>
Sent: Friday, May 05, 2017 12:31 PM
Subject: Re: [FFmpeg-user] Avid opAtom trouble


Hello

This probably happens because the ffmpeg MXF muxer does not write some
metadata that Avid expects.

Namely the following entries in the CDCI descriptor will be missing:
SampledWidth = 1920
SampledHeight = 1080

and this will be set (where 1920x1088 comes from):
StoredWidth = 1920
StoredHeight = 544

But the actual problem I believe is the missing metadata.

There is a patch floating around the mailing lists which fixes this (and
also same problem which happens where OP1a XDCAM HD files generated by
ffmpeg are imported into Avid editors).
https://ffmpeg.org/pipermail/ffmpeg-devel/2016-June/194830.html

Is there any reason why this patch is not accepted/applied?

Hi Jaka,
Is this a question for me? I can't answer it, just took the latest Zeranoe build...
thx,
Bouke

Jaka

On 2 May 2017 at 17:37, Bouke (VideoToolShed) <bo...@videotoolshed.com>
wrote:

----- Original Message ----- From: "Carl Eugen Hoyos" <ceffm...@gmail.com>
To: "FFmpeg user questions" <ffmpeg-user@ffmpeg.org>
Sent: Tuesday, May 02, 2017 4:31 PM
Subject: Re: [FFmpeg-user] Avid opAtom trouble


2017-05-02 14:46 GMT+02:00 Bouke (VideoToolShed) <bo...@videotoolshed.com
>:

Toying around with Avid opAtom mxf, generating test clips.
When I look at the clip in Avid, the bin info shows a raster dimension of
1920x1088, pixel aspect ratio of 1.007 (expected 1920x1080 / 1.000)
And of course, when editing the clip into a seqence, frameflex kicks in.

same line but output to Mov and AMA the clip in does give the
expected result.


What happens if you use FFmpeg to remux the working mov file
into mxf?


-vcodec copy NEEDS the FPS, or FFmpeg bitches. When I add -r 25, it does
the re-wrap, but output gives the same trouble in Avid.

What happens if you use FFmpeg to remux the broken mxf file
into mov?


FFmpeg reports the frame size has changed from 1088 to 1080, and all is
well.
(Except the UUID or something is copied over, so doing the dance twice to
two filenames makes Avid refuse to import both, as it 'knows' it already...)

Nice details, with -vcodec copy also timecode comes across (From MXF to
MOV and vice-versa.)
Also the interlace flag is set without issue.

Can you provide a working mxf file similar to the one FFmpeg
produces?


Yes, see here:
Download link
https://wetransfer.com/downloads/d35f135d397837227c965ee7b95
ea7bf20170502152440/018e64f2872c5c6e4de8bca6e08ca3f620170502152440/fd3691


Note, this is an AVID generated mixdown of the (good) AMA linked MOV. Tc
has changed to seqence TC (00:00:00:00)

(I believe I remember what the issue is but would like to
verify.)


Let me know if you need more, and thanks!

Bouke

Carl Eugen
_______________________________________________
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".



---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

_______________________________________________
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

_______________________________________________
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

_______________________________________________
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

Reply via email to