A 1.1 final version of Xvid,when?

[Kostarum Rex Persia]

When Koepi will finaly post for download final 1.1 version of xvid.

[unskinnyboy]

If you are really interested in following the development and keeping up with the news, subscribe to the XviD-announce mailing list - http://list.xvid.org/mailman/listinfo/xvid-announce, so you will know if there is a 1.1-final in the works. But if I am not mistaken, the next build will be 2.0.

[Sharktooth]

@Kostarum Rex Persia:

I think you are misunderstanding how things work with open source development. See, it's not like anyone has to do anything! Making suggestions is allright, but asking "when will we see ..." etc is sort of pointless because open source isn't really on any sort of schedule. It's sort of impolite to ask those questions.

Don't take this post the wrong way, I dont mean to attack you or anything, you just seemed confused regarding why people are responding the way they are.

Hope that helps :)

-MiSfit
Ok,I understand that.I appologize if I offend someone.
... ok ... what's the part you didnt understood then?

[IgorC]

Steps of evaluation of codec.
1. Alpha
2. Beta
3. Realise Candidate RC
4. Final version

Maybe there are some others between the general steps.

Xvid is on beta test. There is no even RC version. I'm waiting for a final 1.1 too. More than other video codec.

[celtic_druid]

There hasn't been much change to the cvs in recent months. In terms of a 1.1RC I am not sure if that is good or bad.

Your post makes it sound like 1.1 final was commited sometime back and that Koepi hasn't released a build yet. This is not the case.

[bond]

what difference would it make if xvid was labelled "1.1" or 3.0" or "3000" or "xp" or what else anyways...?

[communist]

Improved over previous versions ;)
Ie fixed bugs / higher quality / higher encoding speed / more features etc. I guess some people are just used to see XZY 1.0 then 6 months later 2.0 etc. just because Microsoft manages to release yearly iterations of basically the same stuff doesnt mean OSS devs should follow ;)

The 1.1 code needs testing / fixing, testing / fixing again -> repeat until no serious show-stopping bugs show up. Then they call it stable.

But since we're talking about OSS - remember they're doing it for free and in their free time - patience :)

[bond]

what "show-stopping" bugs do you know in xvid?

[communist]

Well I'm using 1.0.3 - so I dont know about 1.1. And I also cant remember any show stopping bug in XviD (once it went into 1.0 betas / RC etc.) but I can imagine there being problems with the rate control / mp4 compliant bitstreams / visual artifacts appearing at rare occasions (like the black blocks in libavcodec).

In other words I dont know about any show stopping bug in XviD - but dont you think the devs would term it stable if they thought it is?
;)

[unskinnyboy]

what "show-stopping" bugs do you know in xvid?
Dancing blocks in dark scenes (with/without AQ). :D

[DeathTheSheep]

Yes!! I thought my computer was "b0rked," but it was really the codec!! Well, I think with that low-bitrate tweaking, the B-frames couldn't be adjusted accordingly, so whenever a B-frame comes up, it displays a bit differently, with blocks in different locations. Also, the recent CVS is "b0rked" when it comes to encoding raw rgb32 in virtualdub 1.6.5.