More screwing around. Using the converter to make a 288x160 file, I get a lower framerate file that looks choppy. Using mencoder to make a 288x160, I get a high framerate file (same as original) that looks great, even fullscreen. I thought the converter was only supposed to step down framerate ABOVE 288x160. I'll be using mencoder for now. I'm using 288x160 and a video bitrate of 384. Looks pretty good. Would probably look better with 2-pass, but I have yet to figure an easy way to do 2-pass with one command and mencoder. I'm sure it's there, I'm just too lazy to figre it out.

If you let me know the exact settings, I'll add them as a preset to my console-based encoder - then you'll have a single command :-)

TIA,

Andrew

Andrew - What are the defaults used by your script for converting the videos? For example: bitrate(s), resolution, number of passes, crop image on, etc?

Thanks for making the script available!

The default preset is "smallest" which has:

smallest => { abitrate => 32, vbitrate => 80, width => 240 },

Maximum fps of 15, optimising by default, single pass by default.

Command line
 

Sorry it took me so long. I ditched my Nokia 770 and then got work to buy me one. :-)

Here's the command I'm using.

mencoder infile.avi -oac mp3lame -ovc lavc -lavcopts vcodec=mpeg4vbitrate=300 -vf scale=352:208 -ffourcc DIVX -o outfile.avi