Displaying 20 results from an estimated 20000 matches similar to: "Raw driver for libao"
2000 Sep 02
1
libao endian fix (attempt 2)
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
2001 May 08
2
libao AU driver
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
2000 Aug 16
1
YALCSF (Yet Another Libao Configure Script Fix)
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
2001 Mar 28
1
Whining about the raw driver.
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:
2000 Sep 02
1
Future libao refinements
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
2004 Oct 22
0
libao-0.8.5 patch
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
2000 Jul 10
0
libao/ogg123 update: ESD (fwd)
------- 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
2001 Jul 23
0
libao: ogg123 branch ready
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
2001 Jul 21
1
Preview of next version of libao
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
2000 Aug 12
1
libao patch: Minor clean up / Byte-order proposal
Here is a patch to fix the compiler warnings I mentioned earlier. I've
removed the byte-order changes that don't make sense. (Thanks Michael for
pointing out the error!)
As for the byte-order changes, since some output modules don't have the option
to set the sample byte-order, I would like to standardize libao and ogg123 on
native byte-order. Will this break the ao_wav.c patches
2001 Jan 20
0
libao: Raw audio device
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
2001 Mar 14
0
Raw driver patch for libao (New Version)
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/
2001 Jan 20
4
"Infinite" wav files
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
2000 Dec 17
1
Re: libao api change
> 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
2001 Sep 03
2
Building vorbis-tools without libao
Hi All,
For my new file (and thus mp3) server I've decided to switch
completely to Ogg Vorbis. This means having to reencode
~30GB worth of 128Kb MP3's, but i figured that it would all
be worth the effort. So I downloaded the sources for
libogg, libvorbis and vorbis-tools and fired up my trusty
old compiler. libogg and libvorbis built and installed
like a charm. Not so for
2000 Jul 09
0
libao: Cross-platform audio for ogg123
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
2000 Oct 01
4
CVS Problem
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
2000 Jul 28
0
libao testing
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
2007 Apr 02
1
win32 driver for libao
Hi there.
Sorry I may be a little off topics with this mail but I have already
written to the official libao maintainer (volsung@xiph.org) and he is
the one who suggest me to write here. As I did not see any more suitable
mailing list @xiph.org here I am.
My point is that I have recently written a win32 driver for the libao
and I would be glad to see this contribution include to the official
2000 Aug 07
1
libao patch: Endian-ness fix
[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