mencoder reads wrong frame rate flag from Quicktime files
Hi everyone, I've noticed something odd when reading Quicktime files with mencoder. Specifically broadcast HD formats such as ProRes and DVCPRO HD. Quicktime seems to flag these files as VFR (even though they are not) and then flags them with odd frame rate info. Is there a way to read the frame rate correctly when encoding with mencoder without forcing the frame rate with a command? Heres the flags from mediainfo on a 23.976 ProRes file (I know its 23.976 as I captured the file with FCP): Frame rate mode : Variable Frame rate : 24.014 fps Minimum frame rate : 15.984 fps Maximum frame rate : 162.000 fps Mencoder reads this as 15.984fps. If I force it using the -fps 23.976 command I can encode it without skipping frames but I need to set it up as a script for encoding thousands of files at different frame rates. As there is no consistency with what the actual frame rate is it's hard to write something without rounding up the frame rate to the nearest whole number or something but that would not work when trying to differentiate between 23.976 and 24 material, or 29.97 and 30 material. Is there a command in mencoder that tries to work out the frame rate of the file more accurately? Thanks in advance! Heres the command im using FYI: mencoder -demuxer mov \\xxx\testmovhd2398.mov -o \\xxx\testmovhd2398.flv -vf pp=fd,scale=1280:720 -af channels=2,format=s16le,resample=44100 -mc 0 -ovc x264 -x264encopts global_header:level_idc=30:bframes=0:bitrate=2048:preset=superfast -oac faac -faacopts mpeg=4:object=2:br=128:raw -of lavf
-----Original Message----- From: mplayer-advusers-bounces@mplayerhq.hu [mailto:mplayer-advusers-bounces@mplayerhq.hu] On Behalf Of Dominic Bird Sent: 06 July 2010 15:13 To: MPlayer-advusers@mplayerhq.hu Subject: [MPlayer-advusers] mencoder reads wrong frame rate flag fromQuicktime files Hi everyone, I've noticed something odd when reading Quicktime files with mencoder. Specifically broadcast HD formats such as ProRes and DVCPRO HD. Quicktime seems to flag these files as VFR (even though they are not) and then flags them with odd frame rate info. Is there a way to read the frame rate correctly when encoding with mencoder without forcing the frame rate with a command? Heres the flags from mediainfo on a 23.976 ProRes file (I know its 23.976 as I captured the file with FCP): Frame rate mode : Variable Frame rate : 24.014 fps Minimum frame rate : 15.984 fps Maximum frame rate : 162.000 fps Mencoder reads this as 15.984fps. If I force it using the -fps 23.976 command I can encode it without skipping frames but I need to set it up as a script for encoding thousands of files at different frame rates. As there is no consistency with what the actual frame rate is it's hard to write something without rounding up the frame rate to the nearest whole number or something but that would not work when trying to differentiate between 23.976 and 24 material, or 29.97 and 30 material. Is there a command in mencoder that tries to work out the frame rate of the file more accurately? Thanks in advance! Heres the command im using FYI: mencoder -demuxer mov \\xxx\testmovhd2398.mov -o \\xxx\testmovhd2398.flv -vf pp=fd,scale=1280:720 -af channels=2,format=s16le,resample=44100 -mc 0 -ovc x264 -x264encopts global_header:level_idc=30:bframes=0:bitrate=2048:preset=superfast -oac faac -faacopts mpeg=4:object=2:br=128:raw -of lavf _______________________________________________ MPlayer-advusers mailing list MPlayer-advusers@mplayerhq.hu https://lists.mplayerhq.hu/mailman/listinfo/mplayer-advusers I think i've found it. Mencoder should read the 'Time Scale' flag rather than any frame rate flags with VFR material. If you use ExifTool on a Quicktime file the 'Time Scale' data = the frame rate. See below on 2 test files. First is 23.976, second is 29.97. ExifTool Version Number : 8.24 File Name : testmovhd2398.mov File Type : MOV MIME Type : video/quicktime Time Scale : 23976 Duration : 9.26 s Compressor ID : apch Source Image Width : 1920 Source Image Height : 1080 Video Frame Rate : 24.013 ExifTool Version Number : 8.24 File Name : testmovhd2997.mov File Type : MOV MIME Type : video/quicktime Time Scale : 2997 Duration : 8.21 s Compressor ID : apch Source Image Width : 1920 Source Image Height : 1080 Video Frame Rate : 29.91
On Tue, 6 Jul 2010 15:12:48 +0100, Dominic Bird wrote:
Mencoder reads this as 15.984fps. If I force it using the -fps 23.976 mencoder -demuxer mov \\xxx\testmovhd2398.mov -o \\xxx\testmovhd2398.flv
why not using -demuxer lavf? does -demuxer lavf give correct fps? what mencoder version? what programs can output the correct fps in a vfr file? quicktime / fcp.. anything else? it looks like mediainfo rounds the fps or just gets it wrong (24.014). is the correct fps stored in the mov container in an atom or something? a sample vfr file (if we dont already have one in http://samples.mplayerhq.hu/mov/ ) would be useful. also, this mailing list is for patches/development not bugreports/user questions. use mencoder-users list or mplayer-users list in the future. -compn
On Tue, 6 Jul 2010 12:01:15 -0400, compn wrote:
also, this mailing list is for patches/development not bugreports/user questions. use mencoder-users list or mplayer-users list in the future.
oops, its been so long since i've seen an -advusers post that i thought this was on dev-eng, please ignore the above message. -compn
-----Original Message----- From: mplayer-advusers-bounces@mplayerhq.hu [mailto:mplayer-advusers-bounces@mplayerhq.hu] On Behalf Of compn Sent: 06 July 2010 17:01 To: MPlayer bug reports Subject: Re: [MPlayer-advusers] mencoder reads wrong frame rate flag from Quicktime files On Tue, 6 Jul 2010 15:12:48 +0100, Dominic Bird wrote:
Mencoder reads this as 15.984fps. If I force it using the -fps 23.976 mencoder -demuxer mov \\xxx\testmovhd2398.mov -o \\xxx\testmovhd2398.flv
why not using -demuxer lavf? does -demuxer lavf give correct fps? what mencoder version? what programs can output the correct fps in a vfr file? quicktime / fcp.. anything else? it looks like mediainfo rounds the fps or just gets it wrong (24.014). is the correct fps stored in the mov container in an atom or something? a sample vfr file (if we dont already have one in http://samples.mplayerhq.hu/mov/ ) would be useful. also, this mailing list is for patches/development not bugreports/user questions. use mencoder-users list or mplayer-users list in the future. -compn _______________________________________________ MPlayer-advusers mailing list MPlayer-advusers@mplayerhq.hu https://lists.mplayerhq.hu/mailman/listinfo/mplayer-advusers thanks for response! -demuxer lavf gives correct frame rate but cannot use lavf as im decoding prores so i need to use QTMLClient.dll for decoding. Mencoder version is r31372 win32 from http://oss.netfarm.it/mplayer-win32.php. The file is not actually VFR, but Final Cut flags it that way for some reason (as it seems to all captured HD files). Apparently the way you work out the frame rate is from the is like this... It looks like ffmpeg's .MOV parser sets the video stream frame rate solely based on the time scale, which doesn't work for FCP's .MOV files. Instead it must divide the time scale by the duration of one video sample (as found in the 'stts' atom). http://lists.mplayerhq.hu/pipermail/ffmpeg-devel/2006-February/006914.ht ml Is there some way I can use the frame rate extracted by lavf and insert it in the command? Like -fps lavf? That would solve all my issues!!! If not then the -demuxer mov has a bug and needs to calculate the fps differently.
-----Original Message----- From: mplayer-advusers-bounces@mplayerhq.hu [mailto:mplayer-advusers-bounces@mplayerhq.hu] On Behalf Of Dominic Bird Sent: 06 July 2010 17:14 To: MPlayer bug reports Subject: Re: [MPlayer-advusers] mencoder reads wrong frame rate flag fromQuicktime files -----Original Message----- From: mplayer-advusers-bounces@mplayerhq.hu [mailto:mplayer-advusers-bounces@mplayerhq.hu] On Behalf Of compn Sent: 06 July 2010 17:01 To: MPlayer bug reports Subject: Re: [MPlayer-advusers] mencoder reads wrong frame rate flag from Quicktime files On Tue, 6 Jul 2010 15:12:48 +0100, Dominic Bird wrote:
Mencoder reads this as 15.984fps. If I force it using the -fps 23.976 mencoder -demuxer mov \\xxx\testmovhd2398.mov -o \\xxx\testmovhd2398.flv
why not using -demuxer lavf? does -demuxer lavf give correct fps? what mencoder version? what programs can output the correct fps in a vfr file? quicktime / fcp.. anything else? it looks like mediainfo rounds the fps or just gets it wrong (24.014). is the correct fps stored in the mov container in an atom or something? a sample vfr file (if we dont already have one in http://samples.mplayerhq.hu/mov/ ) would be useful. also, this mailing list is for patches/development not bugreports/user questions. use mencoder-users list or mplayer-users list in the future. -compn _______________________________________________ MPlayer-advusers mailing list MPlayer-advusers@mplayerhq.hu https://lists.mplayerhq.hu/mailman/listinfo/mplayer-advusers thanks for response! -demuxer lavf gives correct frame rate but cannot use lavf as im decoding prores so i need to use QTMLClient.dll for decoding. Mencoder version is r31372 win32 from http://oss.netfarm.it/mplayer-win32.php. The file is not actually VFR, but Final Cut flags it that way for some reason (as it seems to all captured HD files). Apparently the way you work out the frame rate is from the is like this... It looks like ffmpeg's .MOV parser sets the video stream frame rate solely based on the time scale, which doesn't work for FCP's .MOV files. Instead it must divide the time scale by the duration of one video sample (as found in the 'stts' atom). http://lists.mplayerhq.hu/pipermail/ffmpeg-devel/2006-February/006914.ht ml Is there some way I can use the frame rate extracted by lavf and insert it in the command? Like -fps lavf? That would solve all my issues!!! If not then the -demuxer mov has a bug and needs to calculate the fps differently. _______________________________________________ MPlayer-advusers mailing list MPlayer-advusers@mplayerhq.hu https://lists.mplayerhq.hu/mailman/listinfo/mplayer-advusers and this is why i can't use the lavf demuxer... http://archives.free.net.ph/message/20090731.134921.b39a58ca.en.html if I could it would be great as it obviously uses the right method to get the frame rate!
On Tue, 6 Jul 2010 17:13:56 +0100, Dominic Bird wrote:
thanks for response! -demuxer lavf gives correct frame rate but cannot use lavf as im decoding prores so i need to use QTMLClient.dll for decoding. Mencoder version is r31372 win32 from
binary codecs dont work with lavf :(
http://oss.netfarm.it/mplayer-win32.php. The file is not actually VFR,
are you able to use mplayer to play the video? here i only get black screen. it does work in mencoder for me. prores only works in windows xp for me. on win2k i get DecompressSequenceFrameS result=0x-8961 and decoding fails. 8961 points to 'noCodecErr' in the apple quicktime api. i'm not sure where to look to fix this on win2k.
but Final Cut flags it that way for some reason (as it seems to all captured HD files). Apparently the way you work out the frame rate is from the is like this...
argh, what an annoying fcp problem.
It looks like ffmpeg's .MOV parser sets the video stream frame rate solely based on the time scale, which doesn't work for FCP's .MOV files. Instead it must divide the time scale by the duration of one video sample (as found in the 'stts' atom).
http://lists.mplayerhq.hu/pipermail/ffmpeg-devel/2006-February/006914.ht ml
Is there some way I can use the frame rate extracted by lavf and insert it in the command? Like -fps lavf? That would solve all my issues!!! If not then the -demuxer mov has a bug and needs to calculate the fps differently.
unfortunately no. you can only get lavf's fps information if you use -demuxer lavf and that doesnt work with the binary codecs. mplayer made -demuxer lavf default because -demuxer mov was unmaintained. patches welcome to fix this fps bug , but i dont think any of the devs are interested in fixing it. this looks like the same bug in our bug tracker: http://bugzilla.mplayerhq.hu/show_bug.cgi?id=1065 anyways, you can use the mplayer -demuxer lavf -identify -frames 1 to get the correct fps, then script it to use that in your mencoder line. it doesnt seem like a very efficient method, but at least it works. -compn
-----Original Message----- From: mplayer-advusers-bounces@mplayerhq.hu [mailto:mplayer-advusers-bounces@mplayerhq.hu] On Behalf Of compn Sent: 06 July 2010 21:17 To: mplayer-advusers@mplayerhq.hu Subject: Re: [MPlayer-advusers] mencoder reads wrong frame rate flag from Quicktime files On Tue, 6 Jul 2010 17:13:56 +0100, Dominic Bird wrote:
thanks for response! -demuxer lavf gives correct frame rate but cannot use lavf as im decoding prores so i need to use QTMLClient.dll for decoding. Mencoder version is r31372 win32 from
binary codecs dont work with lavf :(
http://oss.netfarm.it/mplayer-win32.php. The file is not actually VFR,
are you able to use mplayer to play the video? here i only get black screen. it does work in mencoder for me. prores only works in windows xp for me. on win2k i get DecompressSequenceFrameS result=0x-8961 and decoding fails. 8961 points to 'noCodecErr' in the apple quicktime api. i'm not sure where to look to fix this on win2k.
but Final Cut flags it that way for some reason (as it seems to all captured HD files). Apparently the way you work out the frame rate is from the is like this...
argh, what an annoying fcp problem.
It looks like ffmpeg's .MOV parser sets the video stream frame rate solely based on the time scale, which doesn't work for FCP's .MOV files. Instead it must divide the time scale by the duration of one video sample (as found in the 'stts' atom).
http://lists.mplayerhq.hu/pipermail/ffmpeg-devel/2006-February/006914.h t ml
Is there some way I can use the frame rate extracted by lavf and insert it in the command? Like -fps lavf? That would solve all my issues!!! If not then the -demuxer mov has a bug and needs to calculate the fps differently.
unfortunately no. you can only get lavf's fps information if you use -demuxer lavf and that doesnt work with the binary codecs. mplayer made -demuxer lavf default because -demuxer mov was unmaintained. patches welcome to fix this fps bug , but i dont think any of the devs are interested in fixing it. this looks like the same bug in our bug tracker: http://bugzilla.mplayerhq.hu/show_bug.cgi?id=1065 anyways, you can use the mplayer -demuxer lavf -identify -frames 1 to get the correct fps, then script it to use that in your mencoder line. it doesnt seem like a very efficient method, but at least it works. -compn _______________________________________________ MPlayer-advusers mailing list MPlayer-advusers@mplayerhq.hu https://lists.mplayerhq.hu/mailman/listinfo/mplayer-advusers I agree with all your points but is there no way of getting a fix submitted into the mov demuxer? Surely the way it works out the frame rate just needs to be taken from the lavf demuxer. Its probably more complicated than that but im not a coder undortunately!
I've raised a bug for this on mplayer bug list and posted on here. Doesnt seem to be much going on. Is there any chance of this being fixed in the mov demuxer or lavf being able to use binary codecs? -----Original Message----- From: mplayer-advusers-bounces@mplayerhq.hu [mailto:mplayer-advusers-bounces@mplayerhq.hu] On Behalf Of Dominic Bird Sent: 07 July 2010 10:30 To: MPlayer bug reports Subject: Re: [MPlayer-advusers] mencoder reads wrong frame rate flag fromQuicktime files -----Original Message----- From: mplayer-advusers-bounces@mplayerhq.hu [mailto:mplayer-advusers-bounces@mplayerhq.hu] On Behalf Of compn Sent: 06 July 2010 21:17 To: mplayer-advusers@mplayerhq.hu Subject: Re: [MPlayer-advusers] mencoder reads wrong frame rate flag from Quicktime files On Tue, 6 Jul 2010 17:13:56 +0100, Dominic Bird wrote:
thanks for response! -demuxer lavf gives correct frame rate but cannot use lavf as im decoding prores so i need to use QTMLClient.dll for decoding. Mencoder version is r31372 win32 from
binary codecs dont work with lavf :(
http://oss.netfarm.it/mplayer-win32.php. The file is not actually VFR,
are you able to use mplayer to play the video? here i only get black screen. it does work in mencoder for me. prores only works in windows xp for me. on win2k i get DecompressSequenceFrameS result=0x-8961 and decoding fails. 8961 points to 'noCodecErr' in the apple quicktime api. i'm not sure where to look to fix this on win2k.
but Final Cut flags it that way for some reason (as it seems to all captured HD files). Apparently the way you work out the frame rate is from the is like this...
argh, what an annoying fcp problem.
It looks like ffmpeg's .MOV parser sets the video stream frame rate solely based on the time scale, which doesn't work for FCP's .MOV files. Instead it must divide the time scale by the duration of one video sample (as found in the 'stts' atom).
http://lists.mplayerhq.hu/pipermail/ffmpeg-devel/2006-February/006914.h t ml
Is there some way I can use the frame rate extracted by lavf and insert it in the command? Like -fps lavf? That would solve all my issues!!! If not then the -demuxer mov has a bug and needs to calculate the fps differently.
unfortunately no. you can only get lavf's fps information if you use -demuxer lavf and that doesnt work with the binary codecs. mplayer made -demuxer lavf default because -demuxer mov was unmaintained. patches welcome to fix this fps bug , but i dont think any of the devs are interested in fixing it. this looks like the same bug in our bug tracker: http://bugzilla.mplayerhq.hu/show_bug.cgi?id=1065 anyways, you can use the mplayer -demuxer lavf -identify -frames 1 to get the correct fps, then script it to use that in your mencoder line. it doesnt seem like a very efficient method, but at least it works. -compn _______________________________________________ MPlayer-advusers mailing list MPlayer-advusers@mplayerhq.hu https://lists.mplayerhq.hu/mailman/listinfo/mplayer-advusers I agree with all your points but is there no way of getting a fix submitted into the mov demuxer? Surely the way it works out the frame rate just needs to be taken from the lavf demuxer. Its probably more complicated than that but im not a coder undortunately! _______________________________________________ MPlayer-advusers mailing list MPlayer-advusers@mplayerhq.hu https://lists.mplayerhq.hu/mailman/listinfo/mplayer-advusers
On Fri, Jul 23, 2010 at 05:58:55PM +0100, Dominic Bird wrote:
I've raised a bug for this on mplayer bug list and posted on here. Doesnt seem to be much going on. Is there any chance of this being fixed in the mov demuxer or lavf being able to use binary codecs?
Please use a mailer with proper quoting, neither top-posting nor putting the reply somewhere where nobody can find it because it looks exactly like the quoted text is any good. I can't test it because the decoder does not work at all for me on Linux (though it might just be that the qthtml.dll etc. files from the codec pack are too old for that codec), but here's a patch that builds a similar imagedesc with -demuxer lavf. MPlayer will print a hexdump of that data, the differences between the one with -demuxer mov and -demuxer lavf should be trivial to see, if it does not work it's just a matter of finding out which other fields need to be filled in. I'd assume at least the "vendor" is necessary in addition.
-----Original Message----- From: mplayer-advusers-bounces@mplayerhq.hu [mailto:mplayer-advusers- bounces@mplayerhq.hu] On Behalf Of Reimar Döffinger Sent: 23 July 2010 20:34 To: MPlayer bug reports Subject: Re: [MPlayer-advusers] mencoder reads wrong frame rate flag fromQuicktime files
On Fri, Jul 23, 2010 at 05:58:55PM +0100, Dominic Bird wrote:
I've raised a bug for this on mplayer bug list and posted on here. Doesnt seem to be much going on. Is there any chance of this being fixed in the mov demuxer or lavf being able to use binary codecs?
Please use a mailer with proper quoting, neither top-posting nor putting the reply somewhere where nobody can find it because it looks exactly like the quoted text is any good. I can't test it because the decoder does not work at all for me on Linux (though it might just be that the qthtml.dll etc. files from the codec pack are too old for that codec), but here's a patch that builds a similar imagedesc with -demuxer lavf. MPlayer will print a hexdump of that data, the differences between the one with -demuxer mov and -demuxer lavf should be trivial to see, if it does not work it's just a matter of finding out which other fields need to be filled in. I'd assume at least the "vendor" is necessary in addition.
Thanks for the help. Unfortunately I am not a developer so I was hoping it might be taken on as a bug request and fixed. Ive posted it in the mplayer/mencoder bug tracker but looks like nothing has been touched there for a long time...
On Mon, 26 Jul 2010 09:28:59 +0100, Dominic Bird wrote:
On Fri, 23 Jul 2010 21:33:44 +0200, Reimar Döffinger wrote:
I can't test it because the decoder does not work at all for me on Linux (though it might just be that the qthtml.dll etc. files from the codec pack are too old for that codec), but here's a patch that builds a similar imagedesc with -demuxer lavf. MPlayer will print a hexdump of that data, the differences between the one with -demuxer mov and -demuxer lavf should be trivial to see, if it does not work it's just a matter of finding out which other fields need to be filled in. I'd assume at least the "vendor" is necessary in addition.
Thanks for the help. Unfortunately I am not a developer so I was hoping it might be taken on as a bug request and fixed. Ive posted it in the mplayer/mencoder bug tracker but looks like nothing has been touched there for a long time...
reimar committed this, so its being worked on. there are still some bugs. current status on win2k with -demuxer lavf (demuxer mov working unless noted) qtsvq1 crashes in decode_video (i'm guessing inside of the dll). -8961 is 'noCodecErr', a very helpful error message. qtsvq3 DecompressSequenceFrameS result=0x-8961 qt3ivx DecompressSequenceBegin result=-8961 (after adding 3iv1 to isom.c) qth263 working, aside from image too small inside mov bug. qt261 working, aside from image too small inside mov bug. qtactl working qtavui DecompressSequenceBegin result=-8961 qtrlerpza DecompressSequenceBegin result=-8961 (frozen video in r30521 with demux mov) qtvp3 working qtzygo working qtbhiv no sample qtcvid DecompressSequenceFrameS result=0x-8961 qtindeo working qtmjpeg DecompressSequenceFrameS result=0x-8961 qtmpeg4 DecompressSequenceBegin result=-8961 (fails in rc1/svn with demux mov too) qtcine decoded picture is incorrect , samples/V-codecs/v210/coff3.mov qtaic dont have mac box to test atm qtprores DecompressSequenceFrameS result=0x-8961 (with demuxer mov too) --now i dont remember how i got prores to work before. qdmc audio seems to crash using binary codec with lavf. i have one svq1 file which is broken in r31372 and svn with -demuxer mov and -vc qtsvq1. it works in 30521. uploaded to samples/V-codecs/SVQ1. the imagedescription is different, i wonder if thats the cause? not working, green w/static: F:\mplayer-test>mplayer MystxSVQD12.mov -demuxer mov -vfm qtvideo MPlayer Sherpya-SVN-r31372-4.2.5 (C) 2000-2010 MPlayer Team 154 audio & 345 video codecs Fontconfig error: Cannot load default config file Playing MystxSVQD12.mov. Quicktime/MOV file format detected. [mov] Video stream found, -vid 0 [mov] Audio stream found, -aid 1 VIDEO: [SVQ1] 240x180 24bpp 12.000 fps 0.0 kbps ( 0.0 kbyte/s) Clip info: copyright: Copyright ⌐ 1997 Opening video filter: [scale] Opening video filter: [eq] ========================================================================== Trying to force video codec driver family qtvideo... Opening video decoder: [qtvideo] Quicktime Video decoder 56 00 00 00 53 56 51 31 00 00 00 00 00 00 00 00 01 00 01 00 73 69 56 53 FF 03 00 00 00 02 00 00 F0 00 B4 00 00 00 48 00 00 00 48 00 00 00 00 00 01 00 0E 53 6F 72 65 6E 73 6F 6E 20 56 69 64 65 6F 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 18 00 FF FF =============== ImageDescription at 0356f128 ================== idSize=0x56 fourcc=0x31515653 ver=1 rev=1 vendor=0x53566973 tempQ=1023 spatQ=512 dim: 240 x 180 dpi: 72.00 x 72.00 depth: 24 dataSize=0 frameCount=1 clutID=-1 name='Sorenson Video' ========================================================= Movie-Aspect is undefined - no prescaling applied. [swscaler @ 02444010]using unscaled yuv410p -> yuv410p special converter VO: [directx] 240x180 => 240x180 Planar YVU9 Selected video codec: [qtsvq1] vfm: qtvideo (Win32/QuickTime SVQ1) ========================================================================== ========================================================================== Trying to force audio codec driver family ffmpeg... Opening audio decoder: [qtaudio] QuickTime Audio Decoder AUDIO: 11025 Hz, 1 ch, s16le, 23.9 kbit/13.57% (ratio: 2993->22050) Selected audio codec: [qdmc] afm: qtaudio (QuickTime QDMC/QDM2 audio) ========================================================================== AO: [dsound] 11025Hz 1ch s16le (2 bytes per sample) Starting playback... Fontconfig failed to select a font. Trying without fontconfig... Fontconfig failed to select a font. Trying without fontconfig... A: 0.5 V: 0.5 A-V: 0.002 ct: 0.000 7/ 7 ??% ??% ??,?% 0 0 Exiting... (Quit) working: F:\mplayer-test>mplayera MystxSVQD12.mov -demuxer mov -vfm qtvideo MPlayer Sherpya-SVN-r30521 (C) 2000-2010 MPlayer Team 154 audio & 345 video codecs Fontconfig error: Cannot load default config file Playing MystxSVQD12.mov. Quicktime/MOV file format detected. [mov] Video stream found, -vid 0 [mov] Audio stream found, -aid 1 VIDEO: [SVQ1] 240x180 24bpp 12.000 fps 0.0 kbps ( 0.0 kbyte/s) Clip info: copyright: Copyright ⌐ 1997 dvdsublang...mystxsvqd12 en,eng, dvdsublang...mystxsvqd12 en,eng, dvdsublang...mystxsvqd12 en,eng, dvdsublang...mystxsvqd12 en,eng, dvdsublang...mystxsvqd12 en,eng, dvdsublang...mystxsvqd12 en,eng, Opening video filter: [scale] Opening video filter: [eq] ========================================================================== Trying to force video codec driver family qtvideo... Opening video decoder: [qtvideo] Quicktime Video decoder 56 00 00 00 53 56 51 31 00 00 00 00 00 00 00 00 01 00 01 00 73 69 56 53 FF 03 00 00 00 02 00 00 F0 00 B4 00 00 00 48 00 00 00 48 00 00 00 00 00 01 00 0E 53 6F 72 65 6E 73 6F 6E 20 56 69 64 65 6F 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 18 00 FF FF =============== ImageDescription at 0270F128 ================== idSize=0x56 fourcc=0x31515653 ver=1 rev=1 vendor=0x53566973 tempQ=1023 spatQ=512 dim: 240 x 180 dpi: 4718592 x 4718592 depth: 24 dataSize=0 frameCount=1 clutID=-1 name='Sorenson Video' ========================================================= Movie-Aspect is undefined - no prescaling applied. [swscaler @ 021e2010]using unscaled yuv410p -> yuv410p special converter VO: [directx] 240x180 => 240x180 Planar YVU9 Selected video codec: [qtsvq1] vfm: qtvideo (Win32/QuickTime SVQ1) ========================================================================== ========================================================================== Trying to force audio codec driver family ffmpeg... Opening audio decoder: [qtaudio] QuickTime Audio Decoder AUDIO: 11025 Hz, 1 ch, s16le, 23.9 kbit/13.57% (ratio: 2993->22050) Selected audio codec: [qdmc] afm: qtaudio (QuickTime QDMC/QDM2 audio) ========================================================================== AO: [dsound] 11025Hz 1ch s16le (2 bytes per sample) Starting playback... Fontconfig failed to select a font. Trying without fontconfig... Fontconfig failed to select a font. Trying without fontconfig... A: 0.8 V: 0.8 A-V: 0.002 ct: 0.001 11/ 11 1% 6% 1.3% 0 0 Exiting... (Quit) -compn
-----Original Message----- From: mplayer-advusers-bounces@mplayerhq.hu [mailto:mplayer-advusers- bounces@mplayerhq.hu] On Behalf Of compn Sent: 26 July 2010 15:44 To: mplayer-advusers@mplayerhq.hu Subject: Re: [MPlayer-advusers] mencoder reads wrong frame rate flag fromQuicktime files
On Fri, 23 Jul 2010 21:33:44 +0200, Reimar Döffinger wrote:
I can't test it because the decoder does not work at all for me on Linux (though it might just be that the qthtml.dll etc. files from
codec pack are too old for that codec), but here's a patch that builds a similar imagedesc with -demuxer lavf. MPlayer will print a hexdump of that data, the differences between
On Mon, 26 Jul 2010 09:28:59 +0100, Dominic Bird wrote: the the
one with -demuxer mov and -demuxer lavf should be trivial to see, if it does not work it's just a matter of finding out which other fields need to be filled in. I'd assume at least the "vendor" is necessary in addition.
Thanks for the help. Unfortunately I am not a developer so I was hoping it might be taken on as a bug request and fixed. Ive posted it in the mplayer/mencoder bug tracker but looks like nothing has been touched there for a long time...
reimar committed this, so its being worked on. there are still some bugs.
Personally the only problem im having is the frame rate being read incorrectly with the mov demuxer. Everything else works perfectly (binary codecs/prores/dvcpro hd/xdcam anything I throw at it) so not sure if much needs changing. I know what the actual problem is as I've been chatting to the guys from mediainfo about it. Basically when MediaInfo or the MOV demuxer from mencoder sees VFR flagged they seem to take an average of first/middle/last frame rates. With ProRes HD files they are VFR because the first and last frames are VFR, but the rest are constant, so it should just take the mean fps and all would be solved :)
Basically when MediaInfo or the MOV demuxer from mencoder sees VFR flagged they seem to take an average of first/middle/last frame rates. With ProRes HD files they are VFR because the first and last frames are VFR, but the rest are constant, so it should just take the mean fps and all would be solved :) _______________________________________________ MPlayer-advusers mailing list MPlayer-advusers@mplayerhq.hu https://lists.mplayerhq.hu/mailman/listinfo/mplayer-advusers
I meant a median FPS value!
Hi! On Mon, 26 Jul 2010, compn wrote:
qtprores DecompressSequenceFrameS result=0x-8961 (with demuxer mov too)
Works fine for me with Boar__Apple_ProRes_422-partial.mov Carl Eugen
Does mplayer supports apple ProRes422? Em Terça-feira 27 Julho 2010, às 06:23:15, Carl Eugen Hoyos escreveu:
Hi!
On Mon, 26 Jul 2010, compn wrote:
qtprores DecompressSequenceFrameS result=0x-8961 (with demuxer mov too)
Works fine for me with Boar__Apple_ProRes_422-partial.mov
Carl Eugen
-----Original Message----- From: mplayer-advusers-bounces@mplayerhq.hu [mailto:mplayer-advusers- bounces@mplayerhq.hu] On Behalf Of Rafael Diniz Sent: 27 July 2010 14:49 To: mplayer-advusers@mplayerhq.hu Cc: Carl Eugen Hoyos Subject: Re: [MPlayer-advusers] mencoder reads wrong frame rate flagfromQuicktime files
Does mplayer supports apple ProRes422?
Em Terça-feira 27 Julho 2010, às 06:23:15, Carl Eugen Hoyos escreveu:
Hi!
On Mon, 26 Jul 2010, compn wrote:
qtprores DecompressSequenceFrameS result=0x-8961 (with demuxer mov too)
Works fine for me with Boar__Apple_ProRes_422-partial.mov
Carl Eugen
MPlayer-advusers mailing list MPlayer-advusers@mplayerhq.hu https://lists.mplayerhq.hu/mailman/listinfo/mplayer-advusers
It does if you use -demuxer mov and take a file from the apple quicktime sdk and put it in clients
Hi everybody! On Tue, 27 Jul 2010, Rafael Diniz wrote:
Does mplayer supports apple ProRes422?
Once more: MPlayer supports ProRes422 on certain architectures (x86_32) via binary decoder. Wherever it works, it works fine with -demuxer lavf and (possibly with limitations) with -demuxer mov. Carl Eugen PS: Note that _only_ latest svn is supported on this list, on mplayer-users and mencoder-users and that all problem reports must at least contain complete command line and complete, uncut console output. PPS: Please do not top-post, it is considered rude. PPPS: Please cut your quotes, not doing so is also considered rude.
-----Original Message----- From: mplayer-advusers-bounces@mplayerhq.hu [mailto:mplayer-advusers- bounces@mplayerhq.hu] On Behalf Of Carl Eugen Hoyos Sent: 27 July 2010 17:22 To: MPlayer bug reports Subject: Re: [MPlayer-advusers] mencoder reads wrong frame rate flag fromQuicktime files
Hi everybody!
On Tue, 27 Jul 2010, Rafael Diniz wrote:
Does mplayer supports apple ProRes422?
Once more:
MPlayer supports ProRes422 on certain architectures (x86_32) via binary decoder. Wherever it works, it works fine with -demuxer lavf and (possibly with limitations) with -demuxer mov.
Carl Eugen
PS: Note that _only_ latest svn is supported on this list, on mplayer-users and mencoder-users and that all problem reports must at least contain complete command line and complete, uncut console output.
PPS: Please do not top-post, it is considered rude.
PPPS: Please cut your quotes, not doing so is also considered rude. _______________________________________________ MPlayer-advusers mailing list MPlayer-advusers@mplayerhq.hu https://lists.mplayerhq.hu/mailman/listinfo/mplayer-advusers
I didn't think binary codecs were support with LAVF? I've never got it to work with prores.
On Wed, Jul 28, 2010 at 11:16:44AM +0100, Dominic Bird wrote:
PPPS: Please cut your quotes, not doing so is also considered rude.
This applies to you as well.
I didn't think binary codecs were support with LAVF? I've never got it to work with prores.
Did you try latest Subversion HEAD? Reimar committed a fix. Diego
-----Original Message----- From: mplayer-advusers-bounces@mplayerhq.hu [mailto:mplayer-advusers- bounces@mplayerhq.hu] On Behalf Of Diego Biurrun Sent: 29 July 2010 11:10 To: MPlayer bug reports Subject: Re: [MPlayer-advusers] mencoder reads wrong frame rateflag fromQuicktime files
On Wed, Jul 28, 2010 at 11:16:44AM +0100, Dominic Bird wrote:
PPPS: Please cut your quotes, not doing so is also considered
rude.
This applies to you as well.
I didn't think binary codecs were support with LAVF? I've never got it to work with prores.
Did you try latest Subversion HEAD? Reimar committed a fix.
Diego _______________________________________________ MPlayer-advusers mailing list MPlayer-advusers@mplayerhq.hu https://lists.mplayerhq.hu/mailman/listinfo/mplayer-advusers
Im not a developer so I have no idea how to build mplayer from scratch I'm afraid! I'll have to wait until the win32 builds get updated and then try. Where do you see the changelogs? I've searched everywhere but can't find anything and I get a 404 here... http://svn.mplayerhq.hu/mplayer/trunk/
On Thu, 29 Jul 2010 11:29:27 +0100, Dominic Bird wrote:
On Wed, Jul 28, 2010 at 11:16:44AM +0100, Dominic Bird wrote:
PPPS: Please cut your quotes, not doing so is also considered
rude.
This applies to you as well.
I didn't think binary codecs were support with LAVF? I've never got it to work with prores.
Did you try latest Subversion HEAD? Reimar committed a fix.
Diego
Im not a developer so I have no idea how to build mplayer from scratch I'm afraid! I'll have to wait until the win32 builds get updated and then try.
any user can build mplayer. for win32 it means you have to download and install mingw/msys. sometimes its difficult to do install and compile.
Where do you see the changelogs? I've searched everywhere but can't find anything and I get a 404 here... http://svn.mplayerhq.hu/mplayer/trunk/
any user can build mplayer. for win32 it means you have to download and install mingw/msys. sometimes its difficult to do install and compile.
Where do you see the changelogs? I've searched everywhere but can't find anything and I get a 404 here... http://svn.mplayerhq.hu/mplayer/trunk/
http://lists.mplayerhq.hu/pipermail/mplayer-cvslog/
-compn _______________________________________________ MPlayer-advusers mailing list MPlayer-advusers@mplayerhq.hu https://lists.mplayerhq.hu/mailman/listinfo/mplayer-advusers
I downloaded minigw and some libs that go with it from the win32 build site to try and have a go at making my own fixes but have no idea where to start. Got as far as running the makefile and got thousands of errors about paths etc... if I had the time to learn to build and compile I would love to!
On Thu, Jul 29, 2010 at 1:57 PM, compn <tempn@twmi.rr.com> wrote:
On Thu, 29 Jul 2010 11:29:27 +0100, Dominic Bird wrote:
On Wed, Jul 28, 2010 at 11:16:44AM +0100, Dominic Bird wrote: Im not a developer so I have no idea how to build mplayer from scratch I'm afraid! I'll have to wait until the win32 builds get updated and then try.
any user can build mplayer. for win32 it means you have to download and install mingw/msys. sometimes its difficult to do install and compile.
This is a very bad attitude. Being a developer, I'm not afraid of doing a ./configure && make && sudo make install. However, a vast majority of the world population doesn't have a compiler installed on their system (let alone a fully configured mingw/msys system). Most of the users also wants the software to *just work*. They don't want to have to fiddle with it for hours, just to get it working. Having a mindset in which "any user can build my project from sources" is dangerous for the project. See http://xkcd.com/196/ for another thought on that subject. --Shachar
On Thu, Jul 29, 2010 at 02:07:35PM +0300, Shachar Raindel wrote:
On Thu, Jul 29, 2010 at 1:57 PM, compn <tempn@twmi.rr.com> wrote:
On Thu, 29 Jul 2010 11:29:27 +0100, Dominic Bird wrote:
On Wed, Jul 28, 2010 at 11:16:44AM +0100, Dominic Bird wrote: Im not a developer so I have no idea how to build mplayer from scratch I'm afraid! I'll have to wait until the win32 builds get updated and then try.
any user can build mplayer. for win32 it means you have to download and install mingw/msys. sometimes its difficult to do install and compile.
This is a very bad attitude. Being a developer, I'm not afraid of doing a ./configure && make && sudo make install. However, a vast majority of the world population doesn't have a compiler installed on their system (let alone a fully configured mingw/msys system). Most of the users also wants the software to *just work*. They don't want to have to fiddle with it for hours, just to get it working. Having a mindset in which "any user can build my project from sources" is dangerous for the project.
On this specific list at least I consider your comment very much out of line. That said, the user-friendlyness of MinGW was always questionable and has been getting worse. Using Cygwin might be simpler, if you do not care about OSD/text subtitle etc., a ./configure --enable-static --with-yasm='' --cc=gcc-3.4 --extra-cflags=-mno-cygwin --extra-ldflags=-mno-cygwin --target=i686-mingw32 --enable-gui directly after installation even produces a binary that works without the cygwin runtime. But even compared to that, installing Ubuntu first and compiling MPlayer on that probably still could be considered simpler...
This is a very bad attitude. Being a developer, I'm not afraid of doing a ./configure && make && sudo make install. However, a vast majority of the world population doesn't have a compiler installed on their system (let alone a fully configured mingw/msys system). Most of the users also wants the software to *just work*. They don't want to have to fiddle with it for hours, just to get it working. Having a mindset in which "any user can build my project from sources" is dangerous for the project. See http://xkcd.com/196/ for another thought on that subject.
--Shachar _______________________________________________ MPlayer-advusers mailing list MPlayer-advusers@mplayerhq.hu https://lists.mplayerhq.hu/mailman/listinfo/mplayer-advusers
Agreed! As an end user I have no problem experimenting with mplayer/mencoders many different functions for hours to get the best result or get it working properly and finding work arounds to bugs... but I don't have time to learn to compile and build it myself first! No doubt I would introduce even more problems than an experienced developer would.
On Thu, Jul 29, 2010 at 01:04:30PM +0100, Dominic Bird wrote:
Agreed! As an end user I have no problem experimenting with mplayer/mencoders many different functions for hours to get the best result or get it working properly and finding work arounds to bugs... but I don't have time to learn to compile and build it myself first! No doubt I would introduce even more problems than an experienced developer would.
Let me make one thing clear: This is a list that all MPlayer developers are supposed to _have_ to subsribe to. This means 1) Beyond being pointless due to just restating previous ones, this discussion has no place here. 2) If you are not willing or able to recompile from latest SVN this is the wrong list. Documentation patches clarifying this welcome, discussing this on this list _not_. Use MPlayer-users if you don't like these restraints, but I expect this to be the end of the discussion on _this_ list.
On Tue, Jul 06, 2010 at 04:16:52PM -0400, compn wrote:
On Tue, 6 Jul 2010 17:13:56 +0100, Dominic Bird wrote: [...] anyways, you can use the mplayer -demuxer lavf -identify -frames 1 to get the correct fps, then script it to use that in your mencoder line. it doesnt seem like a very efficient method, but at least it works.
fixing demuxer lavf for the binary codecs would seem like a nicer long term solution what is the problem?, extradata format? [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Its not that you shouldnt use gotos but rather that you should write readable code and code with gotos often but not always is less readable
On Sun, Jul 11, 2010 at 10:54:00PM +0200, Michael Niedermayer wrote:
On Tue, Jul 06, 2010 at 04:16:52PM -0400, compn wrote:
On Tue, 6 Jul 2010 17:13:56 +0100, Dominic Bird wrote: [...] anyways, you can use the mplayer -demuxer lavf -identify -frames 1 to get the correct fps, then script it to use that in your mencoder line. it doesnt seem like a very efficient method, but at least it works.
fixing demuxer lavf for the binary codecs would seem like a nicer long term solution what is the problem?, extradata format?
I don't know about this case specifically, but extradata could be converted. With other codecs the issue is actually that the lavf mov demuxer just doesn't make the data available at all (this was discussed on the FFmpeg list some time ago, I think it that case it was mostly about palette data being unavailable).
-----Original Message----- From: mplayer-advusers-bounces@mplayerhq.hu [mailto:mplayer-advusers-bounces@mplayerhq.hu] On Behalf Of Michael Niedermayer Sent: 11 July 2010 21:54 To: MPlayer bug reports Subject: Re: [MPlayer-advusers] mencoder reads wrong frame rate flagfrom Quicktime files On Tue, Jul 06, 2010 at 04:16:52PM -0400, compn wrote:
On Tue, 6 Jul 2010 17:13:56 +0100, Dominic Bird wrote: [...] anyways, you can use the mplayer -demuxer lavf -identify -frames 1 to get the correct fps, then script it to use that in your mencoder line. it doesnt seem like a very efficient method, but at least it works.
fixing demuxer lavf for the binary codecs would seem like a nicer long term solution what is the problem?, extradata format? [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Its not that you shouldnt use gotos but rather that you should write readable code and code with gotos often but not always is less readable Is there any chance of the LAVF demuxer being able to use binary codecs?
participants (8)
-
Carl Eugen Hoyos -
compn -
Diego Biurrun -
Dominic Bird -
Michael Niedermayer -
Rafael Diniz -
Reimar Döffinger -
Shachar Raindel