XviD-27072002-1

[Koepi]

Hi folks,

Foxer and I had some hours chat again and here's the result, an improved 2pass curve treatment (again) :

Changelog:

XviD-27072002-1:
- EPSZ(^2) Motion Estimation activated
- New curve treatment revised, should work even better now.

You'll find two new fields in 2pass tab.

One where you can enter a threshold below which keyframe occurences will be treated as consecutive keyframes, Those keyframes get some bitrate reduction except the last keyframe of such a series, which gets "full quality" again. This should help low bitrate conditions a lot.

Please, test this build, I even took the time to correct the behaviour if you want to naviagte with the tab-button on your keyboard ;)

Best regards,
Koepi

[Surreptitous]

Koepi,

You Are Great !!! I Finished A Test Last Night , Comparing SBC 2pass , Div5.02 2pass , An Xvid 7-23-02 2pass /with new curve treatment . I used Decomb3.8 , SSHiQ AviSynth Filter , An BicubicResize 512x384 , In An AVS Then Converted Source To HuffYuv . An Then Started Testing . Div5.02 Had Quater Pixel , Bi-Directional Encoding An I Changed Max Quant To 8 . NanDub Used AntiFreeze , 25% moition Based Curve , LumA Correction , Bit Reservoir Modulation Enabled . Xvid Used Luma Masking , H.263 , Hinted ME , An High Alt. Curve Aggresion . There Was Absoluly NO Comparison , The Newest Xvid Build Is Absolutely The BEST . An I Would Also Like To Thank You , Koepi , For Your Efforts Put Forth An Given To The Testing Community . :)


PS : I Like Your Site Changes !

[Koepi]

Wohoo,

I'm impressed :)

Thank you very much for testing (thank god it went well ;) ) with these immense efforts, Surreptitous!

I'm glad you like it (as well as my new site layout ;) ). I think you'll be even more impressed by the new build, but don't feel like you have to test it this way again!

Thanks a million again,

best regards,
Koepi

[Surreptitous]

I Still Have The 16Gig HuffYuv Source Of The Movie `The One` Which I Like To Test With , Cause It Has Alot Of Action , Stop Motion 360 Scenes , Like The Matrix . An Is Only A 1hr30min Long So It Can Easily Fit On 1Disc . An You Can Bet Ill Test The New Build Out Tonight An See If I Can Tell The Difference Between build 7-23-02 An 7-27-02 . Keep Up The Good Work . :)

[Emp3r0r]

Koepi: i haven't encoded anything yet with the new build as I already have one going, but I did notice some GUI bugs which are nothing more than visual. The inset 3D frames are displayed on top of the text. Previous build was ok. Just letting you know even though it has no importance whatsoever.

[zulu]

Koepi: i haven't encoded anything yet with the new build as I already have one going, but I did notice some GUI bugs which are nothing more than visual. The inset 3D frames are displayed on top of the text. Previous build was ok. Just letting you know even though it has no importance whatsoever.


yes, i can confirm this.

@ koepi:
thanks for sacrificing friday night in favour of a new,improved build :D

i'll test it tomorrow.

[Koepi]

thanks for sacrificing friday night in favour of a new,improved build


well, this is a sad story as my GF is on vacation for > 2 weeks now and it will take another 6 weeks until she returns. So nothing really left except for work, work and work a little more to confuse my thoughts.

But this is no post that's meant to make you feel sorry, because I have some success story to tell...

I tried to encode R2 Rush Hour 2 at 704x304, heading for 1 CD (using trbarry's simpleresize filter and english burnt in "subtitles", but just the translations of the parts where they're speaking chinese, and using 2 languages as audio, english and german. so the movie shouldn't exceed ~632MB)... and the result is amazing. Nearly no blocks, even in the fast motion scenes, real fancy details (the leather jacket of chris tucker when he goes to the casino and in many places more),...

I think _now_ XviD can really compete very well in the highest league! Even without bframes (they don't give good results either, just take a look at DivX5, the bframes are butt-ugly), qpel (will come soon and improve quality just another bit) and GMC (once more doesn't help quality noticably).

Thanks for your feedback people, let it all out here :)

Best regards,
Koepi

[BiaTch 5.0]

:) :D :p

[roy]

Everything fine but I can't open Koepi's site. What's going on?

[Nic]

Well done Koepi (love the new site BTW) :) Im off for a week now....

(im looking forward to having QPel... :) (although it might be a little way off))

-Nic

[TripleA]

TAB works!!

Thank you ever so much for taking the time to fix it, Keopi.

Now, I've managed to fit Terminator 2 ESE (544x224) on a single 800MB CD with the July 20th build (I think, anyway: the older build that had consecutive KF handling). No blocks to be seen anywhere. Very acceptable quality. I was very surprised with that since GKnot told me I'd need 2 CDs for it. The first time I get away with disregarding GKnot's recommendations.

Of course, I cannot be sure it's because of the new consecutive KF handling code since DebugView won't run on my PC, for some reason (just hangs if I run it. I already had the latest ver and reinstalling didn't help (no corrupt .EXE, so)), but I plan on some test encodes using older builds once I have some free time.

Will let you know.

[Pasqui]

Hi Koepi,
Using Mozilla 1.1 beta, I cannot access your web site: I get an "Error 404 - File not found" error. I did not have this problem with previous version of Mozilla (1.1 alpha) nor with IE.
BTW, I love your new builds ! 23072002 build did a wonderful job on Ali and I 'm gonna test your new build. Do you intend to add Nic's filter in your package ? (it was not present in 23072002-1 one)
Cheers,

Pasqui.

[Erbse]

good work !

is it right, the color of your webpage ist grey / white ?? (opera)
looks strange :(

[sillKotscha]

hi Pasqui,

I think this is a problem of mozilla ("since the day they've put the dl manager control in the settings there have been ZERO changes in mozilla" - doom9: http://forum.doom9.org/showthread.php?s=&postid=157958#post157958)

and as you can read on Koepis site:

This referer-check has some disadvantages: some browsers don't send a referer and you get redirected to an error-page. Plenty people use download managers and didn't switch on to transmit a referer, in such a case the file you want to download doesn't get delivered, too. In such cases try to use another browser or work without a download manager, the files are very small and can be downloaded without problems even for modem users.

guess what?...

[Swede]

I've made some tests this morning and must say that the quantizer-distribution seems to be much-much 'smoother'. Using Matrix and comparing this build aginst the '20072002' shows a clear difference when stepping frame by frame, so this is definately a step in the right direction.

Well done.

[Easy123]

@Koepi

I can only say "GREAT WORK DONE!". I did a test and converted "The Last Castle" 124min 2CD / AC3 and there are no Macroblocks! The Quality is really amazing... Perhaps I will try and squeeze it to one CD with MP3...


Thx Dude...

CU
EASY123

[MoonWalker]

Some question :p

1)The min I-frame intreval should be 1 or it doesn't matter..
2)what are the <<suggested>> values for Below i-frame distance and I-frame bitrate reduction? I am thinking 5/20??

Thanks,
MoonWalker

BTW I confirm the bug in the GUI..

[Koepi]

Yeah, I have that bug in the GUI as well. That happened as I resorted the tab-order... dunno how to solve it :-(


suggestions:
1) Min iframe interval shouldn't matter anymore with this curve treatment, you can set it to one (but you should raise the reduction value then!)

2) I tested the code with iframe distance 10 and reduction 50.

This works very well for one cd encodes.

You have to realize that the code is a little sophisticated: if there _are_ p-frames within consecutive keyframes (well, those we treat like them due to the iframe threshold span above), the reduction is less. if we have the sequence I-P-I , redutcion 50%, iframe distance threshold 10, the first keyframe would still get 75% of the toal bitrate as the p-frame can compensate as well!

I hope this helps,

best regards,
Koepi

[MoonWalker]

Just for clarification...

If we set the threshold to 10, I-frames the are 10 or LESS in distances whould be treated as consecutive and the first one will get the reduction???

MoonWalker

[Koepi]

Now it starts getting nerve-wasting... :P

I-1-2-3-4-5-6-7-8-9-I

That's 10. ok? ;)

Regards,
Koepi

[cjv]

I just finished a 2CD encode of "Spy Game" (I love that movie) with the new build..the result is UNBELIEVABLE!!! You'd be hard pressed to say whether you were watching the actual DVD or this encode, and that's 2 feet away from the monitor :)

Ran the first encode through debugview and decided to cap I & P at 2-4.
My only question..approx 15% of the I-frames were encoded at quant 4, whereas with previous builds they never went above 3 on this movie?
This is only on paper, though, you can't argue with the visual result..it looks amazing.

Bitrate approx. 1300, 192 vbr MP3.
MPEG quant, ME, I & P 2-4, Medium curve 300-99
I-frame distance 5, reduction 20.

Koepi you're doin' amazing work..thanks!

cjv

[Koepi]

Hehe, thanks!

But don't forget that foxer did the actual implementation, I just forced him to do so ( I had more radical ideas how to calculate that, but he did it nicely with his existing code and just added that) ;) Well, I did the GUI stuff, implemented a proof-of-concept "cc kf"(consecutive keyframe) treatment,.. It's foxer's work you're encoding with though, thank him!

Thanks foxer!

Regards,
Koepi

[BiaTch 5.0]

Koepi,

What settings should I be using for 1cd encodes? Aliens(Hardest to encode movie) turned out not good 800MB better with older build I used:

first pass
H.263
ME

Second pass
modulated
lumi
Min I 2
Max I 4
Min P 2
Max P 4
ME
Curve Agression Low
High Distance 150
Low Distance 50
Max bitrate 4000

Can anyone tell me what is/how to use DebugView.

[Emp3r0r]

Second pass
modulated <-- best?
lumi <-- recommended always good?
Min I 2 <-- is this good
Max I 4 <-- with this?
Min P 2 <-- what about
Max P 4 <-- this?
ME
Curve Agression Low <-- best curve?
High Distance 150
Low Distance 50
Max bitrate 4000 <-- will higher degrade quality?

It's been a while since I read options exlained.. so can someone supply some wisdom? We are talking about 1CD or 2CD, and any differences between them.

Praying to XviD Gods for direction.

Do the XviD Gods prefilter (http://forum.doom9.org/showthread.php?s=&threadid=28127&perpage=40&pagenumber=2)?

[BiaTch 5.0]

Please, please don't say there is no one setting, what about a best for most movies setting? , we need what ever Guidance you can give.

[TripleA]

Originally posted by Koepi
Yeah, I have that bug in the GUI as well. That happened as I resorted the tab-order... dunno how to solve it :-(


Well, since I was (the?) one who asked for the "proper" TAB functionality I feel a bit guilty. So here's what I think:

Assuming the 3D-bezel-thingy is a GUI element same as the textboxes and whatnot, it seems to me Windows draws the GUI elements in some order somehow related to their resource-number (or whatever it's called) order. So take a look at the numbers and move the affected checkboxes to the other side of the affecting 3D thingies (make them higher if they're lower now or lower if they're higher now).

Of course that may very well re-break TAB functionality and I'm not sure how much you'll enjoy re-fixing that. So alternately PM me with how to:

0) Compile XviD (I have VS6 with SP5 and VS.NET).
1) How to set the GUI element order.

...And I'll see if I can fix that.

P.S. On second thought, I probably will find 0 with a search here so scrape that.

[The People's Elbow]

...aren't there enough threads around in this xvid section dealing with 1/2CD basic settings?

@BiaTch 5.0:
1. There is no alwaysfancyandabsolutelyoutstandingworking setting for all movies! (except setting minQ & maxQ @2 and to stop bothering about the filesize!)
2. Setting minQ and maxQ @ 2/4 is stupid... at least for P-Frames! Let the damn codec decide where to put in high quantizers and where not, it's the way it works best, if you go for a fixed size! maxQ4 is an overkill for high motion scenes!
3.By the way... this thread is about the actual build and not about some general encoding guidelines! Don't post such questions here, plz!!! Because they have been answered so many times by koepi or other skilled encoders.

@XviD Developers:
Superb work guys, keep on going! :D

PS: @ BiaTch 5.0: Leech DebugView start it then start the encode and do something like ... :eek:

greetz, Elbow!

[BiaTch 5.0]

Then can you tell me/guide me on how to calculate the right setting for each movie?, thanks.

[MoonWalker]

About the quants...

My opinion is not to cap them...Just leave I-frame 2/31, P-frame 2/31...

MoonWalker

[Koepi]

Yeah, quantizer restrictions _shouldn't be_ necessary with the new code, but I still feel like I need them for tweaking (Iframe quant range 2-5, pframe quant range usually 2-10, maybe even 16).
This always helped mne in situations where really nothing was left for the curve treatment other than use higher quantizers and the result might look blocky.

Btw, capping the bitrate to 4000 and so on is odd, I really had a good laugh when I saw those settings as that definatly is a setup that ruins your encodes :)
Just use alt curve compression with default values, this works like charme with normal encodes (curve aggression medium, low/high distance 300).

Regards,
Koepi

[soujir0u]

Hi, I'm a bit confused. I thought with the new curve treatment, we should use the normal curve compression (not Alt CC)? Or am I wrong?

[Koepi]

Use whatever you like! It shouldn't be of too much importance, but I didn't verify that yet. Please try and post the results :)

Regards,
Koepi

[BiaTch 5.0]

Originally posted by Koepi

capping the bitrate to 4000 and so on is odd, I really had a good laugh when I saw those settings as that definatly is a setup that ruins your encodes :)


This is where I got that from:

http://forum.doom9.org/showthread.php?s=&threadid=29221&pagenumber=1

Pretty dumb on my part, now I know why so many frames where so blocky, the encoder was chocking.

[MoonWalker]

Some results about the new build :

My settings :

Motion : 6
Quant Type : 1-Pass(H.263), 2-pass(Modulated)
Max I-Frame Interval : 300
Min I-Frame Interval : 1

Min/Max I-Frame : 2/31
Min/Max P-Frame : 2/31

I-Frame boost : 20
Below i-frame distance : 10
I-frane reduction : 40

Alt-CC Used :
High : 200
Low : 100
Aggresion : Med
Strength : 50
Max Bitrate :10000
Max/Min Overflow : 60

Credits :
I/P-Frame Quant : 31

Desired Filesize : 581625 Kb
Actual FIlesize : 581828 Kb


Some blind results :)



DebugView analyzer for XviD codec v0.81 by MoonWalker
e-mail : s_ilias@gmx.net


Quantizers Analisis
---------------------

Quantizers Used For Movie :
------------------------------
Quant 2 Used : 3973 Times, Percentage Used : 2.13%
Quant 3 Used : 119133 Times, Percentage Used : 63.99%
Quant 4 Used : 58333 Times, Percentage Used : 31.33%
Quant 5 Used : 4662 Times, Percentage Used : 2.50%
Quant 6 Used : 86 Times, Percentage Used : 0.05%
Quant 7 Used : 1 Times, Percentage Used : 0.00%

Average Quantizer Used for Movie : 3.343

Quantizers Used For Credits :
--------------------------------
Quant 31 Used : 9967 Times.

MPEG Quantization Type Used 133073 timed, Percentage Used : 67.84%

H.263 Quantization Type Used 63082 timed, Percentage Used : 32.16%

Quantizers prevented from rising too steeply 17 times


Intra-Frame (Key-Frame) Quantizers
------------------------------------

Movie
-------
Quant 3 Used : 2533 Times, Percentage Used : 76.02%
Quant 4 Used : 181 Times, Percentage Used : 5.43%
Quant 5 Used : 569 Times, Percentage Used : 17.08%

Credits
---------
Quant 31 Used : 49 Times, Percentage Used : 1.47%

Inter-Frame (P-Frame) Quantizers
------------------------------------

Movie
-------
Quant 2 Used : 3973 Times, Percentage Used : 2.06%
Quant 3 Used : 116600 Times, Percentage Used : 60.47%
Quant 4 Used : 58152 Times, Percentage Used : 30.16%
Quant 5 Used : 4093 Times, Percentage Used : 2.12%
Quant 6 Used : 86 Times, Percentage Used : 0.04%
Quant 7 Used : 1 Times, Percentage Used : 0.00%

Credits
---------
Quant 31 Used : 9918 Times, Percentage Used : 5.14%



Frame Analisis
----------------

Number Of Intra-Frames (Key-Frames) : 3332
Number Of Inter-Frames (P-Frames) : 192823
Total Number Of Frames : 196155

1.70% of the Movie is Intra-Frames (Key-Frames)
98.30% of the Movie is Inter-Frames (P-Frames)



Size Analysis
----------------

1-Pass Size : 1111719411 Bytes or 1085663 KBytes
Scaled Size : 590876040 Bytes or 577027 KBytes
Actual Size : 590978520 Bytes or 577127 KBytes
Compressibility : 53.16%
Quality of XviD avi : 59.82%

Visual Quality :

Less Macroblocs than previous version but some weird shifting in the backround(at least to my eyes :p)

Some Notes :

1)I got very much consecutive I-frames..See pics 1.jpg and 2.jgp here http://www.geocities.com/aleksikerayno
2)The Encoding ended with -102480 overflow
Here are the last lines :

00196203 7218.45336488 [4084] 2nd-pass: quant:31 MPEG inter stats1:91 scaled:91 actual:91 overflow:-102480 credits
00196204 7218.46550497 [4084] 2nd-pass: quant:31 MPEG inter stats1:91 scaled:91 actual:91 overflow:-102480 credits
00196205 7218.47687038 [4084] 2nd-pass: quant:31 MPEG inter stats1:91 scaled:91 actual:91 overflow:-102480 credits

MoonWalker

[Koepi]

Hm, that background shifting can derive from noise in the original source.
But the overall visual quality should be good-very good.

I still hope you like it ;)

Regards,
Koepi

EDIT: setting iframe boost to 10% might help quality in your case as well... 20% with many cc kfs can take up real many bits...

[MoonWalker]

What about the overflow? Is it normal??

The weird is that I have done the same movie with a previous build of yours(XviD-22052002-1).And the maximun quant was 16 for p-frames and the overflow was normal (about 13000, not minus)...

Thanks,
MoonWalker

[Koepi]

well, 130kb off is point-accurate for my taste, sorry...

But the explanation is easy: since the first pass is done in h263 and the second pass id moudlated, the credits are encoded using MPEG quant type (haven't looked in that code to figure out why it's doing that). This is enough for the size to vary if you use fixed quant. for the credits.

Regards,
Koepi

[Acaila]

@Koepi:

Although it is indeed strange that Modulated results in MPEG quants for credits, it IS actually the better choice. With any quant over 15 MPEG is almost always smaller than H.263, and that's exactly what most people want: small credits. Please don't change this.

[MoonWalker]

I have done The Matrix for 2-CD rip..

My settings :

Motion : 6
Quant : MPEG
Max/Min I-Frame Interval:300/1

Min/Max I Frame quant :2/3
Min/Max P Frame quant :2/5

I-frame boost : 30
Below I-frame distance : 5
I-frame reduction : 10

Aggr : Low
High/Low : 300/100
Strength : 50

The log :


DebugView analyzer for XviD codec v0.81 by MoonWalker
e-mail : s_ilias@gmx.net


Quantizers Analisis
---------------------

Quantizers Used For Movie :
------------------------------
Quant 2 Used : 143974 Times, Percentage Used : 77.33%
Quant 3 Used : 42199 Times, Percentage Used : 22.66%
Quant 4 Used : 15 Times, Percentage Used : 0.01%

Average Quantizer Used for Movie : 2.227

Quantizers Used For Credits :
--------------------------------
Quant 31 Used : 9968 Times.

MPEG Quantization Type Used 196156 timed, Percentage Used : 100.00%

Quantizers prevented from rising too steeply 0 times


Intra-Frame (Key-Frame) Quantizers
------------------------------------

Movie
-------
Quant 2 Used : 3137 Times, Percentage Used : 94.77%
Quant 3 Used : 3 Times, Percentage Used : 0.09%

Credits
---------
Quant 31 Used : 170 Times, Percentage Used : 5.14%

Inter-Frame (P-Frame) Quantizers
------------------------------------

Movie
-------
Quant 2 Used : 140837 Times, Percentage Used : 73.03%
Quant 3 Used : 42196 Times, Percentage Used : 21.88%
Quant 4 Used : 15 Times, Percentage Used : 0.01%

Credits
---------
Quant 31 Used : 9798 Times, Percentage Used : 5.08%



Frame Analisis
----------------

Number Of Intra-Frames (Key-Frames) : 3310
Number Of Inter-Frames (P-Frames) : 192846
Total Number Of Frames : 196156

1.69% of the Movie is Intra-Frames (Key-Frames)
98.31% of the Movie is Inter-Frames (P-Frames)



Size Analysis
----------------

1-Pass Size : 1208014667 Bytes or 1179701 KBytes
Scaled Size : 1066939637 Bytes or 1041933 KBytes
Actual Size : 1066946899 Bytes or 1041940 KBytes
Compressibility : 88.32%
Quality of XviD avi : 89.81%


Visual Results :
I haven't seen better quality than this...I have tested it with acaila's filter chain and the visual quality was outstanding...

The only thing I didn't like is that I got 155 I-frames at the credits.(Maybe a bug???)

MoonWalker

[Acaila]

Looking at the quant distribution you ended up with you could have restricted I-frames to 2 and P-frames to 2-3 :)

But basically if you get a distribution, and an average, like that it means you should go for 1 CD instead of 2 ... either that or increase your resolution a notch or two.

[dread]

Originally posted by MoonWalker
The only thing I didn't like is that I got 155 I-frames at the credits.(Maybe a bug???)

Weird, I've got about 30 i-frames for credits (about 5 mins, movie Last Castle). Maximum i-frame interval 250.

[kastro68]

I think I am experiencing the background shifting too. Well I don't know what it is called exactly, but the the scenes with minimal movement are a bit watery/shaky/nervous.

Is B-frames supposed to be disabled for this build? Because the B-frame function appears grayed out for me.

Ja

[Koepi]

Jupp, no BFrames or SMP support within this build (bframes are too early stage for a real public test, as you can read in the response to them already - they're overated anyways, they don't help quality much, most likely they degrade it... but they result in "better" keyframes once they're finished, and that's what people think of as "better quality" with divx5 IMHO, at least the bframes themselves are butt ugly...).

Well, this can be due to noisy sources as I wrote or it can be caused by EPSZ motion search, which gruel said it's not complete yet (but for my taste the result looks better). If you switch back to PMVfast you'll experience a lot of other things moving around where this doesn't belong... Just search for that in this forum, that's the reason why I eneable EPSZ ME.

Regards,
Koepi

[MoonWalker]

Originally posted by Acaila
Looking at the quant distribution you ended up with you could have restricted I-frames to 2 and P-frames to 2-3 :)

But basically if you get a distribution, and an average, like that it means you should go for 1 CD instead of 2 ... either that or increase your resolution a notch or two.

Yes I know, I should have raised the resolution.I always go for 2-cd rips cause I use the AC3 sound(I have a DD theater system).But I don't think that, this justifies so many concecutive I-frames, especialy at the credits.

EDIT :

@Koepi
Has this build have Nic DSF??Cause I get the first frame not exactly solid green(like the bug) but vertical green and black stripes..

MoonWalker

[canadian_fbi]

there was a bug i found some time ago with credits encoded at a high fixed quantizer where it would sometimes put in a bunch of i-frames mistakenly. for more info on this, go here:
http://forum.doom9.org/showthread.php?s=&threadid=24687

hopefully this is what you're talking about...

[Koepi]

MoonWalker,

NO, Nic's DSF isn't included. Use ffdshow to decode your vid (and make sure to switch on "use xvid dll" as well for that).

The problems you can see might be due to bugs in your avisynth filters, if you set the cropping to strange values the filters sometimes produce buggy output. It's no error of xvid if you use resolutions multiple of 16 (as stated in MANY threads already where people where reporting their wrong settings as bugs).

Regards,
Koepi

[MoonWalker]

Originally posted by Koepi
MoonWalker,

NO, Nic's DSF isn't included. Use ffdshow to decode your vid (and make sure to switch on "use xvid dll" as well for that).

The problems you can see might be due to bugs in your avisynth filters, if you set the cropping to strange values the filters sometimes produce buggy output. It's no error of xvid if you use resolutions multiple of 16 (as stated in MANY threads already where people where reporting their wrong settings as bugs).

Regards,
Koepi

Well, I have read the post (I remember div2 for crop, 4 for resize)..Here is my avs..Can't find any "bugs"...


LoadPlugin("D:\DivX\GORDIA~1\mpeg2dec.dll")
LoadPlugin("J:\Cnr2.dll")
LoadPlugin("J:\TemporalSoften2.dll")

Source=mpeg2source("J:\Matrix\matrix.d2v").crop(0,79,718,418)

LumaFiltered=Source.TemporalSoften2(1,5,25)
ChromaFiltered=LumaFiltered.Cnr2().MergeLuma(LumaFiltered)


Movie=ChromaFiltered.Trim(0,186188).BicubicResize(640,256,0,0.5)


Credits=Trim(Source,186188,0).TemporalSmoother(10).BilinearResize(640,256)

Return Movie+Credits


Thanks,
MoonWalker

[MoonWalker]

Hmm...This bug I say maybe it's a bug of Bsplayer(never said it was a bug of Xvid)..Because when I play the avi at WMP it's ok...So sounds like BSplayer's bug..

MoonWalker

[ookzDVD]

@MoonWalker,

So... I think now it's time to upgrade your BSPlayer to the latest one
0.85 build 490 ;)

[MaTTeR]

I've done a lot of testing the last several days with this build and I have to say my rips have never looked better. This new curve compression is amazing to say the least. I use to see a few macroblocks on dark walls but now even they are gone. I just ripped "Savior" to an 800MB CD with 256kbps AC3 and it's the best rip I ever seen even when compared to the DVD source. Great job guys!

The only thing that I have noticed is the frames or background sort of jumping around. This is happening on the last 4 DVDs I ripped and cc/altcc settings doesn't seem to affect the jumping frames. Over all the quality is amazing though:D

@uManiac
If your reading this, your SMP build link seems to be invalid. Maybe you set this purposely until the next build?