similar to: ao_wav.c patch

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

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

I'm reordering the code in ao_wav.c that writes wav files to prevent the problem we had earlier. If ogg123 was improperly terminated (Segfault, kill -9, etc.), the output wav file was not even recognizable because the header was totally blank. I have found that at the start of playback (from libao's perspective), I know all of the wav header info except two things: 1) The length of the

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

Can someone apply this patch? It corrects a silly typo on my part. --- Stan Seibert ---------- Forwarded message ---------- Date: Wed, 07 Mar 2001 01:20:48 +0100 From: Markus Keller <markus@mercury.net.dhis.org> To: indigo@aztec.asu.edu Subject: ao patch Hi, I just noticed a small typo in ao_esd.c. Here is a patch for it: --- ao_esd.c~ Sun Feb 25 03:06:05 2001 +++ ao_esd.c Wed

This patch fixes three problems with the current configure script: 1. Manual exclusion of drivers: Now you will be able to force drivers NOT to be compiled, even if they are detected. This was specifically requested with so that ALSA could be disabled. 2. Selecting the default device: Now you can override the default driver chosen by the script with your own preference. Again, this enhancement

Just so people know what I'm working on (between physics assignments), here's a quick list of what's currently in the pipeline: * I received an IRIX patch which I am very excited about. I'll be submitting that shortly. * A month ago another user sent me a very small patch that improved ALSA performance on his machine. I don't understand what it does exactly, and would

I was looking back through the libao source after some time away from it and I noticed the addition of a plugin_get_latency() function to the plugin API. What is the purpose of this function and what was the motivation for adding it? --- Stan Seibert --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a

Hi, I'm whining again about the inclusion of the raw driver in libao. Can someone please commit the patch I posted in message: http://www.xiph.org/archives/vorbis-dev/0098.html (which will turn into http://www.xiph.org/archives/vorbis-dev/200103/0098.html in 4 days.) I've got people who want it included asking me what's the hold up. --- Stan Seibert --- >8 ---- List archives:

[Oops. Sent this to the wrong list.] Kenneth already appears to have committed a byte order fix for the WAV output driver. Attached is a patch to fix byte order in the OSS and ALSA drivers. The other output drivers seem to just use the native byte order (which libvorbisfile uses). As I do not have anything but Linux systems on Intel hardware at my disposal, I would really appreciate it if

I think my NetBSD patch got lost. I've reattached it. Could whoever commits it please email me so I know it went in? (Or better yet, is CVS write access a possibility?) --- Stan Seibert <HR NOSHADE> <UL> <LI>TEXT/PLAIN attachment: netbsd.patch </UL> -------------- next part -------------- A non-text attachment was scrubbed... Name: netbsd.patch Type:

The problem I noted earlier about segfaulting at the end of playback and the problem about mangled wav files have the same cause. The playback buffer in ogg123 is freed without checking if it has even been allocated. Ken probably didn't notice because he was using a buffer (which is optional). :) A patch for ogg123.c is attached. (Probably takes the record for the smallest patch

I've completed the new device for libao that just writes raw, headerless, unformatted audio data to the file of your choice. The driver also supports writing to stdout by specifying the output file to be "-". This is the better way to stream uncompressed audio for now, thereby avoiding the headaches contained in wav files. To add the driver: 1) Copy ao_raw.c into ao/src/ 2) Apply

Okay, here's the new version of the raw output driver. It now allows output in native, little-endian, and big-endian (to make the .cdr people happy) order. I've now had two different people request this driver, so I know there is some demand for it. Below are the patching directions cut-and-pasted from the original email: To add the driver: 1) Copy ao_raw.c into ao/src/

I've attached a patch for the IRIX driver that should make it actually compile and work! The driver definitely won't work without the endian fix I posted 30 min ago, so make both have been applied before you complain to me. :) --- Stan Seibert <HR NOSHADE> <UL> <LI>TEXT/PLAIN attachment: irix.patch </UL> -------------- next part -------------- A non-text

I'm also working on writing the raw driver I mentioned in the last email, but noticed that Jack has rearranged some of the guts of ao since I last looked at it. In ao/include/ao/ao.h you define AO_NULL and AO_WAV to be 0 and 1, respectively. If I want to add a raw driver that is compiled into the main library, can I just add #define AO_RAW 2 and then modify ao_initialize to put ao_raw

Okay, before I submit my patch to make libao produce sorta-streamable wav files, I want to know what these partial wav files do to various players. I've posted two sample wav files on my webserver: http://volsung.dhcp.asu.edu/~stan/infinite.wav http://volsung.dhcp.asu.edu/~stan/zero.wav The first uses a riff and data length of 0xFFFFFFFF (approximately infinite) and second uses a riff and

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

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

Thanks. sox was exactly what I was looking for. -----Original Message----- From: volsung@asu.edu [mailto:volsung@asu.edu] Sent: Thursday, February 08, 2001 2:06 PM To: vorbis-dev@xiph.org Subject: Re: [vorbis-dev] Conversion API for computer telephony systems (Dialogic Mu-law wa v format to PCM encoded wav format) On Thu, 8 Feb 2001, Giovanni Sanfelici wrote: > I am working on a project