XviD 1.0.0 now ready?

[virus]

hi!

I was browsing the CVS and noticed there's now a new changelog entry (http://www.xvid.org/cvs/chora/cvs.php/xvidcore/ChangeLog?login=2) for XviD 1.0.0 final. It was added a few hours ago. Looks like the bitstream has been frozen to version 34, too. Does that mean that the long-awaited final build is ready and due in a few hours/days?
This would be great :)

virus

[bob0r]

[22:15] *** [#xvid] Requesting topic...
[22:15] *** [#xvid] topic- 'Stay tuned for good news'
[22:15] *** [#xvid] topic- set Sun 9th May 2004 01:10a

It should come soon i guess :D

[celtic_druid]

Just did a compile and the about box says version 1.0.0 ("xvid-1.0.0")
vs. say version 1.0.-123 ("xvid-1.0.0") for RC4.

[gatormac]

C'mon baby. I'm shaking with anticipation.

And then please immediately add a VBV patch ;)

[virus]

Originally posted by gatormac
And then please immediately add a VBV patch ;)
This raises a question: are they going to backport patches to the 1.0 tree (releasing, say, version 1.0.1, 1.0.2 and so on) or the changes will be applied only to the 1.1 tree? If so, maybe we'll need to go through a new series of betas/RCs before enjoying new features in a "stable" build.

BTW I think they're taking extra care for the final release. Maybe they're testing the definitive build by Koepi internally... this release is going to gain some (highly deserved) attention over the Net so everything should work well ;)

virus

[CruNcher]

Or maybe there will be another feature hmm who knows :D
damn wait and wait and wait :rolleyes:

[gatormac]

I don't see why they couldn't make additions to the 1.0 tree....however I really don't care just so long as it is released (soon) with VBV applied. I have several projects on hold (and quit encoding at all basically) as manually limiting bitrate spikes is too much of a pain in the a**.

[timeismoney]

By a strange way I got XviD-1.0-09052004 Final Release

Not bad, but Brightness is still locked...

[gatormac]

We've been in RC4 stage longer than any beta or RC to date. I'm starting to convulse already. I need my fix of something new ;)

[Doom9]

And then please immediately add a VBV patchIf you need it, why not code it yourself? To the best of my knowledge this is all but trivial so it'll take a while to be done.

[BoNz1]

Originally posted by Doom9
If you need it, why not code it yourself? To the best of my knowledge this is all but trivial so it'll take a while to be done.

Gruel is coding it and it is already in the cvs sort of 2pass2 cvs log (http://www.xvid.org/cvs/chora/co.php/xvidcore/src/plugins/plugin_2pass2.c?login=2&r=1.1.2.38) see also XviD mailing lists. Apparently he had a some problems with it so the current cvs version does not work properly.
@ all, not sure how many times it has been said but there is a feature freeze, I almost wonder if someone actually has to spell out what that means because people still complain about the lack of vbv and brightness in XviD 1.0. These things will be in releases after 1.0 and are based off the same development tree as 1.0. In fact brightness, deringing all the things people seem to be complaining about (with exception of vbv) are already there.

[gatormac]

Originally posted by Doom9
If you need it, why not code it yourself? To the best of my knowledge this is all but trivial so it'll take a while to be done.

If you're going to quote me at least include the intent of the post which is the ;) at the end of it. Leaving the light-hearted, winking smiley face off the end leaves a completely different impression than the original message and is misleading.

I'm excited about the new XVID final being released soon. Is that a crime? I would like for VBV support to be included soon. Is that a crime? There was nothing in my post that necessitated any smart-aleck remarks about becoming a programmer. Whether it is trivial or not is subjective, but if it takes a while to get done that is fine with me because as I have stated in numerous posts I truly do appreciate the time and effort of the developers in making such a fine encoder, especially for the price. I do appreciate the time and effort that you have made in creating and maintaining the DOOM9 site and forums.

However, I do not appreciate the "code it yourself" responses, especially to a post as lighthearted as the one in question.

@ bonz1

You posted right when I was posting this. I understand the freeze and realize that no additions are coming until after the 1.0.0 final release. That is why I am excited to see the final released....new stuff to tinker with! VBV being one of them hopefully!:D :D :D :D (is that enough smileys for people to understand that I'm not griping or complaining?)

[BoNz1]

Originally posted by gatormac
@ bonz1

You posted right when I was posting this. I understand the freeze and realize that no additions are coming until after the 1.0.0 final release. That is why I am excited to see the final released....new stuff to tinker with! VBV being one of them hopefully!:D :D :D :D (is that enough smileys for people to understand that I'm not griping or complaining?)

Hehe, there's nothing wrong with wanting to play with new stuff. Sorry, that statement should have been directed at timeismoney.

[virus]

Originally posted by BoNz1
These things will be in releases after 1.0 and are based off the same development tree as 1.0.
:confused: don't know, syskin said that now the CVS HEAD points to the 1.1 tree, not to the 1.0 one. This is because the 1.0 tree is based on dev-api-4, which cannot support things as the brightness control (API change required, as they said). I think any feature that can work with dev-api-4 can be added easily to both trees, though (and released _after_ 1.0.0 is out, of course).

[BoNz1]

don't know, syskin said that now the CVS HEAD points to the 1.1 tree, not to the 1.0 one. This is because the 1.0 tree is based on dev-api-4, which cannot support things as the brightness control (API change required, as they said). I think any feature that can work with dev-api-4 can be added easily to both trees, though (and released _after_ 1.0.0 is out, of course).

Yes, they are different branches that were split some time ago from dev-api-4 which eventually became 1.0 branch. That is why I said *based*.

[hajj_3]

apparently 09/05/2004 1.0.0 final is this: http://en.fixdown.com/softdown.asp?id=7784&soft=down8

guess the real final must be very soon !

[communist]

Originally posted by hajj_3
http://en.fixdown.com/softdown.asp?id=7784&soft=down8

Linky not worky for me :confused:

[Gaia]

Originally posted by hajj_3
apparently 09/05/2004 1.0.0 final is this: http://en.fixdown.com/softdown.asp?id=7784&soft=down8

guess the real final must be very soon !

Stop posting links to chinese warez sites.

[virus]

guys, if you need a copy of the sourcecode for XviD 1.0.0 you can grab it at Edouard's site (http://ed.gomez.free.fr/projects/xvid-1.0.0/). This is the copy which will be uploaded at xvid.org soon.

[amango]

I have installed the free "Visual C++ Toolkit 2003" (only command prompt-version). Is it possible to compile XVID with this free compiler from Microsoft? How exactly?

[Koepi]

Just wait a few hours more and you'll get a nice, "commonly" bundled installer binary :)

If you don't mind I'll close this thread soon.

Regards
Koepi

[Sharktooth]

<---- Waiting.

[virus]

Originally posted by Koepi
If you don't mind I'll close this thread soon.
thanks for answering Koepi, we are all waiting for this thread to be closed (together with the "Hola!" one) ;)

[timeismoney]

Originally posted by Gaia
Stop posting links to chinese warez sites. I just wanna you stop you racial talking!

[Gaia]

Originally posted by timeismoney
I just wanna you stop you racial talking!

What are you talking about? Racial? Fixdown is big Chinese warez site. Read the rules. No links to any illegal material.