View Full Version : The present of XviD?
Alxemi
10th September 2003, 12:32
Hi all!
I start this post asking about the actual state of the xvid codec...
Is the development of devAPI3 reaching the end?
Will be more API3 binaries?
And what about API4? I've found <a href=http://canalxvid.urbenalia.com/phpBB2/viewtopic.php?t=363>here</a> (Spanish xvid page) a Syskin-API4 build. Are we going to have here API4 binaries? Koepi/Nic/Umaniacs will work on it?
Maybe they are dumb-questions, but I'm confused on this particular and i couldn't find any information... :(
Thanks for the help, take care.
Alxemi
10th September 2003, 12:34
Sorry for the html code... I'm used to use it in other forums :scared:
sysKin
10th September 2003, 12:47
Originally posted by Alxemi
I start this post asking about the actual state of the xvid codec...
Is the development of devAPI3 reaching the end?
Will be more API3 binaries?I think so. Some dev-api-4 features made it into Koepi's dev-api-3 (trellis) but I don't think more will be ported. Maybe one "final" build ;) with some bugs fixed (compared to current devapi3). Dunno.
And what about API4? I've found <a href=http://canalxvid.urbenalia.com/phpBB2/viewtopic.php?t=363>here</a> (Spanish xvid page) a Syskin-API4 build. Are we going to have here API4 binaries? Koepi/Nic/Umaniacs will work on it?Developers don't want dev-api-4 builds to be published. I used to publish my builds (on irc channel, mostly) but I changed my mind and I don't. There are still too many problems and known bugs for it to be usable.
Once we get rid of the known and major bugs, I guess you should expect XviD 1.0RC1 :) :) I know you can't wait, just a bit more patience please :)
Radek
mf
10th September 2003, 12:51
Originally posted by Alxemi
Is the development of devAPI3 reaching the end?
Yes.
Will be more API3 binaries?
No.
And what about API4?
It is being stabilized at the moment. During this period normal users (non-testers) should stay with the last API3 build.
Are we going to have here API4 binaries? Koepi/Nic/Umaniacs will work on it?
Public API4 builds will be put up by respective build suppliers when API4 reaches public usable state.
Damnit sysKin, you beat me to it! :D
mmebane
10th September 2003, 19:10
What kind of testing needs to be done? I am doing DVD rips pretty much for the fun factor, so I wouldn't mind using a alpha/beta build and looking for bugs.
Enigmax
18th September 2003, 20:40
Why the developers do not want to make public the development? Between all we could find the Bugs more quickly.
Regards
superdump
18th September 2003, 21:23
To be fair, it is public. You can get the CVS whenever you like and compile it yourself if you wish to test it. Binaries aren't made available so that people don't start using dev-api-4 for archiving when things could still be wrong.
Animaniac
19th September 2003, 05:50
There's a good chance that there's nothing seriously wrong with dev-api-4 seeing as ffdshow (or another external decoder) can decode it correctly.
superdump
19th September 2003, 10:38
There is currently a bitstream bug which noone has fixed. BoNz1 and I have both encountered it.
Enigmax
19th September 2003, 20:28
O.K. Superdump.
Regards
Koepi
20th September 2003, 09:29
Well, that bug seems only to affect h.263/trellis/vhq. Still, noone's fixed it yet, but i fell over it too, let's see what happens ;)
Regards
Koepi
superdump
20th September 2003, 11:01
I've narrowed it down to VHQ and posted on the dev ML so it should get fixed soon. :)
EDIT: However, if you use VHQ + GMC, somehow GMC stops the bug from occurring.
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.