Hi guys, 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. Am I missing something or is this a bug? Next, what kind of metadata besides the clip name / timecode is supported? thx, Bouke ffmpeg -f lavfi -i "testsrc=size=1920x1080:rate=25" -frames:v 10 -f mxf_opatom -vcodec dnxhd -pix_fmt yuv422p -vb 120M -timecode 01:02:03:04 -metadata material_package_name="rastertest" -flags +ildct -top 1 -y "M:\Avid Mediafiles\MXF\2\test.mxf" ffmpeg version N-85653-gb4330a0 Copyright (c) 2000-2017 the FFmpeg developers built with gcc 6.3.0 (GCC) configuration: --enable-gpl --enable-version3 --enable-cuda --enable-cuvid --enable-d3d11va --enable-dxva2 --enable-libmfx --enable-nvenc --enable-avisynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libfreetype --enable-libgme --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenh264 --enable-libopenjpeg --enable-libopus --enable-librtmp --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxavs --enable-libxvid --enable-libzimg --enable-lzma --enable-zlib libavutil 55. 61.100 / 55. 61.100 libavcodec 57. 93.100 / 57. 93.100 libavformat 57. 72.101 / 57. 72.101 libavdevice 57. 7.100 / 57. 7.100 libavfilter 6. 87.100 / 6. 87.100 libswscale 4. 7.101 / 4. 7.101 libswresample 2. 8.100 / 2. 8.100 libpostproc 54. 6.100 / 54. 6.100 Input #0, lavfi, from 'testsrc=size=1920x1080:rate=25': Duration: N/A, start: 0.000000, bitrate: N/A Stream #0:0: Video: rawvideo (RGB[24] / 0x18424752), rgb24, 1920x1080 [SAR 1:1 DAR 16:9], 25 tbr, 25 tbn, 25 tbc Stream mapping: Stream #0:0 -> #0:0 (rawvideo (native) -> dnxhd (native)) Press [q] to stop, [?] for help Output #0, mxf_opatom, to 'M:\Avid MediaFiles\MXF\2\tst1.mxf': Metadata: timecode : 01:02:03:04 material_package_name: raster test encoder : Lavf57.72.101 Stream #0:0: Video: dnxhd (DNXHD), yuv422p, 1920x1080 [SAR 1:1 DAR 16:9], q=2-1024, 120000 kb/s, 25 fps, 25 tbn, 25 tbc Metadata: encoder : Lavc57.93.100 dnxhd frame= 10 fps=0.0 q=1.0 Lsize= 5927kB time=00:00:00.40 bitrate=121375.9kbits/s speed=2.38x video:5920kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.110738% --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
2017-05-02 14:46 GMT+02:00 Bouke (VideoToolShed) <bouke@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? What happens if you use FFmpeg to remux the broken mxf file into mov? Can you provide a working mxf file similar to the one FFmpeg produces? (I believe I remember what the issue is but would like to verify.) Carl Eugen
----- Original Message ----- From: "Carl Eugen Hoyos" <ceffmpeg@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) <bouke@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/d35f135d397837227c965ee7b95ea7bf20170502152... 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-request@ffmpeg.org with subject "unsubscribe".
--- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
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? Jaka On 2 May 2017 at 17:37, Bouke (VideoToolShed) <bouke@videotoolshed.com> wrote:
----- Original Message ----- From: "Carl Eugen Hoyos" <ceffmpeg@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) <bouke@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-request@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-request@ffmpeg.org with subject "unsubscribe".
----- Original Message ----- From: "Jaka Bac" <jakabac@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) <bouke@videotoolshed.com> wrote:
----- Original Message ----- From: "Carl Eugen Hoyos" <ceffmpeg@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) <bouke@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-request@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-request@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-request@ffmpeg.org with subject "unsubscribe".
Hi Bouke, No the question was not for you :) But for people who are in position to accept patches.. But probably this is the wrong mailing list.. I should have asked the question on ffmpeg-devel However I am fairly certain that this is the source of your problem... Maybe I can do a test with your file with the patch applied... Jaka On 5 May 2017 at 14:15, Bouke (VideoToolShed) <bouke@videotoolshed.com> wrote:
----- Original Message ----- From: "Jaka Bac" <jakabac@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) <bouke@videotoolshed.com> wrote:
----- Original Message ----- From: "Carl Eugen Hoyos" <ceffmpeg@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) < bouke@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/018e64f2872c5c6e4de8bca6e08ca3f620170502 152440/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-request@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-request@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-request@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-request@ffmpeg.org with subject "unsubscribe".
Hello, i use ffmpeg with Tvheadend to transcode DVB to my mobilephone. In some case I habe no sound, But Video or no Video, But sound, or the Video has freezer. After close ffmpeg and Start again its work Fine. How can i implement a automatic detection to restart ffmpeg? Now my pipe is: #!/bin/bash url=$1 su /usr/local/bin/ffmpeg \ -i $url \ -i /home/logo/HD.png \ -filter_complex overlay=main_w-overlay_w-10:main_h-overlay_h-10 \ -vcodec h264_qsv \ -b 2000k \ -minrate 2000k \ -maxrate 2000k \ -bufsize 2000k \ -preset fast \ -s 1280x720 \ -acodec aac \ -ab 128k \ -ar 44100 \ -ac 2 \ -strict \ -2 \ -metadata service_provider="Team" \ -metadata service_name=$name \ -f mpegts pipe:1 exit 0 Best reguards Spyer
Hi all, I have the same trouble. I used the latest version of FFmpeg downloaded 2018-01-26 from Zeranoe The trouble is only if I import the file. but if I use AMA relink all is ok. my workaround is FFmbc but i loking for ffmpeg solution Thk Livio -- Sent from: http://www.ffmpeg-archive.org/
participants (5)
-
algia -
Bouke (VideoToolShed) -
Carl Eugen Hoyos -
Jaka Bac -
Spyer spyer