Sonntag, 27. April 2008

Yet another Xvid-build with a bugfix

As I blogged earlier, there was an issue with motion vectors (MVs), an array was too small so a wrong MV could have been chosen in some cases. Since those MVs are costly bitrate-wise, it should have happened very seldom.

I spoke to sysKin and he verified that this issue should be fixed, he also recommended using CVS head/main instead of "old" 1.1.3 nowerdays. Anyhow, I updated Xvid-1.1.3 and Xvid-1.1.3-VAQ. You can find the builds over on my homepage.

On a sidenote, today we made already over half an hour of sport, each one, my GF and I. If this keeps going on, that WiiFit-game would be a very nice investment! ;-)

Kommentare:

Anonym hat gesagt…

How come that softwares like GSpot & MediaInfo still detects encodes made with v1.1.3 as v1.1.2

Koepi hat gesagt…

Maybe those programs weren't updated since 1.1.2 came out...
Or since 1.1.3 just fixed a security issue, the bistream-version stayed the same and wasn't bumped up. I don't have the sources at hands here so I could verify that.

Cheers Koepi

Barough hat gesagt…

GSpot haven't been updated since February/March 2007, but MediaInfo was updated a couple of weeks ago.

Anonym hat gesagt…

Would be great if you could fix so that the bistream-version gets bumped up to v1.1.3 and maybe make a 'new' release.

topolinik hat gesagt…

Hi, there's a question about xvid i really don't know who to ask.
You wrote an xvid guide (it's now on the nic's page) and it's at version 1.3 but it's old, it was updated in 2002: what about latest xvid versions? Is there a reliable, full explanation of the many options xvid offers in the vfw interface?