> Once it encodes real bitstreams (the currently missing part)Am I correct in assuming that it will also be able to decode bitstreams? Tony Arcieri --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/
The 2.0 release at my Day Job is winding itself up so I finally have cycles for libvorbis and the player again. I'm seriously considering just doing Vorbis full time, funding or no :-) In any case, I'm going to push off all the aggressive, unfinished features I've played with for the time being and institute a (personal) feature freeze in the interest of finishing the coder block for Vorbis. Once it encodes real bitstreams (the currently missing part), I'll come back and play with continuous balance and things of that nature. Monty --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/
> > Once it encodes real bitstreams (the currently missing part) > > Am I correct in assuming that it will also be able to decode bitstreams?Yes, of course :-) Monty --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/
Well, I noticed the list sort of died down, so I thought I'd submit my quota of useless traffic... Any rough ballpark estimates on when the coding code should be completed? I've been talking with various people (namely Peter Alm with xmms) about "vorbis enabling" their projects... but it is somewhat difficult to do considering the only example source I have to look off of doesn't work :) If encoding actual bitstreams does not loom in the not-too-distant future, perhaps you can provide eager developers such as myself with a little more information about the API? Tony Arcieri --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/