gunnm
20th September 2003, 02:52
Wasn't sure where to post this, so sorry if it's in the wrong place :(
I have a couple of requests, both related to goofy framerate stuff. These both apply to the AVI2SVCD mode, but maybe they would be good for other modes too.
When a strange framerate is used, besweet seems to either crash or create a silent .mp2 file. Removing the -ota(...) part of the command fixes it. Could an option be added to automatically skip the -ota(...) part of the besweet command?
Also, when a strange framerate is used, like 119.880 (this is due to an avi that has seperate sections, some being 29fps, others being 24fps), a message pops up about it being incompatible and the avisynth script ends up with this line in it:
AssumeFPS(29.970,True)
This totally screws up the encode, resulting in a huge file that plays in slow-motion.
Using this line instead gives a very acceptable encode:
ChangeFPS(23.976)
It would be nice if an option was available to make this choice without having to edit the avisynth script.
--Edit--
Hmm...I'm having even more problems with another 119.880 fps video. Now, the encoding is totally borked. The effect is weird, sorta like the image is being smeared when movement occurs. This new problem happens in both CCE and TMPEG. These hack-job variable frame rate videos are really making life difficult for non-experts like me :(
---------
Above all, I would like to thank you for a wonderful program. You guy(s) rule!
I have a couple of requests, both related to goofy framerate stuff. These both apply to the AVI2SVCD mode, but maybe they would be good for other modes too.
When a strange framerate is used, besweet seems to either crash or create a silent .mp2 file. Removing the -ota(...) part of the command fixes it. Could an option be added to automatically skip the -ota(...) part of the besweet command?
Also, when a strange framerate is used, like 119.880 (this is due to an avi that has seperate sections, some being 29fps, others being 24fps), a message pops up about it being incompatible and the avisynth script ends up with this line in it:
AssumeFPS(29.970,True)
This totally screws up the encode, resulting in a huge file that plays in slow-motion.
Using this line instead gives a very acceptable encode:
ChangeFPS(23.976)
It would be nice if an option was available to make this choice without having to edit the avisynth script.
--Edit--
Hmm...I'm having even more problems with another 119.880 fps video. Now, the encoding is totally borked. The effect is weird, sorta like the image is being smeared when movement occurs. This new problem happens in both CCE and TMPEG. These hack-job variable frame rate videos are really making life difficult for non-experts like me :(
---------
Above all, I would like to thank you for a wonderful program. You guy(s) rule!