View Full Version : lowest fps when using ConvertFPS
nessusing
17th March 2006, 23:23
when i try to encode a clip using MeGUI from its original 25fps down to 12.5fps for my cellphone playback, MeGUI returned an error message indicating: (using convertFPS)
"ConvertFPS: new frame rate too small. must be greater than 16.6666 increase or use 'zone='"
so is there another way that i can reduce it lower than 16.6666?
and what is zone?
berrinam
18th March 2006, 00:19
If you want exactly half the framerate, why don't you just use SelectEven()?
nessusing
18th March 2006, 00:52
thx for the input. as i am still new to avisynth scripting(just started yesterday), i didnt know there was such filter.
the reason i chose 25/2fps was simply becuase i thought it would make the calculation eaiser on the avisynth and encoder side, kinda the idea i tried to mimic what SelectEven() does only that i didnt know such filter before u pointed out to me, thx!
however, what if i want to choose other frame rate, like 15,18 or something. is there another filter which can go below 16.6666?
nessusing
18th March 2006, 01:06
i dont know if i should open another post for this question, i will just try to post within this one:
what is the difference between the following 4 fps converting filters:
assumeFPS
AssumeScaledFPS
ChangeFPS
ConvertFPS [yuy2]
from their descriptions, it seems that assumeFPS/AssumeScaledFPS are the same and ChangeFPS/ConvertFPS are the same, except converfps needs yuy2 support.
this is confusing to me.
Wilbert
18th March 2006, 01:35
AssumeFPS changes the framerate by speeding up (or slowing down) your stream. No frames are added or removed.
ChangeFPS changes the framerate by deleting or duplicating frames.
ConvertFPS changes the framerate by blending frames. The avs docs isn't totally clear on this, but note that the total frame count changes here.
AssumeScaledFPS is not really important here. It is basically a shorthand for
AssumeScaledFPS(clip, mult, div) = AssumeFPS(clip, clip.FrameRateNumerator*mult, clip.FrameRateDenominator*div)
nessusing
18th March 2006, 01:51
hi, wilbert. sorry for all the trouble again, but i still dont get those commands. as you wrote above, what are FrameRateNumerator*mult and FrameRateDenominator*div?
all i did was like assumeFPS(myDesiredFPS) or changeFPS(myDesiredFPS). and they all ended up stopping rendering video when reach (or close to) 1000 frames. so is there a defualt number of frame limit in those command when rendering?
Wilbert
18th March 2006, 12:09
so is there a defualt number of frame limit in those command when rendering?
No.
all i did was like assumeFPS(myDesiredFPS) or changeFPS(myDesiredFPS). and they all ended up stopping rendering video when reach (or close to) 1000 frames.
Do you mean that the encoded video has only 1000 frames? If so, what's the number of frames of your source?
nessusing
18th March 2006, 21:51
yes wilbert thats what i meant, the total # of frame of my source is 88876 frames and length is 59:15:04.
but somehow i think i fixed the issue. i just pressed "queue analysis pass" b4 i enqueued the job, and it worked. although i still dont know what that option does, and it was not mentioned in berrinam's MeGUI guide.
Mug Funky
19th March 2006, 07:55
btw, if you want to get convertfps type conversion on any framerate (and faster, and in YV12 space), try clouded's (mg262's) motion plugin - it contains a filter called "blendfps"
nessusing
19th March 2006, 08:24
thx "Mug Funky". As i forgot to mention i used changeFPS instead of convertFPS in order to avoid the lowest framerate limitation. but sure i will look into the motion plugin u mentioned. thx!!
can someone still explain to me what "queue analysis pass" does in MeGUI? and should i use it everytime when i encode something? and should i ask this in MeGUI section? :P
foxyshadis
19th March 2006, 08:35
It's so the codec (or script) can do 1st pass without any output file. Are you sure it wasn't because you, say, forgot to run a first pass and were using an old stats file, made off a 1000 frame video?
nessusing
19th March 2006, 08:40
It's so the codec (or script) can do 1st pass without any output file. Are you sure it wasn't because you, say, forgot to run a first pass and were using an old stats file, made off a 1000 frame video?
I used CBR mode in Xvid, i thought that was only a one-pass process mode.
speaking of that plugin u mentioned, i just download it from avisynth website, there is no documentation came with the .dll, so how am i suppose to know what command to call in avs? any ideas?
foxyshadis
19th March 2006, 08:53
http://people.pwf.cam.ac.uk/mg262/posts/Motion/motion.html
and
http://forum.doom9.org/showthread.php?t=101859
nessusing
19th March 2006, 09:06
thx foxyshadis for the fast reply!! supporting YV12 is nice!
berrinam
19th March 2006, 12:21
at "queue analysis pass" does in MeGUI?It's for two-pass AviSynth scripts (not for codecs, foxyshadis). If you don't know what they are, don't use them. It's got nothing to do with one pass/two pass XviD encoding.
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.