View Full Version : About 1.0
gldblade
23rd November 2002, 19:19
We all know that XviD is currently split up between two branches: stable and development. We also know that the stable branch has had some things removed for the 1.0 release. Then there is the awesome development branch where new features are being added daily.
Maybe I just haven't been watching closely enough or maybe its because this board has been focusing more on the development branch, but it seems that there is a growing rift between stable and development in terms of features. So I pose the question, what's currently being done with stable?
How much of development is migrating over to stable? I know that QPel, B-frames and GMC is still highly experimental and thus shouldn't be transferred over quite yet. But since we're spending considerable amount of time working on these features, I guess there isn't much else that could be transfered over to stable. So does this mean that stable has undergone a virtual feature freeze?
Teegedeck
23rd November 2002, 20:01
Hi gldblade,
in the end it's up to the devels to decide where to branch off. AFAIK it's that simple: all features deemed stable will get included...:)
As for what's stable or not; there don't seem to be crashes with any of the new features, it's merely small problems here and there. GMC though is still a proof-of-concept as of this date. There are no advantages using it, yet.
Zarxrax
23rd November 2002, 20:49
gdlblade, you seem to be thinking of the stable and developement builds as two seperate projects. People dont need to *work* on the stable branch, they only have to work on the dev branch. When features in the dev branch become stable, then they can simply be moved over to the stable branch. :D
gldblade
24th November 2002, 06:00
all features deemed stable will get included...
Ah, I can see the day when XviD 1.0 is released. And then floods of people coming by and asking: hey, where's this feature?! Add it, now! :devil:
there don't seem to be crashes with any of the new features, it's merely small problems here and there. GMC though is still a proof-of-concept as of this date
I dunno. From what I've seen and heard, I'm not sure everything will stabilize in a month. We'll see.
I just realized something. New Years is XviD's first real deadline. Will our excellent developers be staying up that last week to get things done? :D
gdlblade, you seem to be thinking of the stable and developement builds as two seperate projects. People dont need to *work* on the stable branch, they only have to work on the dev branch. When features in the dev branch become stable, then they can simply be moved over to the stable branch.
Good point, but I guess this does mean that stable will lag behind development considerably. And, for now, this would mean that XviD stable is under a "feature freeze". That is, until something else is deemed stable.
I read today on the XviD-Devel Archives that a certain patch worked with XviD stable and not XviD devel. Oops? I hope this doesn't happen too often. Incompatibility and large differences aren't fun to work around...
sysKin
24th November 2002, 16:04
Actually, the branches idea is quite different.
The idea is: whenever we think that a codec is good at it's current state, we branch off and give it a version number.
First stable branch is 0.9 . We're not going to change this version unless we find bugs. The code is clear, with no unneeded parts, all documentation is done etc (all praise GomGom for this).
When we decide that current devel branch is really good and stable, we'll branch off again - to 1.0 this time. Again, we'll clean the code, find all bugs, write documentation etc.
This is how it's supposed to go :)
Radek
PS I don't know if you noticed, but since yesterday mpeg quant type works with bframes. Please take a look :D
Didée
24th November 2002, 16:13
Originally posted by sysKin
PS I don't know if you noticed, but since yesterday mpeg quant type works with bframes. Please take a look :D
HOORAY!
A binary, someone please build a binary for testing... !
Teegedeck
24th November 2002, 16:48
Hi sysKin,
did anyone have a look at the problem Koepi reported? I believe it's the same that has been brought up on this forum. I realized it first time with Koepi's and the insta-builds, curiously.
Yours,
Tee
gldblade
24th November 2002, 19:10
When we decide that current devel branch is really good and stable, we'll branch off again - to 1.0 this time. Again, we'll clean the code, find all bugs, write documentation etc.
Oh? Wow, that seems like a lot of work. :)
cjv
24th November 2002, 21:22
Originally posted by sysKin
PS I don't know if you noticed, but since yesterday mpeg quant type works with bframes. Please take a look :D
Wow! Just tested using b-frames and MPEG quant. Looks great..this is really great news!
Used b-frame offset@100 with 2-bframes. ffdshow reports b-frames, and the resulting file is larger and noisier than using h263 with the same settings, (so I think I activated it correctly.)
cjv
NoLogo
24th November 2002, 23:56
@sysKin:
On your site, there are two versions of XviD.dll: xvid-lm.rar and xvid.zip. What's the difference between them ? Or maybe this is just for developpers and not for testing...?
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.