similar to: new vorbis.com launched

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 know you're tired of hearing me complain about ogg123, but this time I noticed that some of the error messages are a bit inconsistant. Also, I noticed that some things (like "Error connecting to server") are fatal errors that kill ogg123, while I think they should simply go on to the next file in the list like "input not an Ogg Vorbis audio stream" does. Another problem

Here's yet another ogg123 patch that: 1) Adds a command-line parameter "--prebuffer n" or "-p n" that decodes "n" chunks into the buffer before even forking off the writer thread. 2) Moves the buffer_shutdown call in ogg123.c to its proper place. 3) Doesn't use signals ;) This way, the default behavior is to start playing immediately, while allowing the user

Looking at it, I think this patch is actually better than the one I sent before, mainly because it keeps from adding a bunch of weird parameters to functions at the expense of a single global variable (globals... ick). Aaron Plattner <HR NOSHADE> <UL> <LI>text/plain attachment: ogg123.diff.2 </UL> -------------- next part -------------- A non-text attachment was

I tried to use ogg123 -b to play from a slow HTTP server, and I realized that ogg123 starts to play immediately even if the buffer isn't full, so if it can't read the ogg fast enough it skips, even with a huge buffer. Is this the way it's supposed to work? It seems to me like the buffer shouldn't start playing until it's full. Am I misunderstanding the purpose of having a

Hi, I noticed there was some discussion on this list about the desire for ogg123 to support output to stdout via Sun's .au file format, so I decided to give implementing an AU driver for libao a shot. Here is my first attempt. To test the driver: * Apply the patch below (against ao in CVS) * Copy the attached ao_au.c into ao/src * Run ao/autogen.sh, compile, and

I have a small feature request for oggenc: Can a command line option be added to allow the user to set the first serial number to be used for the output ogg stream? This only takes a few lines of code, actually. Rationale: it is quite helpful for debugging other encoders. If oggenc is the "reference" encoder, ensuring that your new whiz-bang encoder has diffable output to oggenc is a

http://news.webnoize.com/item.rs?ID=11136 or Quietly Slipping into Audio Software, Vorbis Wants to Dethrone MP3 by Mark Lewis Confident they can oust the MP3 format from dominance, developers of Ogg Vorbis, an open-source, royalty-free audio encoding format, say they are making headway, getting their technology into software players, portable devices and

http://news.webnoize.com/item.rs?ID=11136 or Quietly Slipping into Audio Software, Vorbis Wants to Dethrone MP3 by Mark Lewis Confident they can oust the MP3 format from dominance, developers of Ogg Vorbis, an open-source, royalty-free audio encoding format, say they are making headway, getting their technology into software players, portable devices and

I'm updating my vorbis rpm spec file, and when I try to do "make -C vorbis-tools ogg123", due to rpm's build environment, I get lots of: gcc ogg123.o -o ogg123 -lm ../lib/libvorbis.a ../lib/vorbisfile.a ../lib/vorbisfile.a(vorbisfile.o): In function `_get_prev_page': vorbisfile.o(.text+0x54): undefined reference to `ogg_sync_reset' vorbisfile.o(.text+0xa9): undefined

Is anyone looking at bugs.xiph.org? There are several bugs that are easy to fix (bugs 2,3,4,7, and 9) or have already been fixed (Bugs 5 and 6). Bug 8 I think is a Multi/single -threaded issue and Bug 15 is a problem with ogg123, not with libao. Some of these bugs are pretty old. Is anyone going to fix them? I'd do it, but I don't have CVS write access. Aaron Plattner <HR

Greets, Every linux user that sets up a sound card using sndconfig heres Linus pronouncing "Linux" - I confess that's how I learned to pronounce it right, until then I prononced it 'l-EYE-nucks' - I was wondering - what's the correct pronounciation of 'Ogg Vorbis'? I pronounce it 'OOOg' (a long 'O' sound or a portuguese 'U' if you must

hello, I try to listen to the stream at http://ogg.radiostudio.org:8007/ostream.ogg with ogg123, it's a 44100/mono stream. It sounds to me like a mono file played as a stereo file. there are very often silent drop outs and the music is pitched. is this a bug in ogg123? I changed to stereo encoding and know it's better (normal pitch without silence), but I have klicks/scratches in

The first Ogg Traffic is out. This will be your weekly news/status summary of Ogg, Vorbis and related projects. Enjoy! The Ogg Traffic site: http://www.vorbis.com/ot/ The latest update: http://www.vorbis.com/ot/latest.html Comments and suggestions are welcome. jack. --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe

> to wait when called. I commented out the line where it calls > thread_mutex_lock and it all seems to work now. Ick. What a hack :) It does seem to be a deadlock issue. But I wouldn't recommend anyone trust just removing that. Locks are there for a reason :) jack. --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To

> Well I think the mutex has previously been locked in the code, hence the > reason it just waits when it gets to that particular piece of code. I > just found the problem, it's up to you guys to fix it properly :) Don't hold your breath. Icecast 1.x is basically deprecated at this point. We fix bugs that are easy, and deadlocks are usually pretty difficult. Icecast 2.x has

Following a few months of lurking on the list, and vainly trying to get vorbis to compile on os/2, I finally managed to get the nightly gzip from saturday to compile (fairly) cleanly, and so have finally been able to play with Vorbis on my OS of choice :) Using the EMX runtime system, and bash for OS/2 (along with a few ported GNU apps), both configure and make work fine (except for ogg123

I have got libao up to oggenc and ogg123 working on Mac OS X Public Beta now. I'd like to submit patches, but last time I did, they never got committed by anyone. Who is in charge of committing stuff? Does someone want to nominate themselves to review and commit my patches? The patches are briefly: - On Mac OS X dlopen() is not very well supported, so libao has been cleaned up a bit to

Well, this may not be unique to RC2. I believe this is the first time I have noticed it. It is definitely the first time I have vorbis encoded this song. Try encoding They Might Be Giants - Istanbul. Go to offset around 50 seconds. It should say "Maybe people just like it better that way." However, the maybe is pretty bassy (low pitch) and is just gone. Anyway, RC2 is so much

Hey. Last night I hacked grip so that it'd allow me to use vorbize and comments with grip. It's very ugly because grip'd need a bit of rearrangement in order to facilitate the way the vorbis comments work (that is, the comments are not added in after the encoded file has been written). Any one who wants to use it should patch grip-2.94 (http://www.nostatic.org/grip), and make sure you