similar to: libao IRIX patch

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

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

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

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

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

------- Forwarded Message Return-Path: owner-vorbis-dev@xiph.org Delivery-Date: Mon Jul 10 01:38:16 2000 Delivered-To: xiphmont@localhost.xiph.org Received: from localhost (localhost [127.0.0.1]) by bloopfish.xiph.org (Postfix) with ESMTP id 1A4A48882F for <xiphmont@localhost>; Mon, 10 Jul 2000 01:38:15 -0700 (PDT) Delivered-To: xiphmont@xiph.org Received: from xiph.org

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

[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

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/

Now that libao is integrated with ogg123, I was hoping that people with platforms different than mine could test the operation of ogg123+libao. I would really appreciate it if people testing ogg123 could send me email (privately, NOT to the list) with the following information: Hardware Platform: (Intel x86, MIPS, PowerPC, etc.) Operating System: (Linux, NetBSD, IRIX, etc.) Other sound

> Does anyone object to the attached patches? The main change is to be able > to call > > ao_append_option(&opts, "key", "value"); > I'm all for this one. The original form of the function is really poor design on my part. I hope this gets committed. --- Stan Seibert --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project

I just committed what will eventually become the next version of libao. I've made some major changes: renamed stuff, redesigned the API, actually documented things. It *will* break any current libao applications (like ogg123). It is on its own branch, so it shouldn't affect the mainline libao code for a while. But beware: I want to land this branch before Vorbis 1.0 goes out. Please

A branch of ogg123 is in CVS now which you can use to test the libao prerelease. Because of the way I did the branch, checkout is a little screwy (as Monty once said: "Know thy tools!"). (I am assuming here that you already have CVSROOT set correctly.) cvs co vorbis-tools # Notice there is no tag here! cd vorbis-tools/ogg123 cvs update -r volsung_20010721 Or, if you already have

Ack! I hate it when I have to fix my own crappy code. :) I present the endian fix for the wav output driver. Apply it along with the endian-fix.patch I sent earlier and things should be okay. Hopefully. Kenneth can check me on this with his PowerPC. --- Stan Seibert --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe

Kenneth mentioned he wanted a cross-platform audio library to use for ogg123. So, I've spent the last week hacking up the libao from ac3dec that someone suggested earlier. It bears little resemblance to the old code, but now does what I want. libao now supports OSS and WAV file output, with the infrastructure in place to expand further. There are Solaris and IRIX drivers that I inherited

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

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

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:

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, after reading the IRIX Digital Media Audio library documentation and starting to code an IRIX output plugin for libao and afterwards realizing there was already one on the CVS tree (almost identical to what I had up to that point, no wonder) and getting the rest of the vorbis tarball to compile under IRIX with the MIPSpro compiler only to find out the plugin was wrong and after going