similar to: wrote a NAS plugin for libao

Hello, I have written a libsndfile (http://www.mega-nerd.com/libsndfile/) file output plugin for libao. For the moment I haven't done any changes to the core of libao. However some changes could make this more useful. Before I embark on anything like this I'd like to have your opinion on a few things. --- First, what do you prefer ? 1a. Keeping the AU/WAV/RAW plugins and adding

Hello, Here is a small patch for the libao NAS plugin that properly fixes issue 665 (http://trac.xiph.org/ticket/665) and adds minor improvements. -------------- next part -------------- A non-text attachment was scrubbed... Name: ao_nas.c.patch Type: text/x-patch Size: 2204 bytes Desc: not available Url :

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

(Hi, this isn't exactly vorbis related, but I figure most of you use libao with ogg123.) Libao 0.8.4 has been released today. It's mostly a bug-fix release, but has some new drivers too! We've also moved libao to it's own website: http://www.xiph.org/ao/ Source, RPMS for RedHat 9, and Debian packages are there. Enjoy! Changelog: * Incorporated OS X patches from the Fink

I saw that libao has a NAS plugin and wanted to try it out, especially with ogg123. However, I had/have several problems. My platform is Solaris 9/SPARC 12/02, NAS 1.6, libao 0.8.5, curl 7.10.8, libogg 1.1, libvorbis 1.0.1, and vorbis-tools 1.0.1. PROBLEM ONE: ------------ I had to specify LDFLAGS="-lXt -lsocket -lm" before running ./configure with "--enable-nas" in order

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

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

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:

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

In January I submitted a new "raw" output driver for libao that lets you write the audio samples directly to a file without any headers or anything else. It never got committed. Is it too late in the beta cycle to add it? I've been contacted by an author of a CD recording application whose problem could be solved by the inclusion of the raw driver. I need to make a change to the

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

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

I am using the Versatile Application baseboard and intend to use the ogg vorbis libraries . I have been able to install all the modules related to sound . However I think there's something wrong with the /sev/sound folder in my kernel , hence everytime we do cat anything.au > /dev/audio It throws an error cant create device /dev/audio even though /dev/audio is present . My question is

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

Hello, Can I get svn access for applying some libao patches? It seems that nobody maintains libao currently. This is really bad because there are many projects out wich using it. BTW: Not all kind of apps need all available audio controlling settings. My current plans: 1. extending ao_pulse for controlling prebuffering and latency 2. later extending libao api with volume control (softvol). 3. I

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

Hi there, I've been grappling with this for some time, so I'm finally breaking down and trying this list. I'm trying to integrate libvorbisfile and libao to create a simple sound file player, a la ogg123. To do this, I borrowed heavily from ao_example.c and vorbisfile_example.c. I feed the buffer from ov_read into ao_play in a simple loop. It usually works, but occasionally all it