XviD 1.0.2 bugfix release

[daldrum]

* Fixed non compliant bvop decoding (was using rounding=0 instead of rounding=1)
* Added better mv bound clipping for broken streams.
* Better behavior with content claiming not containing bvops but eventually having bvops.
* Force fincr and fbase to be < 16bit.
* Fixed thread safety problem in C language iDCT implementation.

more on xvid.org

[Koepi]

What's this thread supposed to do?

I'll upload a binary tomorrow, I still don't have internet at home (I'm moving to a new place currently).

So please be patient, those bugfixes are more than non-critical.

Regards
Koepi

[daldrum]

Sorry, just wanted to share the info.

[Sharktooth]

Celticdruid has 1.02 binaries ready on his site: http://celticdruid.no-ip.com/xvid

or mirrored here: http://ebola.gamersrevolt.it/XviD-1.0.2.exe

@Koepi: no hurry

[DanielSun]

Finally it comes...after nearly 2 months' waiting...Great!

[gamr]

ummmmm, i dont know what people are expecting but 1.0.2 wont give any major improvements, its a bugfix release, nothing more. if you want any sort of real differences you need to goto a 1.1 alpha build. if you want to try 1 try the url in my signature but dont expect a world of different of 1.0.1 to 1.0.2.

[symonjfox]

Originally posted by gamr
ummmmm, i dont know what people are expecting

Bugfixes and more stability

[easyfab]

Originally posted by gamr
... if you want any sort of real differences you need to goto a 1.1 alpha build. if you want to try 1 try the url in my signature but dont expect a world of different of 1.0.1 to 1.0.2.

Is there already a cvs branch for 1.1 existing ?

[celtic_druid]

The cvs head branch will eventually become 1.1.

[len0x]

Funny, the above build is being distributed on most download sites as "Koepi XviD 1.0.2 binaries", very few mention Celticdruid...

[BeerLion]

Originally posted by len0x
Funny, the above build is being distributed on most download sites as "Koepi XviD 1.0.2 binaries", very few mention Celticdruid...

It wouldn't be so if the naming convention like XviD-1.0.2-CelticDruid.exe or XviD-1.0.2-Koepi.exe was used.

[dragongodz]

It wouldn't be so if the naming convention like XviD-1.0.2-CelticDruid.exe or XviD-1.0.2-Koepi.exe was used.

or if people bothered to read who the binary was from before posting the link ?

celtic_druid - just wondering why you dont link the libguide.lib with your compile. that way you wouldnt have to worry about the libmdd.dll.

[celtic_druid]

I do have libguide.lib linked.

[dragongodz]

woops, sorry. i meant link libmmd.lib. then you should not need libmmd.dll in the installer.

libguide is for libguide40.dll which is the other one sometimes forgoten.

[celtic_druid]

It is linked to libmmd.lib. Has to be because of the symbol libbmmd_sse2_log (I think?). I could remove that then no need for libmmd anymore, no idea what impact speed wise if any that would have on SSE2 capable CPU's.

[dragongodz]

so you still need to include the dll even if you link the lib ? hmm i thought it would be more like libguide where if you link the lib you dont need the dll. the dll being an external form of the functions in the lib.

according to the intel compiler docs libmmd usage is caused by the use of the /md option so you could probably try compiling it without that and see if it still needs the dll aswell etc.

[Koepi]

It took me a whole week, but finally my build is up now!

Enjoy it!

Regards
Koepi

[geoffman]

Originally posted by Koepi
It took me a whole week, but finally my build is up now!

Enjoy it!

Regards
Koepi

YAY!

[obieobieobie]

Good show, Koepi!

[neo75903]

Originally posted by Koepi
What's this thread supposed to do?

no hard feelings, think daldrum was just trying to help until you are settled again

Hows your new place anyway?

Got binaries from your site anyway, i only use trusted sources