Emulgator
11th March 2012, 14:37
Starting with http://forum.doom9.org/showthread.php?t=96516&page=55
AviSynth 2.60alpha2 on WinXP32 SP3
---------Originally posted by Emulgator---------
Hi, Zenitram !
A small suggestion to extend mediainfo's fps field to some more, maybe six or eight decimals:
I just came across a strange fps setting coming straight from a MJPEG in AVI canon camera file [Software Canon MVI02]
mediainfo showed 640x480x30,000 fps, and I thought: Well, let's make use of this stream as being 30fps.
Avisynth refused to concatenate this file with a blankclip(...fps=30...) saying that framerates wouldn't match.
Deeper investigations using abcavi showed [dwMicroSecPerFrame] 33333, Framerate 30,0003 fps
33333 µs presentation time breaks indeed down to a framerate of 300000/99999 or 30.000300003.... fps, so not compatible to anything.
(Assumefps (ntsc_video) and audio stretching in SoundForge to 100,10% helped here.)
If you need a sample, let me know, I will put up one on my FTP.
------------Originally Posted by Zenitram:-----------
My point of view is that the the frame rate is 30.000000000 fps.
The issue is that 30.000000000 fps = 33333 microseconds when rounded and saved into the file.
So there is no reasons to display more digits, I would put 30.000000000.
My point of view is that your software has a bug not "translating" 1/0.033333 to 30.00000000,
its rounding system is not good: to be exact, 1/0.033333 +/-0.0000005
(the precision of the value) --> 29.99985 < real fps <= 30.00075,
and 30.000000000 would be "valid"
(and is the expected value from the guy who wrote the file, I think)
-----------Originally posted by Emulgator------------------
This is about Avisynth. True, a valid point.
Since the given granularity is microseconds there should be no other choice on AviSynth's side
than interpreting the AVI-tagged 33333µs as 30.00000000000fps.
And BTW, for 30000/1001 fps the interpretation of the AVI-tagged presentation time of 33367µs (1s/29.9697305721221...)
as 29.97 fps works as expected in Avisynth .
AviSynth 2.60alpha2 on WinXP32 SP3
---------Originally posted by Emulgator---------
Hi, Zenitram !
A small suggestion to extend mediainfo's fps field to some more, maybe six or eight decimals:
I just came across a strange fps setting coming straight from a MJPEG in AVI canon camera file [Software Canon MVI02]
mediainfo showed 640x480x30,000 fps, and I thought: Well, let's make use of this stream as being 30fps.
Avisynth refused to concatenate this file with a blankclip(...fps=30...) saying that framerates wouldn't match.
Deeper investigations using abcavi showed [dwMicroSecPerFrame] 33333, Framerate 30,0003 fps
33333 µs presentation time breaks indeed down to a framerate of 300000/99999 or 30.000300003.... fps, so not compatible to anything.
(Assumefps (ntsc_video) and audio stretching in SoundForge to 100,10% helped here.)
If you need a sample, let me know, I will put up one on my FTP.
------------Originally Posted by Zenitram:-----------
My point of view is that the the frame rate is 30.000000000 fps.
The issue is that 30.000000000 fps = 33333 microseconds when rounded and saved into the file.
So there is no reasons to display more digits, I would put 30.000000000.
My point of view is that your software has a bug not "translating" 1/0.033333 to 30.00000000,
its rounding system is not good: to be exact, 1/0.033333 +/-0.0000005
(the precision of the value) --> 29.99985 < real fps <= 30.00075,
and 30.000000000 would be "valid"
(and is the expected value from the guy who wrote the file, I think)
-----------Originally posted by Emulgator------------------
This is about Avisynth. True, a valid point.
Since the given granularity is microseconds there should be no other choice on AviSynth's side
than interpreting the AVI-tagged 33333µs as 30.00000000000fps.
And BTW, for 30000/1001 fps the interpretation of the AVI-tagged presentation time of 33367µs (1s/29.9697305721221...)
as 29.97 fps works as expected in Avisynth .