View Full Version : First XviD public release is out !
bergi
27th November 2002, 10:46
Just looked at XVID.org and found this (http://www.xvid.org/modules.php?op=modload&name=News&file=article&sid=21&mode=thread&order=0&thold=0)
@Koepi
Do you make an other stable build with this version? The stable build on your page is realy outdated.
Koepi
27th November 2002, 10:49
The build on my site isn't outdated - nothing changed in the code, it's just some source comments which were added since then.
Regards
Koepi
glenn
28th November 2002, 12:40
** offtopic: What a fantastic avatar, Bergi! C64 Power! :D
Daelin
29th November 2002, 03:19
Originally posted by Koepi
The build on my site isn't outdated - nothing changed in the code, it's just some source comments which were added since then.
Regards
Koepi
Would that be the stable build dated 2002-10-04, or the unstable development branch dated 2002-11-25, which lists b-frame fixes among its updates? :rolleyes:
Koepi
29th November 2002, 09:31
Trust your eyes!
stable tree has no bframes.
The Belgain
29th November 2002, 13:54
So let me get this straight, the stable build labelled from 04-10-2002 uses the same source that XviD just released today as libxvidcore 0.9.0?
Does that mean they haven't actually made any changes to the stable branch in over a month and a half?
Teegedeck
29th November 2002, 15:15
Originally posted by The Belgain
So let me get this straight, the stable build labelled from 04-10-2002 uses the same source that XviD just released today as libxvidcore 0.9.0?
Does that mean they haven't actually made any changes to the stable branch in over a month and a half?
Koepi:
nothing changed in the code, it's just some source comments which were added since then.
iwod
30th November 2002, 14:18
oh.... so i have been fooled
Koepi
30th November 2002, 14:43
Ok, if you really want to know:
"they" took out code which was experimental, and just left in the stable features. Those unstable features had to be activated by intention, so they're NOT used in my 0410-build.
The sources are just cleaned up. The features were stable back then and are stable AND readable/clean now. The api has been overhauled to reflect those changes.
So - all things that don't affect encoding quality or anything like that, it's more important for programmers to know that the API is cleaned up, too.
*sigh*
Koepi
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.