Please mark libao-0.8.5 as stable, or at least libao-0.8.4-r1. Libao 0.8.3 has alot of bugs and is quiet unusable for alsa; hence it is far less stable than libao-0.8.5 and libao-0.8.4. Thanks! Reproducible: Always Steps to Reproduce:
I second this one, libao-0.8.3 is much less stable for ALSA which alot of gentooer's are moving to today, it's not that it won't work, but it skips alot during any kind of 100% CPU load (and that's just one bug).
I would also like to see libao-0.8.5 marked as stable. that is all.
okay, does the dynamic mmap work? And what about the esound backend that had some changes? the reason -r1 wasn't moved to stable earlier was that there cropped up a series of libtool/autoconf issues that bit people, I'll retag it as stable now and hope for the best, holding off on the .8.5 release until it has a week of testing though
erm. emerge info for those who requested that 0.8.4-r1 be marked as stable.
"Dynamic mmap?" Do you mean mmap for Alsa? I'd recommend disabling it for compiles. But a runtime option for the alsa09 plugin was added to enable mmap. So users can enable it if they desire in their /etc/libao.conf for ~/.libao. If i recall correctly, alsa mmap doesn't work correctly for some sound cards and has problems with dmix (although the last testing i did with this was with alsa 0.9.7). I'm not sure which build problems you are refering to, but heres the log entries from cvs on configure.in (I know some build problems were fixed): revision 1.54 date: 2003/10/18 20:36:46; author: calc; state: Exp; lines: +1 -0 AM_MAINTAINER_MODE added This allows for builds not to fail if automake is installed on the build system and it doesnt happen to be exact same version used during autogen.sh process. ---------------------------- revision 1.53 date: 2003/10/08 15:20:27; author: volsung; state: Exp; lines: +1 -1 Never put AM_CONDITIONAL in an if-statement. Fix for esd from Christian Weisgerber. So, hopefully the build problems were fixed.
well, yes. I mean the runtime selection. The build related problems appear to be fixed, but I'm still curious about other combinations of libtool, auto* and company. Somehow it seems that there will always crop up bugs with those two involved ;) The reason I'm wondering about the others emerge info is that 0.8.4-r1 has been stable for x86 for some time. pushing 0.8.5 to stable "too soon" (less than a day after its initial commit) ruins the point of having an ~x86 keyword at all. :)
Sounds good to me :-) Thanks for your help, hopefully libao-0.8.5 should be stable, if not, let me know. Also, libao-0.8.4 is marked as stable for amd64, can you mark libao-0.8.4-r1 as stable on amd64? (this is my dev platform) Thanks, -shank
Closing a stale bug, 0.8.5 is marked stable everywhere except ppc-macos.
