similar to: building libao for an ARM platform

I am having trouble configuring libao for cross compiling for an arm target on an x86 host. I try ./confgure --target=arm but, get the following error configure: error: can not run test program while cross compiling and it ends without finishing. How can I configure for arm development on an x86 system? tj

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

Hello Vorbis Developers. I'm in the proccess of writing an OggVorbis audio player using libao and libvorbisfile. I've greatly appreciated the simplicity of the API and good documentation with the souce of the libraries. I've descided that I really want a mixer on my player, and I'm unsure how to best go about it. LibAO (unless I'm absolutely blind) doesn't

Here are some of my notes with building and using vorbis-tools-1.0beta4 under Debian Linux 2.2. 1) building libao: make[3]: Leaving directory `/home/jeremy/src/ogg/libao-0.6.0/src/plugins/alsa' Making all in arts make[3]: Entering directory `/home/jeremy/src/ogg/libao-0.6.0/src/plugins/arts' /bin/sh ../../../libtool --mode=compile gcc -DPACKAGE=\"libao\"

Again, Hi All, Thanks for your replies. I probably should've mentioned that I'm not subscribed to the list but I found your answers on the archives. I just wanted to go on record and mention that I do in fact have all the original CD's and that by re-encoding I meant repeating the entire process of ripping the original CD's (with cdparanoia (of course ;)) and then encoding them

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

I hope this is the right place to submit libao patches -- the freshmeat page points to ogg vorbis as the homepage for libao. Currently, at least on my system (SB Live Value!, ALSA .9 branch), stuff going to alsa sounds *awful* because of too-small buffers. mpg321 and similar programs are unusable, and none of them seem to want to let you set the buffer size. This patch lets an environment

I've made a new source release of libao. This includes the polypaudio driver contributed by Lennart Poettering. http://downloads.xiph.org/releases/ao/libao-0.8.6.tar.gz http://downloads.xiph.org/releases/ao/libao-0.8.6.zip SHA1 checksums: 2050e008ffcfd6803e2c2c03c7d5f469b6d8379e libao-0.8.6.tar.gz 872ed527a4db012f315ce56e4b27a69e5b191a9f libao-0.8.6.zip MD5 checksums:

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

(Is this the right list for libao patches?) The following adds support for a sndio plugin to libao. sndio is OpenBSD's new audio API. diff -uNrp libao-0.8.8.orig/configure.ac libao-0.8.8/configure.ac --- libao-0.8.8.orig/configure.ac Thu May 24 12:51:05 2007 +++ libao-0.8.8/configure.ac Mon Dec 8 16:34:44 2008 @@ -300,6 +300,11 @@ dnl Check for Sun audio AC_CHECK_HEADERS(sys/audioio.h)

Hi. I'm trying to build and install ogg vorbis on Mandrake 8.2b4. I'm using the ogg vorbis source rpms on the download page. libogg and libvorbis built fine, but it looks like I'm missing a basic aRts header file in the build error excerpt below (artsc.h--somebody check and make sure I'm on the right track). However, I have Mandrake Cooker arts, libarts2, libarts2-devel

remember kenneth that libao has moved to the "ao" module, so copy the changes... jack. ----- Forwarded message from "Kenneth C. Arnold" <kcarnold@xiph.org> ----- Delivered-To: cvs-outgoing@xiph.org Delivered-To: cvs@xiph.org To: cvs@xiph.org Subject: [xiph-cvs] cvs commit: vorbis/vorbis-tools/libao ao_alsa.c ao_oss.c audio_out.c audio_out.h Date: Tue, 5 Sep 2000

I recently had a function added to the aRts API that lets you see if aRts is actually holding the DSP device open or not. This call can be useful in trying to autodetect what audio output to use, like libao does. I've written a patch for libao to take advantage of this. It adds an autoconf macro to test for the presence of this new function (so that it'll still work for people with an

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

I had a go at building libao-0.6.0 and it barfed on the alsa output part, complaining that snd_pcm_channel_status_t is undeclared - probably due to me running alsa 0.9.0 beta4. So the question is, should I try and beat the configure stuff into letting me disable alsa support and just use OSS, or would I be better off trying my luck with the nightly builds? And if so, can I get away with just

I had a go at building libao-0.6.0 and it barfed on the alsa output part, complaining that snd_pcm_channel_status_t is undeclared - probably due to me running alsa 0.9.0 beta4. So the question is, should I try and beat the configure stuff into letting me disable alsa support and just use OSS, or would I be better off trying my luck with the nightly builds? And if so, can I get away with just

On 16-01-13 21:52, Clemens Ladisch wrote: > Rene Herman wrote: >> I'm out of touch of with alsa -- but should dmix/dsnoop still be >> enabled by default on hardware that doesn't do hardware mixing? > > Yes. > >> I believe that it should be from /usr/share/alsa/cards/ICH4.conf, >> but I don't get mixing on this setup when using the

Hey' Can't seem to compile libao. I'm using Slackware-7.1-current-ish, linux-2.4.2, gcc-2.95.2, and alsa-9.0-beta2. This is the first time I've tried to compile libao so I don't know if the problem is related to alsa-9.0 changes. Alsa headers seem to be there: /usr/include/linux> ls -l as*.h -rw-r--r-- 1 root root 35994 Mar 3 10:57 asequencer.h -rw-r--r-- 1

Ben, Thanks for taking an interest in libao. Just so you know, there are a couple of things outstanding. Jeff Waugh asked whether we'd be willing to relicense libao so it can be used with proprietary applications. We have permission from the original authors to do this (either LGPL or BSD) and from Lennart Poettering, but not for most of the plugins. So if we did this the next release

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