Re: [FFmpeg-user] question regarding store_user_comments
Am Mittwoch, 25. Januar 2017 schrieb Carl Eugen Hoyos : > 2017-01-24 17:56 GMT+01:00 Julian Link >: > > > i am trying to write metadata to an mxf file. > > > > ffmpeg.exe -i Z:\hide\MXF_files\A019C046.mxf -an -f mxf_opatom -b:v 36M > > -metadata comment_x=y out.mxf > > > > Before ffmpeg version 2.8.2 this line worked as expected. > > Please also test current FFmpeg git head, nothing else is supported here. > > I'd rather go with bmxtools, obviously you're trying to make something work with Avid MC, which ffmpeg isn't playing nicely with atm. Erik ___ 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".
Re: [FFmpeg-user] EVS compatible AVC Intra 100
> > The problem is that EVS doesn't seem to properly recognize it. Amberfin > is > > working properly with the generated mxf however. > > (Maybe you should ask EVS why they don't like the file?) > > I think the best way is to compare the ffmpeg result (and the EVS file) to > an original Panasonic file. EVS doesn't write 100% identical files as the > cam would. > Also, ffmpeg is/used to be not very good at writing op-atom, I've had better results using the bmxtools or ffmbc if you want to avoid batch processing a single file with multiple tools. Erik ___ 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".
Re: [FFmpeg-user] question regarding store_user_comments
2017-01-25 9:37 GMT+01:00 Erik Dobberkau : > Am Mittwoch, 25. Januar 2017 schrieb Carl Eugen Hoyos : > >> 2017-01-24 17:56 GMT+01:00 Julian Link : >> >> > i am trying to write metadata to an mxf file. >> > >> > ffmpeg.exe -i Z:\hide\MXF_files\A019C046.mxf -an -f mxf_opatom >> > -b:v 36M -metadata comment_x=y out.mxf >> > >> > Before ffmpeg version 2.8.2 this line worked as expected. >> >> Please also test current FFmpeg git head, nothing else is supported here. >> >> > I'd rather go with bmxtools, obviously you're trying to make something > work with Avid MC, which ffmpeg isn't playing nicely with atm. Is there a regression we don't know about? 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".
Re: [FFmpeg-user] question regarding store_user_comments
> > I'd rather go with bmxtools, obviously you're trying to make something > > work with Avid MC, which ffmpeg isn't playing nicely with atm. > > Is there a regression we don't know about? > > I don't know either, but the (now outdated) builds I've been working with did not produce OP-Atoms that would properly work with Avid MC. Erik ___ 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".
Re: [FFmpeg-user] question regarding store_user_comments
- Original Message - From: "Erik Dobberkau" To: "FFmpeg user questions" Sent: Wednesday, January 25, 2017 11:16 AM Subject: Re: [FFmpeg-user] question regarding store_user_comments > I'd rather go with bmxtools, obviously you're trying to make something > work with Avid MC, which ffmpeg isn't playing nicely with atm. Is there a regression we don't know about? I don't know either, but the (now outdated) builds I've been working with did not produce OP-Atoms that would properly work with Avid MC. Probably unrelated, but using -t xx or -shortest on creating MpegII (XDcam) Op1A files will make avid bitch about something with 'mob' (I forgot the exact details, but can create testlines if you like..) bouke Erik __". --- 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".
Re: [FFmpeg-user] question regarding store_user_comments
Tested it with the latest git snapshot. Does not make any difference. If nobody has an idea why it is not working I`ll try bmxtools next. Thank you all Best, Jules [jules@deepthought ffmpeg]$ ffmpeg -i /media/120TB/hide/MXF_files/A019C046.mxf -an -f mxf_opatom -store_user_comments 1 -b:v 36M -metadata comment_x=y out.mxf ffmpeg version N-83198-g9ea2998 Copyright (c) 2000-2017 the FFmpeg developers built with gcc 4.8.5 (GCC) 20150623 (Red Hat 4.8.5-11) configuration: --prefix=/home/jules/ffmpeg_build --extra-cflags=-I/home/jules/ffmpeg_build/include --extra-ldflags='-L/home/jules/ffmpeg_build/lib -ldl' --bindir=/home/jules/bin --pkg-config-flags=--static --enable-gpl --enable-nonfree --enable-libfdk_aac --enable-libfreetype --enable-libmp3lame --enable-libopus --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libx265 libavutil 55. 44.100 / 55. 44.100 libavcodec 57. 75.100 / 57. 75.100 libavformat57. 63.100 / 57. 63.100 libavdevice57. 2.100 / 57. 2.100 libavfilter 6. 69.100 / 6. 69.100 libswscale 4. 3.101 / 4. 3.101 libswresample 2. 4.100 / 2. 4.100 libpostproc54. 2.100 / 54. 2.100 [dnxhd @ 0x3c20c20] frame size changed: 1920x1088 -> 1920x1080 Input #0, mxf, from '/media/120TB/hide/MXF_files/A019C046.mxf': Metadata: uid : adab4424-2f25-4dc7-92ff-29bd000c generation_uid : adab4424-2f25-4dc7-92ff-29bd000c0001 company_name: FFmpeg product_name: OPAtom Muxer product_version : 57.63.100 product_uid : adab4424-2f25-4dc7-92ff-29bd000c0002 modification_date: 0-01-02T00:00:00.00Z material_package_umid: 0x060A2B340101010501010D001324A82352947134D824A8230052947134D82400 timecode: 13:33:28:23 Duration: 00:00:10.00, start: 0.00, bitrate: 37688 kb/s Stream #0:0: Video: dnxhd (DNXHD), yuv422p(bt709/unknown/unknown, progressive), 1920x1080, SAR 1:1 DAR 16:9, 25 fps, 25 tbr, 25 tbn, 25 tbc Metadata: file_package_umid: 0x060A2B340101010501010D001324A82352947134D824A8230052947134D82401 Output #0, mxf_opatom, to 'out.mxf': Metadata: uid : adab4424-2f25-4dc7-92ff-29bd000c generation_uid : adab4424-2f25-4dc7-92ff-29bd000c0001 company_name: FFmpeg product_name: OPAtom Muxer product_version : 57.63.100 product_uid : adab4424-2f25-4dc7-92ff-29bd000c0002 modification_date: 0-01-02T00:00:00.00Z material_package_umid: 0x060A2B340101010501010D001324A82352947134D824A8230052947134D82400 timecode: 13:33:28:23 comment_x : y encoder : Lavf57.63.100 Stream #0:0: Video: dnxhd (DNXHD), yuv422p, 1920x1080 [SAR 1:1 DAR 16:9], q=2-1024, 36000 kb/s, 25 fps, 25 tbn, 25 tbc Metadata: file_package_umid: 0x060A2B340101010501010D001324A82352947134D824A8230052947134D82401 encoder : Lavc57.75.100 dnxhd Stream mapping: Stream #0:0 -> #0:0 (dnxhd (native) -> dnxhd (native)) Press [q] to stop, [?] for help frame= 250 fps=0.0 q=2.0 Lsize= 46007kB time=00:00:10.00 bitrate=37688.6kbits/s speed=14.9x video:46000kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.014251% [jules@deepthought ffmpeg]$ ffprobe out.mxf ffprobe version N-83198-g9ea2998 Copyright (c) 2007-2017 the FFmpeg developers built with gcc 4.8.5 (GCC) 20150623 (Red Hat 4.8.5-11) configuration: --prefix=/home/jules/ffmpeg_build --extra-cflags=-I/home/jules/ffmpeg_build/include --extra-ldflags='-L/home/jules/ffmpeg_build/lib -ldl' --bindir=/home/jules/bin --pkg-config-flags=--static --enable-gpl --enable-nonfree --enable-libfdk_aac --enable-libfreetype --enable-libmp3lame --enable-libopus --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libx265 libavutil 55. 44.100 / 55. 44.100 libavcodec 57. 75.100 / 57. 75.100 libavformat57. 63.100 / 57. 63.100 libavdevice57. 2.100 / 57. 2.100 libavfilter 6. 69.100 / 6. 69.100 libswscale 4. 3.101 / 4. 3.101 libswresample 2. 4.100 / 2. 4.100 libpostproc54. 2.100 / 54. 2.100 [dnxhd @ 0x427e280] frame size changed: 1920x1088 -> 1920x1080 Input #0, mxf, from 'out.mxf': Metadata: uid : adab4424-2f25-4dc7-92ff-29bd000c generation_uid : adab4424-2f25-4dc7-92ff-29bd000c0001 company_name: FFmpeg product_name: OPAtom Muxer product_version : 57.63.100 product_uid : adab4424-2f25-4dc7-92ff-29bd000c0002 modification_date: 0-01-02T00:00:00.00Z material_package_umid: 0x060A2B340101010501010D0013D56E2D52947134D9D56E2D0052947134D9D500 timecode: 13:33:28:23 Duration: 00:00:10.00, start: 0.00, bitrate: 37688 kb/s Stream #0:0: Video: dnxhd (DNXHD), yuv422p(bt709/unknown/unknown, progressive), 1920x1080, SAR 1:1 DAR 16:9, 25 fps, 25 tbr, 25 tbn, 25 tbc Metadata: file_package_umid: 0x060A2B340101010501010D0013D56E2D52947134D9D56E2D0052947134D9D501 [jules@deept
Re: [FFmpeg-user] question regarding store_user_comments
On Wed, Jan 25, 2017 at 17:02:06 +0100, Julian Link wrote: > [jules@deepthought ffmpeg]$ ffmpeg -i > /media/120TB/hide/MXF_files/A019C046.mxf -an -f mxf_opatom > -store_user_comments 1 -b:v 36M -metadata comment_x=y out.mxf According to $ ffmpeg -h muxer=mxf_opatom the mxf_opatom muxer does *not* support "-store_user_comments". The mxf muxer does though, and setting your comment works there. If I change the MXF muxer's OpA1 code to expose and use that option (see attached patch), it actually works: $ ./ffmpeg_g -f lavfi -i testsrc2=s=hd1080 -f mxf_opatom -store_user_comments 1 -b:v 36M -metadata comment_x=y -t 1 ~/tmp/out.mxf -y ffmpeg version N-83183-gd60f090 Copyright (c) 2000-2017 the FFmpeg developers built with icc (ICC) 14.0.3 20140422 configuration: --prefix=/usr/new/tools/video/install/ffmpeg/2017-01-21 --cc=icc --cxx=icpc --enable-gpl --enable-version3 --enable-nonfree --disable-shared --enable-gnutls --enable-libcdio --enable-libfreetype --enable-libx264 --enable-libvpx --enable-libmp3lame --enable-openal --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libtwolame --enable-libopenjpeg --enable-librtmp --enable-libass --enable-li bv4l2 --enable-libvidstab --enable-libfdk-aac --enable-libsmbclient --enable-libzvbi --enable-libtesseract --enable-libzmq libavutil 55. 43.100 / 55. 43.100 libavcodec 57. 75.100 / 57. 75.100 libavformat57. 62.100 / 57. 62.100 libavdevice57. 2.100 / 57. 2.100 libavfilter 6. 69.100 / 6. 69.100 libswscale 4. 3.101 / 4. 3.101 libswresample 2. 4.100 / 2. 4.100 libpostproc54. 2.100 / 54. 2.100 Input #0, lavfi, from 'testsrc2=s=hd1080': Duration: N/A, start: 0.00, bitrate: N/A Stream #0:0: Video: rawvideo (I420 / 0x30323449), yuv420p, 1920x1080 [SAR 1:1 DAR 16:9], 25 tbr, 25 tbn, 25 tbc Output #0, mxf_opatom, to '/home/barsnick/tmp/out.mxf': Metadata: comment_x : y encoder : Lavf57.62.100 Stream #0:0: Video: dnxhd (DNXHD), yuv422p, 1920x1080 [SAR 1:1 DAR 16:9], q=2-1024, 36000 kb/s, 25 fps, 25 tbn, 25 tbc Metadata: encoder : Lavc57.75.100 dnxhd Stream mapping: Stream #0:0 -> #0:0 (rawvideo (native) -> dnxhd (native)) Press [q] to stop, [?] for help [swscaler @ 0xb7bfb40] Warning: data is not aligned! This can lead to a speedloss frame= 25 fps= 10 q=1.0 Lsize=4607kB time=00:00:01.00 bitrate=37736.9kbits/s speed=0.402x video:4600kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.142514% $ ./ffmpeg_g -i ~/tmp/out.mxf ffmpeg version N-83183-gd60f090 Copyright (c) 2000-2017 the FFmpeg developers built with icc (ICC) 14.0.3 20140422 configuration: --prefix=/usr/new/tools/video/install/ffmpeg/2017-01-21 --cc=icc --cxx=icpc --enable-gpl --enable-version3 --enable-nonfree --disable-shared --enable-gnutls --enable-libcdio --enable-libfreetype --enable-libx264 --enable-libvpx --enable-libmp3lame --enable-openal --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libtwolame --enable-libopenjpeg --enable-librtmp --enable-libass --enable-libv4l2 --enable-libvidstab --enable-libfdk-aac --enable-libsmbclient --enable-libzvbi --enable-libtesseract --enable-libzmq libavutil 55. 43.100 / 55. 43.100 libavcodec 57. 75.100 / 57. 75.100 libavformat57. 62.100 / 57. 62.100 libavdevice57. 2.100 / 57. 2.100 libavfilter 6. 69.100 / 6. 69.100 libswscale 4. 3.101 / 4. 3.101 libswresample 2. 4.100 / 2. 4.100 libpostproc54. 2.100 / 54. 2.100 [dnxhd @ 0xbd04420] frame size changed: 1920x1088 -> 1920x1080 Input #0, mxf, from '/home/barsnick/tmp/out.mxf': Metadata: uid : adab4424-2f25-4dc7-92ff-29bd000c generation_uid : adab4424-2f25-4dc7-92ff-29bd000c0001 company_name: FFmpeg product_name: OPAtom Muxer product_version : 57.62.100 product_uid : adab4424-2f25-4dc7-92ff-29bd000c0002 modification_date: 1905-06-07T18:35:44.00Z material_package_umid: 0x060A2B340101010501010D001348BF4F529471342248BF4F0052947134224800 comment_x : y timecode: 00:00:00:00 Duration: 00:00:01.00, start: 0.00, bitrate: 37736 kb/s Stream #0:0: Video: dnxhd (DNXHD), yuv422p(bt709/unknown/unknown, progressive), 1920x1080, SAR 1:1 DAR 16:9, 25 fps, 25 tbr, 25 tbn, 25 tbc Metadata: file_package_umid: 0x060A2B340101010501010D001348BF4F529471342248BF4F0052947134224801 At least one output file must be specified $ I may be violating the format though, what do I know. Perhaps it isn't supported for a reason. Michael N. introduced the feature (of toggling the storage) here: https://github.com/FFmpeg/FFmpeg/commit/d9726893f311b7bbbc9887db2c3ffbefaad78ca3 where it is on by default for MXF, off by default for D10 (because "not allowed"), but not at all exposed to OpA1. Do ask Michael or the MXF maintainer... It *is* a regression in terms of "it used to work for mxf_opatom, but
[FFmpeg-user] C920 Report shows yuvformat
Hi guys Help me with c920 please, even though i change the formats, it still reinits format to yuv420. Why is that? *Canberk Demirsoy* B.Sc. Electrical Engineering, Sabancı University M.Sc. Computer Engineering, Munich Technical University ___ 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".
Re: [FFmpeg-user] C920 Report shows yuvformat
Hi On 25 Jan 2017 18:25, "Canberk Demirsoy (Alumni)" wrote: Hi guys Help me with c920 please, even though i change the formats, it still reinits format to yuv420. Why is that? Can you post the full, uncut console output along with your full command line? That will allow people to answer your question. ___ 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".
Re: [FFmpeg-user] C920 Report shows yuvformat
I will but got off work, see you tomorrow. On Wed, 25 Jan 2017 at 19:39, Kieran O Leary wrote: > Hi > > On 25 Jan 2017 18:25, "Canberk Demirsoy (Alumni)" < > cdemir...@sabanciuniv.edu> > wrote: > > Hi guys > > Help me with c920 please, even though i change the formats, it still > reinits format to yuv420. Why is that? > > > Can you post the full, uncut console output along with your full command > line? That will allow people to answer your question. > ___ > 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". -- *Canberk Demirsoy* B.Sc. Electrical Engineering, Sabancı University M.Sc. Computer Engineering, Munich Technical University ___ 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] Can the video orientation be adjusted for part of an Mp4 ?
Hi, We have a video that was taken from a mobile phone. The first part of the video is not orientated properly, and needs to be moved anti-clockwise 90 degress. At approximately 4:30 , the video orientation is corrected. Is there a method with ffmpeg to adjust the video orientation for the first 4:40 minutes ? Here is the video details: ffmpeg version 2.8.10-0ubuntu0.16.04.1 Copyright (c) 2000-2016 the FFmpeg developers built with gcc 5.4.0 (Ubuntu 5.4.0-6ubuntu1~16.04.4) 20160609 configuration: --prefix=/usr --extra-version=0ubuntu0.16.04.1 --build-suffix=- ffmpeg --toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu --incdir=/usr/ include/x86_64-linux-gnu --cc=cc --cxx=g++ --enable-gpl --enable-shared -- disable-stripping --disable-decoder=libopenjpeg --disable- decoder=libschroedinger --enable-avresample --enable-avisynth --enable-gnutls --enable-ladspa --enable-libass --enable-libbluray --enable-libbs2b --enable- libcaca --enable-libcdio --enable-libflite --enable-libfontconfig --enable- libfreetype --enable-libfribidi --enable-libgme --enable-libgsm --enable- libmodplug --enable-libmp3lame --enable-libopenjpeg --enable-libopus --enable- libpulse --enable-librtmp --enable-libschroedinger --enable-libshine --enable- libsnappy --enable-libsoxr --enable-libspeex --enable-libssh --enable- libtheora --enable-libtwolame --enable-libvorbis --enable-libvpx --enable- libwavpack --enable-libwebp --enable-libx265 --enable-libxvid --enable-libzvbi --enable-openal --enable-opengl --enable-x11grab --enable-libdc1394 --enable- libiec61883 --enable-libzmq --enable-frei0r --enable-libx264 --enable- libopencv libavutil 54. 31.100 / 54. 31.100 libavcodec 56. 60.100 / 56. 60.100 libavformat56. 40.101 / 56. 40.101 libavdevice56. 4.100 / 56. 4.100 libavfilter 5. 40.101 / 5. 40.101 libavresample 2. 1. 0 / 2. 1. 0 libswscale 3. 1.101 / 3. 1.101 libswresample 1. 2.101 / 1. 2.101 libpostproc53. 3.100 / 53. 3.100 Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '1000_686782998156148_4534047573949808640_n.mp4': Metadata: major_brand : isom minor_version : 512 compatible_brands: isomiso2avc1mp41 encoder : Lavf56.40.101 Duration: 00:56:48.13, start: 0.00, bitrate: 580 kb/s Stream #0:0(und): Video: h264 (Main) (avc1 / 0x31637661), yuv420p, 360x636, 501 kb/s, 26.93 fps, 1k tbr, 90k tbn, 2k tbc (default) Metadata: handler_name: VideoHandler Stream #0:1(und): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, mono, fltp, 69 kb/s (default) Metadata:
Re: [FFmpeg-user] EVS compatible AVC Intra 100
Thanks for the answers. I didn't paste the output because I did not get any error. I already checked with EVS and just wanted to make sure I got the "standard"AVC Intra 100 parameters right and that I was not making any mistake before getting back to them. Erik, the mxf was one of my suspicions as well, that's why I rewrapped the file with bmxtranswrap so I could get v1.3 instead of 1.2. This is the output I'm getting, all seems ok to me. host:~$ ffmpeg10bit -i /mnt/file.mxf -coder 0 -map 0 -c:v libx264 -r 25 -g 1 -pix_fmt yuv422p10le -vb 100M -flags +ildct+ilme -tune psnr -x264opts avcintra-class=100 -x264opts colorprim=bt709 -x264opts transfer=bt709 -x264opts colormatrix=bt709 -x264opts tune=psnr -x264opts interlaced=1 -x264opts force-cfr=1 -x264opts fps=25/1 -vf "setfield=1" -c:a copy ~/test.mxf ffmpeg version n3.1.6-8-g6c96200 Copyright (c) 2000-2016 the FFmpeg developers built with gcc 4.8 (Ubuntu 4.8.4-2ubuntu1~14.04.3) configuration: --prefix=/usr --enable-gpl --enable-libx264 --enable-pthreads --enable-static --extra-cflags=-I./x264/include --extra-ldflags=-L./x264/lib --extra-libs=-ldl --progs-suffix=10bit libavutil 55. 28.100 / 55. 28.100 libavcodec 57. 48.101 / 57. 48.101 libavformat57. 41.100 / 57. 41.100 libavdevice57. 0.101 / 57. 0.101 libavfilter 6. 47.100 / 6. 47.100 libswscale 4. 1.100 / 4. 1.100 libswresample 2. 1.100 / 2. 1.100 libpostproc54. 0.100 / 54. 0.100 Guessed Channel Layout for Input Stream #0.1 : mono Guessed Channel Layout for Input Stream #0.2 : mono Guessed Channel Layout for Input Stream #0.3 : mono Guessed Channel Layout for Input Stream #0.4 : mono Guessed Channel Layout for Input Stream #0.5 : mono Guessed Channel Layout for Input Stream #0.6 : mono Guessed Channel Layout for Input Stream #0.7 : mono Guessed Channel Layout for Input Stream #0.8 : mono Input #0, mxf, from '/mnt/file.mxf': Metadata: uid : 479ac510-b1ae-11e6-9a9c-002590e81d4f generation_uid : 479ac510-b1ae-11e6-9a9d-002590e81d4f company_name: OC product_name: OCTk product_version : 2.8 product_uid : 3a4fe380-0d01-11e4-869f-3cd92b5c1dfc modification_date: 2016-11-23 19:54:36 material_package_umid: 0x060A2B340101010501010D20130047998C90B1AE11E69A7F002590E81D4F timecode: 19:49:40:00 Duration: 00:00:24.00, start: 0.00, bitrate: 60781 kb/s Stream #0:0: Video: mpeg2video (4:2:2), yuv422p(tv, bt709), 1920x1080 [SAR 1:1 DAR 16:9], 5 kb/s, 25 fps, 25 tbr, 25 tbn, 50 tbc Metadata: file_package_umid: 0x060A2B340101010501010D20130047987B20B1AE11E69A64002590E81D4F Stream #0:1: Audio: pcm_s24le, 48000 Hz, 1 channels, s32 (24 bit), 1152 kb/s Metadata: file_package_umid: 0x060A2B340101010501010D20130047987B20B1AE11E69A64002590E81D4F Stream #0:2: Audio: pcm_s24le, 48000 Hz, 1 channels, s32 (24 bit), 1152 kb/s Metadata: file_package_umid: 0x060A2B340101010501010D20130047987B20B1AE11E69A64002590E81D4F Stream #0:3: Audio: pcm_s24le, 48000 Hz, 1 channels, s32 (24 bit), 1152 kb/s Metadata: file_package_umid: 0x060A2B340101010501010D20130047987B20B1AE11E69A64002590E81D4F Stream #0:4: Audio: pcm_s24le, 48000 Hz, 1 channels, s32 (24 bit), 1152 kb/s Metadata: file_package_umid: 0x060A2B340101010501010D20130047987B20B1AE11E69A64002590E81D4F Stream #0:5: Audio: pcm_s24le, 48000 Hz, 1 channels, s32 (24 bit), 1152 kb/s Metadata: file_package_umid: 0x060A2B340101010501010D20130047987B20B1AE11E69A64002590E81D4F Stream #0:6: Audio: pcm_s24le, 48000 Hz, 1 channels, s32 (24 bit), 1152 kb/s Metadata: file_package_umid: 0x060A2B340101010501010D20130047987B20B1AE11E69A64002590E81D4F Stream #0:7: Audio: pcm_s24le, 48000 Hz, 1 channels, s32 (24 bit), 1152 kb/s Metadata: file_package_umid: 0x060A2B340101010501010D20130047987B20B1AE11E69A64002590E81D4F Stream #0:8: Audio: pcm_s24le, 48000 Hz, 1 channels, s32 (24 bit), 1152 kb/s Metadata: file_package_umid: 0x060A2B340101010501010D20130047987B20B1AE11E69A64002590E81D4F [libx264 @ 0x27b6f60] using SAR=1/1 [libx264 @ 0x27b6f60] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX FMA3 AVX2 LZCNT BMI2 [libx264 @ 0x27b6f60] profile High 4:2:2 Intra, level 4.1, 4:2:2 10-bit [mxf @ 0x2ac8960] Using AVStream.codec to pass codec parameters to muxers is deprecated, use AVStream.codecpar instead. Last message repeated 8 times Output #0, mxf, to '/home/upop/test.mxf': Metadata: uid : 479ac510-b1ae-11e6-9a9c-002590e81d4f generation_uid : 479ac510-b1ae-11e6-9a9d-002590e81d4f company_name: OC product_name: OCTk product_version : 2.8 product_uid : 3a4fe380-0d01-11e4-869f-3cd92b5c1dfc modification_date: 2016-11-23 19:54:36 material_package_umid: 0x060A2B340101010501010D20130047998C90B1AE11E69A7F002590E81D4F
