libao issueshttps://gitlab.xiph.org/xiph/libao/-/issues2017-11-03T10:00:02Zhttps://gitlab.xiph.org/xiph/libao/-/issues/1779libao plugins call functions defined in libao proper2017-11-03T10:00:02ZChris Brannonlibao plugins call functions defined in libao properOur project uses libltdl to dynamically load plugin modules.
One of our modules links against libao.
When we try to load that module, libao prints an error message stating
that dlopen() failed when loading libao's alsa plugin.
I patched ...Our project uses libltdl to dynamically load plugin modules.
One of our modules links against libao.
When we try to load that module, libao prints an error message stating
that dlopen() failed when loading libao's alsa plugin.
I patched libao, so that I could see the message reported by dlerror.
dlerror claims that ao_is_big_endian is undefined.
Should libao's plugins be calling functions defined by libao itself?
Note that this also causes problems for language bindings like pyao.Monty MontgomeryMonty Montgomeryhttps://gitlab.xiph.org/xiph/libao/-/issues/1776libao 1.1.0 skipping default alsa device2017-11-03T10:00:02Zledtilibao 1.1.0 skipping default alsa deviceMy distribution recently upgraded libao ^(1)^ from 1.0.0 to 1.1.0 and I have encountered a problem where libao is ignoring the default device set in my local .asoundrc file.
It is defaulting to hw:0,0 even though hw:1,0 is set as the de...My distribution recently upgraded libao ^(1)^ from 1.0.0 to 1.1.0 and I have encountered a problem where libao is ignoring the default device set in my local .asoundrc file.
It is defaulting to hw:0,0 even though hw:1,0 is set as the default output device. After blacklisting hw:0,0, I ran two separate applications that use libao. The console output is included as an attachment.
Forgive me if this is distribution related, but it seemed to me to be a upstream issue.
Downgrading to 1.0.0 or blacklisting the snd-hda-intel module fixes the issue for me, though the latter option results in the attached output.
,,1. [upgpkg: libao 1.1.0-1](http://projects.archlinux.org/svntogit/packages.git/commit/libao/trunk/PKGBUILD?id=8307fae21dbe306c94c93b79c8fce8ff66bf7c52),,
Stan SeibertStan Seiberthttps://gitlab.xiph.org/xiph/libao/-/issues/1771libao pulse driver fault2011-02-22T15:56:25Zsimplelibao pulse driver faultHello. I have some problems with using pulse driver for libao.I launched "pacat --record | sox -t raw -r 44100 -s -b 16 -c 2 - -t ao pulse pitch -500" for processing audio input, but it faulted with "Assertion 'p' failed at pulse/simple...Hello. I have some problems with using pulse driver for libao.I launched "pacat --record | sox -t raw -r 44100 -s -b 16 -c 2 - -t ao pulse pitch -500" for processing audio input, but it faulted with "Assertion 'p' failed at pulse/simple.c:384, function pa_simple_drain(). Aborting". Using other drivers, such as alsa, works fine, but I need pulseaudio. So is it because of libao and how can I solve this problem?
Ubuntu 10.10, PulseAudio. libao 1.0.
Thanx.Stan SeibertStan Seiberthttps://gitlab.xiph.org/xiph/libao/-/issues/1764[PATCH] Version symbols2011-02-22T16:28:53ZCristian Morales Vega[PATCH] Version symbolsThe attached patch adds symbol versioning. Doing this
- ao_read_config_files()
- ao_au
- ao_null
- ao_raw
- ao_wav
are not exported anymore. Looking at http://www.xiph.org/ao/doc/libao-api.html it seems this is OK, correct?
Notice...The attached patch adds symbol versioning. Doing this
- ao_read_config_files()
- ao_au
- ao_null
- ao_raw
- ao_wav
are not exported anymore. Looking at http://www.xiph.org/ao/doc/libao-api.html it seems this is OK, correct?
Notice that web page (and the ao.h file) talks about an ao_file_extension() function. But such a function doesn't exists at all!! It's not exported with this patch and wasn't exported before.
The patch is against the latest SVN version. I used only the LIBAO4_1.0.0 symbol (extra verbose, could be changed) since I don't know of any added functionality in any of the functions since the 1.0.0 version... is this OK?
The symbol versioning support detection from configure.ac is copied from libpng, so I expect it to work without problems in other systems. Still, I didn't test it.
Symbol versioning has multiple advantages:
- Avoids crashes in UNIX systems when two ABI incompatible versions of libao are loaded in the same process image (since symbol resolution is global)
- The RPM build process automatically adds dependencies based on symbol versions. So, if the library is versioned, a package that requires libao 1.0.1 will have such dependency in the RPM package. Otherwise any library with the same soname, even if too old, would be allowed.
- If you trust Drepper and want to do the extra work, you can avoid any future ABI breakage.
Stan SeibertStan Seiberthttps://gitlab.xiph.org/xiph/libao/-/issues/1762[PATCH] libao ALSA driver could have a problem with some sound cards2010-12-17T11:32:27ZCristian Morales Vega[PATCH] libao ALSA driver could have a problem with some sound cardsFrom Takashi Iwai, from ALSA fame:
"There are devices that have only a small number of periods (aka
fragments) for a buffer, typically just two periods. So, if you set
the buffer size first, you limit the minimum period size to the half...From Takashi Iwai, from ALSA fame:
"There are devices that have only a small number of periods (aka
fragments) for a buffer, typically just two periods. So, if you set
the buffer size first, you limit the minimum period size to the half
of the given buffer size. This would result in a large latency.
OTOH, if you first set the period size, it limits the max buffer
size. So, the latency is assured.
Thus, it's a question whether you want a smaller latency or a better
stability. In the case of libao, the latency is more important."
This patch (or an equivalent, the source has change over years) has been in openSUSE since 2005 (yeah, sorry) without any complains, so it should be well tested.
Stan SeibertStan Seiberthttps://gitlab.xiph.org/xiph/libao/-/issues/1760[PATCH] libao misses header to use isspace()2010-12-17T11:28:52ZCristian Morales Vega[PATCH] libao misses header to use isspace()config.c uses isspace() without an "#include <ctype.h>"
config.c uses isspace() without an "#include <ctype.h>"
Stan SeibertStan Seiberthttps://gitlab.xiph.org/xiph/libao/-/issues/1731Mac OS X 10.6.4 Build 10F569 - Loss of audio when inserting or removing devic...2010-12-03T22:44:57ZJasonMac OS X 10.6.4 Build 10F569 - Loss of audio when inserting or removing device from audio jackInitiating pianobar while using the macbook's built in speakers, then plugging headphones into or unplugging from the headphone jack results in complete loss of sound from pianobar. The app needs to be restarted to restore sound.
I'm mo...Initiating pianobar while using the macbook's built in speakers, then plugging headphones into or unplugging from the headphone jack results in complete loss of sound from pianobar. The app needs to be restarted to restore sound.
I'm more than willing to provide more info, but I'm not sure what info would be needed to diagnose this. This is a consistent issue and can be replicated on my system 100% of the time.
Related:
http://github.com/PromyLOPh/pianobar/issues/closed#issue/36
http://github.com/PromyLOPh/pianobar/issues/#issue/35Monty MontgomeryMonty Montgomeryhttps://gitlab.xiph.org/xiph/libao/-/issues/1727device->internal no longer available2012-02-15T13:52:36ZRichard Kettlewelldevice->internal no longer availableForwarded from debian http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=577400
Package: libao-dev
Version: 1.0.0-3
In earlier versions of libao it was possible to write new plugins for
it, using the interface described at doc/plugin-ov...Forwarded from debian http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=577400
Package: libao-dev
Version: 1.0.0-3
In earlier versions of libao it was possible to write new plugins for
it, using the interface described at doc/plugin-overview.html and
doc/plugin-api.html.
However, the contents of the ao_device structure is no longer visible,
so plugins that store their private data via device->internal can no
longer be built. That would be fine if there was an alternative way to
associated private data with an ao_device, but there isn't.
plugin-overview.html mentions a number of other fields of ao_device
which plugins are expected to be able to access, e.g.
driver_byte_format, but they are also invisible.
Stan SeibertStan Seiberthttps://gitlab.xiph.org/xiph/libao/-/issues/1725libao mac os 10.6.4 audiojack problem2010-12-03T22:44:37ZGitlab Botlibao mac os 10.6.4 audiojack problemUsing Pianobar (http://github.com/PromyLOPh/pianobar, which utilizes libao) on a macbook pro 2010 13', while playing a song with headphones on, once the headphones are removed, there is no sound for the currently playing song from the ma...Using Pianobar (http://github.com/PromyLOPh/pianobar, which utilizes libao) on a macbook pro 2010 13', while playing a song with headphones on, once the headphones are removed, there is no sound for the currently playing song from the macbook speakers. Plugging the headphones back in does nothing. Monty MontgomeryMonty Montgomeryhttps://gitlab.xiph.org/xiph/libao/-/issues/1724libao waking from sleep problem in Mac OSX2010-12-03T22:44:15ZGitlab Botlibao waking from sleep problem in Mac OSXI have noticed that while using the Pianobar application (http://github.com/PromyLOPh/pianobar, which utilizes libao) in Snow Leopard 10.6.4, and the macbook goes to sleep, when the macbook wakes up, the current playing song has no audio. I have noticed that while using the Pianobar application (http://github.com/PromyLOPh/pianobar, which utilizes libao) in Snow Leopard 10.6.4, and the macbook goes to sleep, when the macbook wakes up, the current playing song has no audio. Monty MontgomeryMonty Montgomeryhttps://gitlab.xiph.org/xiph/libao/-/issues/1719SEGV after changes libao2010-12-02T22:07:50ZGitlab BotSEGV after changes libaoHi
I use libao in my application.
After last update from 0.8.6 to 1.0.0 I've reported failure. Everything was compiled correctly, but I get SEGV.
It was affected because it's been added a field char *matrix in structure ao_sample_forma...Hi
I use libao in my application.
After last update from 0.8.6 to 1.0.0 I've reported failure. Everything was compiled correctly, but I get SEGV.
It was affected because it's been added a field char *matrix in structure ao_sample_format. After set it on null, application run ok.
I compiled your ao_example.c and it's not setting it - it printed error "Unrecognized channel name" with random string or crashes.
My propose is use memset to clear structure before set or use assign format.matrix = NULL;
Secondly, I suggest add a version define in library header. Now I recognize change of structure in my application by finding new define of AO_EBADFORMAT in ao.h file.Stan SeibertStan Seiberthttps://gitlab.xiph.org/xiph/libao/-/issues/1715ao_sndio.c:103: error: `hdl' undeclared2010-08-04T01:24:40ZGitlab Botao_sndio.c:103: error: `hdl' undeclaredSorry; I don't have the time to fix this.
Might be a trivial fix... don't know.
On the download page there did not appear to be a list of required packages; If 'hdl' is due to a missing package dependency then please list it on the down...Sorry; I don't have the time to fix this.
Might be a trivial fix... don't know.
On the download page there did not appear to be a list of required packages; If 'hdl' is due to a missing package dependency then please list it on the download page.
$ make
[...]
ao_sndio.c: In function `ao_plugin_open':
ao_sndio.c:103: error: `hdl' undeclared (first use in this function)
$ uname -srvm
OpenBSD 4.5 GENERIC#1749 i386
$ find /usr/include -exec grep -q -e hdl \;-print -exec grep -n -e hdl \;
/usr/include/dev/audio_if.h
136: void *hdl;
[... not relevant ...]
nothing in /usr/local/include
and /include is non-existant
Stan SeibertStan Seiberthttps://gitlab.xiph.org/xiph/libao/-/issues/1694Segfaults of mpg321 if build with libao 1.0.02010-12-02T22:01:41ZfundawangSegfaults of mpg321 if build with libao 1.0.0See:
https://qa.mandriva.com/show_bug.cgi?id=59019
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=580062See:
https://qa.mandriva.com/show_bug.cgi?id=59019
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=580062Stan SeibertStan Seiberthttps://gitlab.xiph.org/xiph/libao/-/issues/1689libao not working correctly with pulse audio2010-12-02T21:59:56ZGitlab Botlibao not working correctly with pulse audioI'm using an app called "PianoBar". It's a a cli based Pandora client that uses libao for playback. When trying to play it returns the error:
Assertion 'p' failed at pulse/simple.c:384, function a_simple_drain(). Aborting.
Aborted
Play...I'm using an app called "PianoBar". It's a a cli based Pandora client that uses libao for playback. When trying to play it returns the error:
Assertion 'p' failed at pulse/simple.c:384, function a_simple_drain(). Aborting.
Aborted
Plays back fine using the Alsa backend.Monty MontgomeryMonty Montgomeryhttps://gitlab.xiph.org/xiph/libao/-/issues/1667libao 1.0.0 does not compile on Mac OS X 10.52010-04-06T17:25:44ZMax Hornlibao 1.0.0 does not compile on Mac OS X 10.5As the title says, libao 1.0.0 does not compile on Mac OS X 10.5. This is the error:
/bin/sh ../../../libtool --tag=CC --mode=compile gcc -DPACKAGE_NAME=\"libao\" -DPACKAGE_TARNAME=\"libao\" -DPACKAGE_VERSION=\"1.0.0\" -DPACKAGE_STRING...As the title says, libao 1.0.0 does not compile on Mac OS X 10.5. This is the error:
/bin/sh ../../../libtool --tag=CC --mode=compile gcc -DPACKAGE_NAME=\"libao\" -DPACKAGE_TARNAME=\"libao\" -DPACKAGE_VERSION=\"1.0.0\" -DPACKAGE_STRING=\"libao\ 1.0.0\" -DPACKAGE_BUGREPORT=\"monty@xiph.org\" -DPACKAGE=\"libao\" -DVERSION=\"1.0.0\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DHAVE_DLFCN_H=1 -DHAVE_DLOPEN=1 -DHAVE_LIBPTHREAD=1 -DDLOPEN_FLAG=\(RTLD_LAZY\) -DSHARED_LIB_EXT=\".so\" -DSIZEOF_SHORT=2 -DSIZEOF_INT=4 -DSIZEOF_LONG=4 -I. -I. -I../../../include/ao -I../../../include -DAO_SYSTEM_CONFIG='"/sw/etc/libao.conf"' -I/sw/include -D__NO_MATH_INLINES -fsigned-char -g -O2 -DAO_BUILDING_LIBAO -c -o ao_macosx.lo ao_macosx.c
libtool: compile: gcc -DPACKAGE_NAME=\"libao\" -DPACKAGE_TARNAME=\"libao\" -DPACKAGE_VERSION=\"1.0.0\" "-DPACKAGE_STRING=\"libao 1.0.0\"" -DPACKAGE_BUGREPORT=\"monty@xiph.org\" -DPACKAGE=\"libao\" -DVERSION=\"1.0.0\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DHAVE_DLFCN_H=1 -DHAVE_DLOPEN=1 -DHAVE_LIBPTHREAD=1 "-DDLOPEN_FLAG=(RTLD_LAZY)" -DSHARED_LIB_EXT=\".so\" -DSIZEOF_SHORT=2 -DSIZEOF_INT=4 -DSIZEOF_LONG=4 -I. -I. -I../../../include/ao -I../../../include -DAO_SYSTEM_CONFIG=\"/sw/etc/libao.conf\" -I/sw/include -D__NO_MATH_INLINES -fsigned-char -g -O2 -DAO_BUILDING_LIBAO -c ao_macosx.c -fno-common -DPIC -o .libs/ao_macosx.o
ao_macosx.c:74: error: syntax error before 'AudioComponentInstance'
The attached patch fixes this issue. It might even restore compatibility with 10.4, but I cannot test that right now (but will try to find out).
Stan SeibertStan Seiberthttps://gitlab.xiph.org/xiph/libao/-/issues/1642Pulse ALSA emulation refusing hw_param settings2010-02-05T23:15:30ZMonty MontgomeryPulse ALSA emulation refusing hw_param settingsPulse's alsa interception is refusing some hw_param settings that normal ALSA is not. Track this behavior down on an F11/12/13 box.Pulse's alsa interception is refusing some hw_param settings that normal ALSA is not. Track this behavior down on an F11/12/13 box.Monty MontgomeryMonty Montgomeryhttps://gitlab.xiph.org/xiph/libao/-/issues/1641need better configuration output wrt to which backends built2010-03-23T09:16:46ZMonty Montgomeryneed better configuration output wrt to which backends builtA reminder to me:
the configure script right now does not make it clear which backend support is being built and which is not. This must be made more explicit for the 1.0.9 release.A reminder to me:
the configure script right now does not make it clear which backend support is being built and which is not. This must be made more explicit for the 1.0.9 release.Monty MontgomeryMonty Montgomeryhttps://gitlab.xiph.org/xiph/libao/-/issues/1629PATCH: Add support for newer automake versions to libao's autogen.sh2010-01-11T20:39:13ZMax HornPATCH: Add support for newer automake versions to libao's autogen.shThe attached patch enables libao's trunk version to be used with automake 1.10 and newer, by fixing its autogen.sh in a fashion similar to what vorbis & ogg do.
The attached patch enables libao's trunk version to be used with automake 1.10 and newer, by fixing its autogen.sh in a fashion similar to what vorbis & ogg do.
Stan SeibertStan Seiberthttps://gitlab.xiph.org/xiph/libao/-/issues/1582Libao, too many arguments to function ao_play()2010-01-11T20:49:02ZExiquioLibao, too many arguments to function ao_play()I am working on wrapping libao in Ruby and I ran into an issue that probably is a big in my code (I am not a good C programmer). I get the following make error message referring to the method that wraps a call to ao_play():
gcc -I. -I. ...I am working on wrapping libao in Ruby and I ran into an issue that probably is a big in my code (I am not a good C programmer). I get the following make error message referring to the method that wraps a call to ao_play():
gcc -I. -I. -I/usr/lib/ruby/1.8/i686-linux -I. -D_FILE_OFFSET_BITS=64 -fPIC -march=i686 -mtune=generic -O2 -pipe -fPIC -c audiolibs.c
audiolibs.c: In function ‘play_ao’:
audiolibs.c:56: error: expected expression before ‘ao_device’
audiolibs.c:56: error: too few arguments to function ‘ao_play’
make: *** [audiolibs.o] Error 1
I am running Arch Linux (Linux ghostintheshell 2.6.30-ARCH #1 SMP PREEMPT Fri Jul 31 18:10:38 UTC 2009 i686 Intel(R) Core(TM)2 CPU 6420 @ 2.13GHz GenuineIntel GNU/Linux) with extra/libao 0.8.8-2, core/make 3.81-4, and core/gcc 4.4.1-1 installed.
I have attached a few relevant files. Maybe you have an idea of what is going on. Any help that you provide will be much appreciated. Thanks for you time.Stan SeibertStan Seiberthttps://gitlab.xiph.org/xiph/libao/-/issues/1580Compile libao by Visual Studio?2010-01-11T20:51:01ZJIA PeiCompile libao by Visual Studio?To whom it may concern:
Is there any plan for Visual Studio compilation of libao?
Best Regards
JIA Pei
To whom it may concern:
Is there any plan for Visual Studio compilation of libao?
Best Regards
JIA Pei
Stan SeibertStan Seibert