On Tue, 2003-12-16 at 23:17, Bernhard Praschinger wrote:
> > -M 0: 2m 11.9s
> > -M 1: 2m 10.6s, -1.3s
> > -M 2: 1m 27.7s, -44.2s
> > -M 3: 1m 26.5s, -45.4s
> That values look much better.  :-)
> Now you have seen the mpeg2enc can go faster.

It's like it used to be. :> I'm going to try it on a full video, with a
few options. I figure I'll let it run through 24 hours of encoding time
(about 6 different trials) and see how each result turns out, and so on.
I'll let you all know when it's done. :>

> I have tried the command you used on my machine, and I have seen the 
> same "problem". Also 3 processes and each only 33% .
> 
> (time lav2yuv n1000.eli | mpeg2enc -I 0 -f 8 -b 9800 -p -a 3 -o test.m2v
> -S 9999 -M 3 -g 9 -G 18 -4 2 -2 1 -r 32 -q 4 -Q 3.0 -K kvcd -R 0)

Yes.. So it's definitely the -R 0, but -R 1 is faster than the default
of -R 2 (i think that's the default?)

> > Note that I responded in an earlier message with a total of 24 timings
> > across -M 0-3 -I 0-1 -R 0-2 settings, which turned up some interesting
> > results that -M 3 -I 0 -R 1 worked fastest of all of them (same source
> > material I used for the above, and it took 51 seconds). So, I think the
> > -I 1 is on, which makes a huge boost in -M ratings from 0 to 3, but it
> > is still quite a bit slower than -I 0 (which I use since the input is
> > Progressive 23.976fps)
> Thats strange.

It makes a mild bit of sense.. But just a little.

> I'm just running some encodings to see which option causes the problem. 
> 
> On my machine the -R 0 caused the problem. If I used -R 1/2 or or R
> option, I got 3 processes each using about 45-50%. 

Which should total about 150% CPU instead of 99% that it uses with -R 0.

> > > My brain had given up the time I started my computer that evening ;)
> > Mine usually does that at about 8am. :>
> Just as you enter work ? ;)

Self employed, thereby just as I crawl out of bed, and it my brain stays
broken until about noon. That's what I get for staying up till 4am
playing with mpeg2enc. :>

> Encoding without the -R 0 seems to solve the problem, by now.

I'm going to see what speeds I get about halfway through a video, when
nothing from disk is in cache anymore, the encoders/decoders are in full
swing, and everything sort of settles down.. Should be interesting.




-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
Mjpeg-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/mjpeg-users

Reply via email to