similar to: Vorbis Tools are open!

Here is patch with manpages for ogg123(1), mp3tovorbis(1) and vorbize(1). Manpages are in pod format, because it is the most readable man source, and are compiled by pod2man. all and clean for man/ work. Install and uninstall for man/ seem to work. Manpages are GPLed of course. <HR NOSHADE> <UL> <LI>text/plain attachment: manpages.diff </UL> -------------- next part

I finally managed to compile ogg123 under MacOS X, after creating a PB project for it. Rillian, do you want to include the PB project in cvs? (it needs a LOT of polishing, though). ---------- Ogg123 from PACKAGE VERSION by Kenneth Arnold <kcarnold@arnoldnet.net> and others Usage: ogg123 [<options>] <input file> ... -h, --help this help -V, --version display

I've been trying to tackle the vorbis source. I ran across what I think is a missing dependency in the vorbis-tools directory. Since ogg123 and vorbize are staticly linked to libvorbis and vorbisfile, when those file change, the executables should be rebuilt. Below I've attached a patch. (I hope it works. I am sort of new to patch and diff.) BTW, I've been trying to find a good

A feature request that sounds reasonable and a bug report. ----- Forwarded message from Frank Klemm <pfk@fuchs.offl.uni-jena.de> ----- Delivery-Date: Sat Jan 6 06:35:21 2001 Date: Sat, 6 Jan 2001 15:26:43 +0100 From: Frank Klemm <pfk@fuchs.offl.uni-jena.de> To: xiphmont@xiph.org Subject: ogg123 X-Mailer: Mutt 1.0.1i For ogg123 I need the following feature: - Decode one .ogg file

I have having problems trying to take a file recorded with Monitor and convert it to MP3. When I use 'play' to play the .wav file, it sounds fine. After bladenc'ing it, it plays at lightening speed, and the voices are all high pitch. I tried using sox to resample to 32000 before encoding, but that didnt work either. Do any of you convert your .wav files to mp3? Monitor call:

In case there are any Debian developers around here, I wanted to point out message <20020828154322.GA15114@chulak.naquadah.org> on the debian-devel list this morning. Another Debian developer is proposing to submit an mp3->vorbis transcoding program for inclusion in Debian. I have objected to this on the grounds that the resulting vorbis files will sound like crap, and I have also pointed

I've been talking to some people about benchmarks for different operating systems and CPUs, and it would seem that a good way to gain some exposure for Ogg Vorbis would be to push oggenc as a benchmarking application when sites such as ExtremeTech, AnandTech, Ars Technica, etc. post system comparisons. I know that MP3 encoding is used as a common "media" benchmark, so it would be

When using the abx utility that is in LAME's misc dir, trying it on an ogg (with ogg123) gives the following output: Standard Open Source Bug detected, try murksaround ... (ogg123 is decoding to stdout) IIRC this also happened with older mpg123's but no longer with the latest release. Latest ogg123 from CVS still gives it though. Someone stole code but forgot to check for fixes? :)

Hi. When can we expect the next beta version of Vorbis encoder (with some tagging & encoding options I hope)? Also, today I tested MPEG+ encoder which you can download from http://www.stud.uni-hannover.de/user/73884/mppenc.zip (win encoder) http://www.stud.uni-hannover.de/user/73884/in_mpp.zip (winamp plug-in) http://www.stud.uni-hannover.de/user/73884/mppdec.zip (win decoder) It sounds

Hi everybody: Here is this week's Ogg Traffic. The HTML version is available at http://www.vorbis.com/ot/20030324.html Enjoy! <p>Ogg Traffic for Monday, March 24, 2003 [1]Carsten "Purple" Haese March 24, 2003 _________________________________________________________________ Table of Contents 1. Status Updates 1.1. Monty 1.2. Stan Seibert

I've put together a first cut for a Win32 DLL using the BladeEnc interface. Right now, it's just a drop-in replacement for BladeEnc.dll that ignores all encoding parameters passed to it and uses the info_A vorbis_info struct (same as the encoder_example). It's not particularly useful as of yet, but you can rename it to BladeEnc.dll and use it with any number of rippers out there

I just moved a bunch of shared code (like 4 copies of getopt) into a share directory within vorbis-tools. I also moved the UTF-8 code from oggenc into the vorbis-tools/share directory as well so that it could be used by all of the tools, since they all need to handle UTF-8 comments correctly. Header files for the shared code are stored in vorbis-tools/include. I have already fixed vorbiscomment

Why has ao been changed so that there are now two open() functions ? IMHO the original ao_open() was fine - if you wanted to set the filename for output, you could add an option via ao_append_option and if you wanted to avoid overwriting an existing file, you could stat() it yourself. Having ao_open_live() and ao_open_file() just makes more work for the user of the library for no gain, AFAICT.

Why has ao been changed so that there are now two open() functions ? IMHO the original ao_open() was fine - if you wanted to set the filename for output, you could add an option via ao_append_option and if you wanted to avoid overwriting an existing file, you could stat() it yourself. Having ao_open_live() and ao_open_file() just makes more work for the user of the library for no gain, AFAICT.

Okay, here's the patch that should fix byte-ordering madness. The basic rule with libao is that samples have to be in native byte order. All of the drivers will assume this, and libao provides a ao_is_big_endian() function for library clients (and sometimes drivers) to test their byte ordering. I would appreciate it if someone on a big endian platform test ogg123 and make sure that it works

Hi there. I have a short .ogg with Vorbis stream @56kbps from a 44.1 16bits stereo sample, which weights exactly 135'781 bytes. Packed to ZIP, it goes down to 109'485 bytes, that's a 80% ratio ! Even worse with latest RAR3 archive, with which the file size goes to 104'349 (76%). <sceptical> I admit this sample is a bit repetitive, but I guess the probability of having the

I recently bought a DVD Audio disc and I searched the web and wasn't really able to find much about DVD Audio and Linux. I have a few questions that I was hoping some people on this list might be able to answer. How can I extract the uncompressed DVD Audio (not the DTS Audio portion of the disc, but the 96khz/24bit/5.1 pcm part)?

Now that FLAC has officionally joined the Xiph family, there are three different free audio codecs, which can be stored/transported using the ogg container. Would it be possible to create an API and/or a library that would cover them all? If my understanding of the situation is correct, if an application wants to support vorbis, speex and flac, it has to use three different interfaces.

Now that FLAC has officionally joined the Xiph family, there are three different free audio codecs, which can be stored/transported using the ogg container. Would it be possible to create an API and/or a library that would cover them all? If my understanding of the situation is correct, if an application wants to support vorbis, speex and flac, it has to use three different interfaces.

Now that FLAC has officionally joined the Xiph family, there are three different free audio codecs, which can be stored/transported using the ogg container. Would it be possible to create an API and/or a library that would cover them all? If my understanding of the situation is correct, if an application wants to support vorbis, speex and flac, it has to use three different interfaces.