similar to: libao and recent ALSA builds

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

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

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

Ok, this patch replaces the old patch I sent, and it does a bit more. For one, it sorts the linked list of drivers based on the priority values, highest valued ones coming first. That allows the _find_default_driver_id code to stop looping (break) immediately when it finds a driver that works, because it already knows it's the working driver with the highest priority (what it normally

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

Xiph.Org announces the release of libao-1.0.0, libvorbis-1.3.1 and vorbis-tools-1.4.0. This is a coordinated update of the audio libraries and tools to deploy improved surround-sound support across the libraries and toolchain. libao improvements: - AO returned to active development - Added surround channel mapping API and capability - Updated all drivers on modern installs - New config file

Xiph.Org announces the release of libao-1.0.0, libvorbis-1.3.1 and vorbis-tools-1.4.0. This is a coordinated update of the audio libraries and tools to deploy improved surround-sound support across the libraries and toolchain. libao improvements: - AO returned to active development - Added surround channel mapping API and capability - Updated all drivers on modern installs - New config file

Hi, I have downloaded the following files libao-0.6.0.tar.gz libogg-1.0beta4.tar.gz libvorbis-1.0beta4.tar.gz vorbis-tools-1.0beta4.tar.gz as said from the download section. But I'm at a loss to what do after that. I don't have much experience/knowledge in compiling etc, but I still want to try out ogg. (I downloaded the source coz I have an OpenBSD machine, and there was no

hi, i am trying to load vorbis tool on to my arm board EDB9302 , till now i have cross compiled libao, libogg, libvorbis, flac, speex and vorbis tool. when i run the command line arm-linux-ogg123 with some sample ogg format file on my arm board it gave *"Could not load default driver and no driver specified in config file : Exiting"* , please help me to over come this error.

It seems that the configure script in CVS does not check the CFLAGS environment variable at all. Indeed, on line 121 of configure.in, CFLAGS is explicitly set to be blank. Is this done for a reason? I see that several sets of CFLAGS are passed into the Makefiles by configure based upon specific architecture/compiler combinations -- perhaps this is the reason...? I ask because users may wish to

Hi, I've written an ao plugin for aRts, the soundserver that comes with KDE. Any chance of including this in the ao distribution ? Pretty please ? :) Sources and patches attached. This is a very simple plugin because it uses the easy-to-use 'artsc' C wrapper that aRts installs. configure.in.diff is for ao/configure.in Makefile.am.diff is for ao/src/plugins/Makefile.am Makefile.am

Hi, I sent the below a few days ago. It still hasn't turned up in the archive so i'm trying again. Since the first mail was sent, i've found out that removing the call to *_set_periods and *_set_period_size is a better solution to the problem. It seems that the alsa defaults are better than what ever fine tuning the code is trying to do. patch: ---

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

Compiling libao on a system w/linux2.4.2 & glibc-2.0 (I think), I get an error. gcc -DPACKAGE=\"libao\" -DVERSION=\"0.6.0\" -DSIZEOF_SHORT=2 -DSIZEOF_INT=4 -DSIZEOF_LONG=4 -DHAVE_SYS_SOUNDCARD_H=1 -I. -I. -I../../.. -I../../../include -O20 -ffast-math -D_REENTRANT -fsigned-char -DAO_PLUGIN_PATH=\"/usr/local/lib/ao\" -c ao_alsa.c -fPIC -DPIC -o ao_alsa.lo In file

I installed fink and now I have the /sw/lib, however that didn't fix my problem. I went as far as to take out the - Ddlsym=dlsym_auto_underscore out of the configuration files. Now however the libao package won't build at all and yips about this: [ukiel:/MP3/OGG/libao-0.8.6] wind% make Making all in src Making all in plugins Making all in oss make[3]: Nothing to be done for

While trying to compile libao 0.8.0 under OS X 10.1, I got the following problems: > [localhost:ecc/Sources/libao-0.8.0] root# ./configure > creating cache ./config.cache > checking for a BSD compatible install... /usr/bin/install -c > checking whether build environment is sane... yes > checking whether make sets ${MAKE}... yes > checking for working aclocal... found >

I am trying to install mpg321 on another box. But there is no default libao driver on that sysytem, it has a soundblaster card, supported by the kernel directly. Never used OSS or ALSA on that system, so I wonder is it possible to do without OSS or ALSA . The libao documentation does not talk about kernel drivers, so I wonder how to get it work. Any ideas? Arne

The enclosed patch to ao_alsa.c (src/plugins/alsa/ao_alsa.c) fixes (after a fashion) a problem I had with interrupted snd_pcm_write() calls. Apparently this behaves like write() rather than fwrite() and needs to be handled accordingly. The fix is dirty, but it gets the thing working. The patch is against the 0.8.0 version of libao, but I believe the latest ao_alsa.c from CVS is similar (if not

Hello, I built the entire Vorbis kit on my PowerMac G4 running OSX 10.4.6. I'm having problems however doing anything with the libao package. Any time I try to use the library to link it errors out with the following message: /usr/bin/ld: Undefined symbols: _dlsym_auto_underscore collect2: ld returned 1 exit status If I try to run the ogg123 application I get this:

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