similar to: State of CVS?

Hi all, I started testing the RC1 encoder at ftp://sjeng.sourceforge.net/pub/sjeng/oggdrop.exe (based on branch_monty_20010708) On the songs I have tested so far (not much :) I did not hear any stereo issues, but there are some very noticeable problems with the produced files. Songs without much high-end will suddenly have one when encoded. (you'd expect it the other way around) It

Yes I know this question has been asked many times, but since Monty said that RC1 will be released in July (actually a pre-release should happen before that), and since the month is almost over, is everything still on schedule or is RC1 going to be delayed? -- Vorbis Xtreme | http://solair.eunet.yu/~aldov/ Ogg Vorbis is the free, open source alternative to MP3 --- >8 ---- List archives:

I wanted to ask if it is safe to encode my files with encoder compiled from nightly CVS archive? -- Pagarbiai, Algirdas Kepeþinskas [algis@kitoks.lt] [QQuxa@irc.delfi.lt] [UIN 14187537] / Padariau zodyje MAMA keturias klaidas... gavosi ALUS / --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message

As far as I can see, transcoding could be usefull for people who do not primarly care about quality but about filesizes. One could assume that such a user would have a collection of mp3's at 128kbps or higher bitrates, and uses an encoder like BladeEnc or Xing. He wants to take uses of ogg's supposed quality and transcode his 128-or-higher files into 96 or 112kbps oggs to save diskspace.

Hi! I am very pleased with the progress that Ogg is making, expecially after I read the latest comparision tests on http://ff123.net/128test/instruct.html that put OGG on top aside with MPC. BUT the APPLAUD.WAV test case ( http://lame.sourceforge.net/download/samples/applaud.wav ) still produces **VERY** easily audible high-frequency artifacts when encoded with OGG RC3 up to q4.9 (!!!). Things

Hi, In case no-one had mentioned it before, the current CVS won't encode mono files. It bombs out with a segfault in _vp_quantize_couple(). Program received signal SIGSEGV, Segmentation fault. 0x40039328 in _vp_quantize_couple (p=0x8079d78, vi=0x8052a48, pcm=0x80ae9f0, sofar=0xbfffef54, quantized=0xbfffef64, nonzero=0xbfffef84, passno=0) at psy.c:1038 1038

Go monty! jack. ----- To: cvs@xiph.org Subject: [xiph-cvs] cvs commit: vorbis/vq huffbuild.c latticetune.c make_residue_books.pl Date: Sun, 3 Jun 2001 22:50:13 -0700 (PDT) From: xiphmont@xiph.org (Monty) Precedence: bulk Reply-To: cvs@xiph.org xiphmont 01/06/03 22:50:12 Modified: lib codebook.c codebook.h floor0.c mapping0.c os.h res0.c vq

I downloaded a nightly CVS tarball about a week ago. It contains an oggdec tool in vorbis-tools. However, I don't get this tool when I checkout / update from CVS. What's the deal - is it in CVS or isn't it?! :) -- -:-:- David K. Gasaway -:-:- XNS : =David K Gasaway -:-:- Email: dave@gasaway.org -:-:- Web : dave.gasaway.org <p><p>--- >8 ---- List archives:

I tested Vorbis encoder - beta3 version, and here are my thoughts: - In comparison to beta2, subtle high-frequency artifacts seem to be gone (though they were small in beta2). Good job there! :-) - Velvet.wav also sounds better, but transparent quality is reached at -b256+. - Horn.wav still sounds very sucky, mode -b256 gives ~100kbps (this is understandable because in this sample practically

Hey, Maybe you guys remember us, I'm from the Neuros forums. I've got to say, having a player that supports Ogg Vorbis has really turned things around for everybody. We're still struggling with higher bitrate Vorbis streams, but that is only because of our terribly underpowered DSP. Anyway, to the point of my email. Recently the discussion of bitrate peeling has been floating

Hi! >From http://www.vorbis.com/stereo.psp : "Oggenc's default choice varies by bitrate and each mode is selectable by the user" So, how am I supposed to do that? E.g. what do I have to do when I want an 128kbps .OGG using lossless stereo, or does this "selectable by the user" mean only that I can choose the stereo mode indirectly by choosing an appropriate bitrate?

We're there. The decode engine with all 1.0 features is finished and in CVS, tagged as release candidate 1. CVS mainline head and the current nightly snapshot will get you the latest and greatest. Next, we continue work toward rc1 of the encode side. Monty --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this

We're there. The decode engine with all 1.0 features is finished and in CVS, tagged as release candidate 1. CVS mainline head and the current nightly snapshot will get you the latest and greatest. Next, we continue work toward rc1 of the encode side. Monty --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this

Hello everyone, ff123 compiled Monty's branch of the RC1 encoder, see his post on r3mix.net forum: http://66.96.216.160/cgi-bin/YaBB.pl?board=c&action=display&num=994299736&start=30 Anyway it only supports ~128kbps mode, so I did a quick listening test with some files that bugged vorbis beta4. grace.wav - the right channel is still a bit watery, and I think this can be seen

I'm trying to clean up CVS, getting everything where it should be, because pretty soon we're going to have to build SDK's and whatnot, and I want that to be easy. We're basically going to have 3 libraries: 1) libogg 2) libvorbis 3) libvorbisfile I have separated libogg out from the rest of the code, cleaned it up, got it doing 'make dist' and rpms and imported this into

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2000-07-19 at 11:06 Monty wrote: >I'll have to give things a look later/tomorrow to make sure nothing >'bad' (tm) crept in. I know, for example, that the books involved >are likely not exactly what I wanted to be using, but should be OK. >Specifically, the lsp12 and 30 codebooks are gigantic and the mode >description

> > vorbisfile.o needs to be removed from the lib/Makefile in LFILES since > > vorbisfile.a is a seperate lib now. As it stands I get unresolved > > symbol errors when linking with them, so this is a fairly important fix. This is an error in the build, yes, but I don't see why you'd get unresolved symbols. *unused*, yes, but not unresolved... > > sharedbook.c

monty didn't post, so i thought i would. he's been hand editing cvs to recover some history after my build changes. if you notice anything wierd, it's probably not just your computer :) i already noticed that the huff stuff got weird. :) jack. --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list,

Hi folks, some notes about goings on. After opportunity to think aloud, I have the pieces of the VQ system more or less in place. I need to finish the codebook generation core (this is not libvorbis code, but an external utility). I then need to write the encode/ decode/packing code that makes use of the codebook. This future code is already specced. Tony: I haven't worked on the xmms

Hi folks, some notes about goings on. After opportunity to think aloud, I have the pieces of the VQ system more or less in place. I need to finish the codebook generation core (this is not libvorbis code, but an external utility). I then need to write the encode/ decode/packing code that makes use of the codebook. This future code is already specced. Tony: I haven't worked on the xmms