Quote:
Originally Posted by the_provider";p="
Greetings.
I believe I could use some suggestions. I use ViDrop and in it you have the option to create batch jobs. That is when one can see all the command lines(here is an example: mencoder "D:\jay.leno.2008.07.11.michael.caine_convert ed.avi" -idx -forceidx -ovc xvid -xvidencopts bitrate=250:me_quality=6:max_bframes=0:quant_type= h263:turbo:nochroma_me:notrellis:vhq=0 -vf-add scale=-2:256 -vf-add crop=320:256 -vf-add expand=320:256:-1:-1:1 -vf-add eq2=1.1:1:0:1.2:::: -ofps 25 -oac mp3lame -lameopts cbr:br=128:mode=1 -af volnorm=2:0.25 -af extrastereo=2.5 -srate 44100 -o "D:\\jay.leno.2008.07.11.michael.caine_conver ted_converted.avi" -vf-add harddup -noodml -of avi) that would be used for each video file due for conversion.
Well, here I start with some questions:
Q1. If manually modify the command lines from notrellis to trellis and nocroma_me to croma_me, does that have any real and positive impact on the process?
Q2. Mencoder uses only 1 processor my Core 2 Duo computer that actually makes the whole process longer...can this be improved?
And of course any other suggestions would be welcomed.
I am looking forward to hearing from you.
Best regards.
|
trellis slows things down, but doesn't need any extra support for playback (unlike things like qpel) so unless you're in a hurry, I'd turn it on.
More recent builds of xvidenc allow threads=2 to be added to the -xvidencopts for multithreaded encoding: I'm unsure whether this scales up to 3/4 or beyond