similar to: attention vorbis maintainers

Hi everybody: It's been a while, so here is the latest round of Status Updates from just about everybody in Xiph. The HTML version is at http://www.vorbis.com/ot/20030603.html Enjoy! <p>Ogg Traffic for Tuesday, June 3, 2003 Author: Carsten "Purple" Haese Contact: [1]carsten@xiph.org Date: June 3, 2003 Table of Contents 1 Status Updates

Hi everybody: Here is the newest round of status updates from Xiph.org. The HTML version is at http://www.vorbis.com/ot/20030930.html. Enjoy! -Carsten <p>Ogg Traffic for Tuesday, September 30, 2003 Author: Carsten "Purple" Haese Contact: [1]carsten@xiph.org Date: September 30, 2003 Table of Contents 1 Status Updates 1.1 Monty 1.2

Hi everybody: Here is a new Ogg Traffic, with release announcements for Vorbis 1.0.1, Speex 1.0.3, and Icecast 2 Beta 1. The HTML version is at http://www.vorbis.com/ot/20031119.html. Enjoy! -Carsten <p>Ogg Traffic for Wednesday, November 19, 2003 Author: Carsten "Purple" Haese Contact: [1]carsten@xiph.org Date: November 19, 2003 Table of Contents 1

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.

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

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

This question seems a little vague. I propose the following change (or something like it): <p>Q: What do all the names mean? <p>A: "Ogg" refers to the Ogg project, a blanket project designed to create a fully open multimedia system. "Ogg" also refers to a general container file format that can hold any type of multimedia data. "Vorbis" is the name of

I am looking for someone to continue the Ogg Traffic tradition. Ogg Traffic is a weekly update and status report about what's happening with Ogg development as well as other related projects and interesting bits of news (Xiph, Speex, Icecast, etc.). Stan Seibert, who resurrected OT recently, is busy with Real Life activities that prevent him from writing an OT (http://www.vorbis.com/ot/)

I tried to use the current cvs version of ogg123 with oss output and the ogg just sounds like static. I wanted to document it on the list in case anyone else is having the problem. I can make ogg123 write wav files fine. Also Vakor does not have any trouble playing oggs with ogg123, so I am not certain what the problem is. I have tried compiling all of ogg vorbis (ao,ogg,vorbis,vorbis-tools)

Installment #3 on my coding binge: The latest CVS version of ogg123 (in vorbis-tools) now plays FLAC and Ogg FLAC files. The FLAC support is optional, so if you don't have FLAC 1.0.4 and the header files, ogg123 will still build without it. Please give it a whirl and let me know how it works for you. --- Stan Seibert <p>--- >8 ---- List archives: http://www.xiph.org/archives/

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

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

The latest patch to allow oggenc to read FLAC files is up at: http://www.ph.utexas.edu/~volsung/patches/ Now both native FLAC and Ogg FLAC files can be read. Comments should in theory be preserved coming from either FLAC or Ogg FLAC. I cannot figure out how to make an Ogg FLAC file that has comments, so I've only tested it with normal FLAC. (Any tips would be appreciated here.) Note the

Are there any plans to support flac streams with ices (and therefore with libshout as a dependency) currently? If there aren't, anyone have pointers as to where I should start changing things to add it? I've read one of oddsock's mailing list postings mentioning that some format-specific timing issues would need to be resolved as well as some other hangups, but I'm still a bit

I've been kind of busy lately, but I wanted to see what's up with ao after the build change. I was able to check out the vorbis module, but when I tried to check out the ao module I saw this: [stan@volsung vorbis]$ cvs -d:pserver:anoncvs@cvs.xiph.org:/usr/local/cvsroot co -r branch_postbeta2 ao cvs server: Updating ao cvs server: Updating ao/doc cvs server: Updating ao/include cvs

Better late than never :) jack. --- Ogg Traffic for Tuesday, November 13, 2001 Jack Moffitt <[1]jack@xiph.org> _________________________________________________________________ Table of Contents 1. [2]Support The Ogg Project 2. [3]Status Updates 2.1. [4]Stan Seibert 2.2. [5]Chris Wolf 3. [6]New Developments 3.1. [7]Ogg On A Chip

Bear with the text-based format for a bit. I'll make it nicer over time, but for now it's just a lynx -dump of the html one. As always you can find these at http://www.vorbis.com/ot/ and http://www.vorbis.com/ot/latest.html for the latest one. ---- Ogg Traffic for Tuesday, October 30, 2001 Jack Moffitt <[1]jack@xiph.org>

Hi! There are some little inconvenience in libao-0.8.5. - The biggest is may that: the documentation and the header file declare the ao_file_extension function, which give a hint for the file extension where the device is realy a sound file. This function is missing. -An other: the alsa 0.5 and the alsa 0.9+ drivers short name. It will be better if the alsa 0.5's name will be alsa05 and the