QuEnc 0.60 Released!

New XviD Ratecontrol in 2 Pass mode!
Added a MPEG-1 System mux mode
Can apply pulldown to the encode
Bug fixing...More stable (for use in more than one instance of QuEnc, etc)
Tooltips
A bunch of other stuff I'm too ill to remember

Have fun

-Nic

EDIT:
Just release 0.61! Slight bug in the MPEG-1 System Mux was fixed.

weeeee!  thanks, nic.

Great!

Unfortunately I did my last full-dvd-encode just yesterday and I've no projects on hold, so it needs some time until I can test it

Thakns for your work Nic!

Cheers
Koepi

Yaaay! Congrats! The only MPEG-2-encoder I'd ever use turns 0.60!

a milestone indeed. Nic releases a 0.60 version. seems he has overcome that demon.

Great! I have 4 SVCDs to encode for a friend and I just started the first pass on the first disc with 0.59 - might aswell abort it and use this version

Quick test with a few small test files: No more crash when running several instances in 2pass mode. Quality seems as good as with 0.59b4 if not slightly better.
Thank You

I have same problem with previous version. When i encode this CLIP, the encoded video has one frame less than source.

Thanks

Great!! Excellent!

Thank you Nic!

[]'s

Originally posted by Affar
I have same problem with previous version. When i encode this CLIP, the encoded video has one frame less than source.

Thanks

AFAIK this is not a QuEnc bug but a VfW / B-frame issue (the 'B-frame decoder lag' message).

Hey NIC thank you !!! With you and Hank who needs more to use not freeware MPEG2 encoders?

Thank you, Nic.
Will test soon.

@Affar: When I put that AVI clip in VDub, it says it has 149 frames. When I encode a M2V file and run it through BitrateViewer, it says it has 149 frames too. What discrepancy are you seeing and how do I replicate it.

-Nic

I dont know where is the problem, but this persist in 3 diferent pc.

ERROR with this scripts
(avisynth 2.5.5 + ffdshow october 2005 + xvid 1.1)

Avisource(quot;O:\error_db.aviquot;)
BicubicResize(352,576,0,0.50)
ConvertToYV12 ()

Directshowsource(quot;O:\error_db.aviquot;)
BicubicResize(352,576,0,0.50)
ConvertToYV12 ()

Quenc configuration:

quenc.exe -i quot;script.avsquot; -o quot;O:\error_db.m2vquot; -b 1600 -maxbitrate 2500 -dc 10 -priority 4  -2 -mpeg2 -hq -vbr -scene -notrell -nocgop -nointerlaced -noextreme -gopsize 15 -maxbframes 2 -nocmatrix -aspectratio 4:3 -mpeg2mux noaudio -auto -close

And bitrateviewer says... 148 frames

any suggestions?

Awesome.  I love this encoder.  Can't wait to try out the new version.

And bitrateviewer says... 148 frames

yes i got that but look at the number of pictures read, 149.

i tested the .avs with Tmpgenc 2.5 and MainConcept 1.4 aswell and guess what, exact same results.
mpeg stream eye says 149 frames for all of them by the way.

also tried loading the avi in to Tmpgenc and it said 177 frames. tried MC and it said 149 but actually encoded 1 less (147 frames, 148 pics read in bitrate viewer). weird avi.

so sorry but this is not a QuEnc problem since the other encoders are encoding exactly the same.

Nic,
I have a question for you: can you explain what algorithm
you use to calculate the SCR?
In mencoder I used a series of tricks (
something similar to: for every pack scr = Gop initial pts + (delta data/ N) where N is the sum of video and audio data I'm about to mux
), but I realize it's a flawed and too simplistic method.

Often it works well, but sometimes audio pts diverges too much from scr;
additionally it's impossible to manage multiple audio tracks.

I'm looking for better alternatives.

Thanks.

@unifxs: Thankfully libavformat takes care of it for me  SCR is a pain, I remember coding ReJig and that being one of the most difficult problems for getting DVD compatability just right. I honestly can't remember that much about it now. Sorry. I remember MPUCoders forum had a nice thread on it once.

-Nic

Next version will probably be 0.60 which will have Beta 3's 1st Pass RC and XviD's 2 pass RC. -Nic

Just did a 1 pass VBR encode with 0.61 which came out way undersized (2.52 GB instead of 4.7 GB). As far as I remember my 1 pass encodes with 0.59 Beta 3 always came out right, only Beta 4 1pass VBR was broken.

Another question about the new tool tips:
Scene Detection --- Bad for DVD encoding
Closed GOP    --- Recommended for DVD encoding

From my experiences with CCE just the opposite should be true.

Cheers
manolito

@manolito:
1Pass VBR has always been a bit flaky, due to it's very nature. 2Pass is definitely the way to go. 2 Pass also enable the XviD ratecontrol. But I'll look into seeing what I can do.

quot;From my experiences with CCE just the opposite should be truequot;
What experiences are those? Could you elaborate. In reality any which way should be fine. Scene Detection can cause bizarre GOPs (i.e. very short GOPs) that a DVD player might not like, but I'm sure most don't have a problem. Closed GOPs are useful for seeking, but aren't necessary. Share your experiences...Are you talking from a quality point of view? If so, then closed gop = false and scene detection = true would probably equate to better quality.

-Nic

ps
@dgz: What changed between beta 3 amp; 4 again? I can't remember
(Ok, time for me to start using a CVS or at least write a changelog)

just my humble opinion

Scene Detection --- A few dvd players may not like it 100%
Closed GOP --- Only required for multi-angle DVD encoding or editing

What changed between beta 3 amp; 4 again? I can't remember

for 1 pass encoding nothing. however what you could try is changing
lmin = 1 * FF_QP2LAMBDA;
to
lmin = 1;
or
lmin = 0.6 * FF_QP2LAMBDA;

since if you remember the use of lambda caused undersizing with 2 pass for over about 4000Kb/s.

actually, just looking, i see you have lambda in the low bitrate setting aswell so would probably want to change that aswell. so either = 2 or = 1 * FF_QP2LAMBDA.

Ok, time for me to start using a CVS or at least write a changelog

since you used to go over/erase versions changes when you did a new one in the same thread a lot of what was changed when was lost. it would be handy though.