new build 03-20-2002 xvid ????

[wing1]

What is going on with the new build? It seems like the bit bucket has a big hole in it. Data rate keeps on climbing no matter what quantizer or data rate you set it to. It Looks as if I am using Huffyuv codec to compress video :D The speed also decreased quite a bit on this new build. Went to uninstall the codec it says Koepi's 03-06-2002 build????

[Jaset]

Hi there folks,

i recently installed nic's latest build, dated 20th of march, and came across some strange behaviour I didnt expect. Before this codec I used koepis latest build which was this XviD-17032002-2.exe.
I encoded a movie after trying and finding out best settings for my specific needs. To go with the time and to do my part of reporting bugs and testing latest builds I decided to install nic's codec described above. I watched the movie again and experienced visible decreased quality especially on the very top/bottom of the actual image. I also checked for similar xvid ds filter settings. All the same as before but as result: degraded visible quality (like blocky disturbing fields in the image).

I also experienced the same problem explained by the guy before me!

Another question:
I read Doom9's article about proper XviD encoding and came across one thing I really didnt get so far. For his example he claimed its not nessasary to change the Min I-Frame Quant/Max I-Frame Quant/Min P-Frame Quant/Max P-Frame Quant settings under the Quantization Tab and leave everything default settings which are each 2-31 / 2-31 for P and I frames. I had to dramatically lower these to 1-3/2-4 to get appropriate results for a high quality rip. Indeed my filesize came out as calculated.

Any ideas?
Thanking in advance

[Acaila]

I would keep min/max I-frame on 2/3 instead of Doom9's 2/31. Because if the keyframe is already bad, the following P-frames will be even worse. The 2/31 for P-frames is alright, you wouldn't want to constrict it too much otherwise you'll get lower overall quality.

@Doom9:
Why did you suggest 2/31 anyays?

[Nic]

Could you please redownload from my site ( http://nic.dnsalias.com )

Errors & info:
1) The DShow errors were my fault should now be fixed

2) Speed should be fastest, could people please compare with the latest builds of uManiac & Koepi. It is the fastest on my Celeron 1000. Of course this is not a race, im just trying to find optimum params, once I have, Ill put them up here. Please test this for me.

3) The bit bucket thing, could be a CVS core problem, there have been a lot of little changes recently.

Cheers,
-Nic

ps
uManiac has got quite a few builds up at present to help with bug hunting....

[Jaset]

@nic:

DShow errors do not appear anymore... looks fine now, at least for me ;))


@Acaila:

I got much better overall quality with increased P-Frame quants, the range between 1-5 caused usable and satisfying results for me.


Cheers!

[The People's Elbow]

yep, DSF working 100% again...I knew that something wasn't right with it ;)
Speed seems to have improved very little - better than nothing :D
Keep up the good work Nic!

greetz from da Elbow!

[Nic]

Im glad to hear it....Speed hasn't improved much (i.e. you wont notice much in the fps counter :( ) but it should shave a few minutes in encoding movies...

Any more opinions, ideas noted problems....??? Please give as much feedback as possible, without it the bugs wont disappear :(
:)

Cheers,
-Nic

ps
Now I can make AviC take drag-and-drop files.....

[avih]

Originally posted by Nic
Now I can make AviC take drag-and-drop files.....
:D

[Nic]

:D The new build has now got drag-and-drop AviC. :)

[Belgabor]

This might be a player related problem, but the DSF settings don't seem to be remembered. Are they supposed to be? If not, some kind of 'Save Default'/'Save Settings' feature would be nice and very appreciated (my favourite player desperately needs the 'flip picture' option ;) )

Regards
Belgabor

[Nic]

They are saved in the registry...under local machine\gnu\xvid

It works fine on mine & Ive never had any complaints? Do you have admin rights on your computer? Have your tried it in Windows Media Player (preferably 6.4)? If you could answer & try those things, then get back to me that would help solve any problem.

-Nic

[Gabriel_Bouvigne]

Would it be possible for those settings to be saved in current_user?

Then upon reading, checking local_machine first, then current_user...

I think it could be annoying for a user (a user, not an admin) if each time he needs to set up parameters again.

[Belgabor]

Originally posted by Nic
Do you have admin rights on your computer?

Yep.

Originally posted by Nic
Have your tried it in Windows Media Player (preferably 6.4)?

Not yet, thats why i thought it might be a player related problem. I'll check it later when i get back home and post the results.

[wing1]

@nic

D/L new build and completely removed ( regedit / delete all mpg4 ) and reinstalled again.

Speed wise, it is now fixed ;)

However, Data rate is still running amuck 300+KB/s (105min+ is >2Gb file) and keeps on trucking :D no matter what I set it to: 1-pass CBR, 1-pass Quantizer, 1-pass Quality. Same goes for data rate, quantizer, quality, etc.

Removed current build and went back to 03-04-2002 and all is well.
Removed 03-04-2002 and installed 03-17-2002(Koepi) and all is well once again.

Both older builds have max data rate ~ 225KB/s ( < 1.4Gb 2CDs )

I noticed this issue when I saw instant builds on Umaniac's page. from 19th on. However, I saw that you and Koepi build them, I figured something have changed :D

I Currently am using 03-17-2002 build instead.

[Nic]

So both me & uManiacs build have this problem....if so that is a bug is some of the additons is core & ill try to track it down :)

Cheers for all the info,
-Nic

ps
I think that the codec also stores it in the local machine...& I just followed suit :)

[wing1]

@nic

I don't think Koepi updated his binaries to new build from CVS (Last I look b4 download your build, It's still 3-17-2002-2.exe). Otherwise, it would probably have the same issue. I am using the build from 03-17-2002( I think it's your build and not Koepi or maybe it is...I have to look......Too many binaries in Xvidstuff Directory: I labelled the binaries download with date-name just in case of that momentary laps of reasons :D )

[Doom9]

about the guide... certain changes have been made now. I'm still not in favor of manually changing quantizer settings, I tend to think that this is the codec's job but this is mentioned in the guide now.

[-h]

??

Working fine at my end.

I'm uploading some vfw stuff to CVS pretty soon, maybe recompiling will fix the other builds. Core seems OK too.

Heh oh well :)

-h

[Gabriel_Bouvigne]

I tryed encoding from VDub, in cbr or 2 pass vbr, and it always crash.
I also tryed without specific processor features, and it still crashed (integer divide by 0). I tryed both Nic and Koepi compiles.
It's strange as I'm using a very common processor (Duron)

In order to have a usefull bug report, I was wondering if I could download somewhere a debug version that could be a little more verbose with some assertions.

[uManiac]

You can get a debug version of the most current build on my page (http://www.heimsnet.is/kg) under instant builds. It's on the bottom of the page.

uManiac

[-h]

There isn't much by way of assertions in core (which is where this problem appears to be located), but a debug build should spew an ungodly amount of data into the dbgview log.

I must say I'm not sure where these crashes could be coming from..

-h

[Gabriel_Bouvigne]

I don't know either where they could come from, but I hope that right now I'll be able to have a usefull bug report in such cases.

Btw I think that the location of those debug builds should be indicated a little more, as it could be really usefull for reporting bugs.

[uManiac]

Btw I think that the location of those debug builds should be indicated a little more, as it could be really usefull for reporting bugs.

Actually I only added the debug build at 8:30 this morning... now you know where to get it if you need it :D

uManiac