About 1.0

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.

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

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

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