similar to: libao WAV 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

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

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

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

> 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

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

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

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'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! 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'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

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

I am about to commit HTTP streaming code for ogg123. This has no relation to the discussion about "real" steaming Ogg; it just downloads and plays at the same time. But unless you have a direct T3 connection, it'll almost definately break up quite frequently. Solution? Buffer. But I have other things to work on for the rest of the day... Any screaming objections? This has been

[I'm still poking around in vorbis-tools. Here's another trivial patch.] In ogg123.c, the function get_stream goes down a linked list looking for the nth stream. Currently it will run off the end of the list and dereference the NULL pointer if the list is smaller than n. Attached is a patch to check for a null list and abort. Would assert() be a better way to do this? -=-=- Stan

------- 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

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

[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

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

For those of you who want to be able to decode Ogg Vorbis files into other formats, SoX (the swiss army knife of audio programs) now has Ogg Vorbis support in CVS. It can read Ogg Vorbis files and export the audio in any format SoX supports. You can also write Ogg Vorbis with it, but, because of limitations in the design of SoX, only output at 128kbps is supported. Note: Instructions on how to