The audio is taken hostage.
openpanda opened this issue · comments
What I mean is you must close pianobar to regain use of anything else, like youtube.
Are you using the OSS backend of libao? Try switching to alsa by adding
default_driver=alsa
to your ~/.libao
Alsa.
I doubt this is pianobar’s fault. Can you report the problem to libao’s
or your distribution’s bugtracker/mailinglist, please?
Indeed, I shall work see whats up. However as said before if I play mixxx,
or lmms while also running flash I can switch from the two. With pianobar I
notice the inability to do this until pianobar is killed.
On Thu, Nov 3, 2011 at 1:06 PM, PromyLOPh <
reply@reply.github.com>wrote:
I doubt this is pianobars fault. Can you report the problem to libaos
or your distributions bugtracker/mailinglist, please?
Reply to this email directly or view it on GitHub:
#167 (comment)
However as said before if I play mixxx, or lmms while also running
flash I can switch from the two.
Neither of these uses libao. Which reminds me: You can search for a
libao based player and test whether it “takes the audio hostage” as
well. If it does it’s a libao issue.
As i said I would take a look, also I noted libao as you stated it earlier.
On Thu, Nov 3, 2011 at 2:05 PM, PromyLOPh <
reply@reply.github.com>wrote:
However as said before if I play mixxx, or lmms while also running
flash I can switch from the two.
Neither of these uses libao. Which reminds me: You can search for a
libao based player and test whether it takes the audio hostage as
well. If it does its a libao issue.
Reply to this email directly or view it on GitHub:
#167 (comment)
I am not sure how to check which libao backend I am using, I haven't changed anything, so it is my distribution's (gentoo) default. I can not confirm this issue. I just tried to reproduce this error and was unable to do so.
@brutal-chaos: what does it say in /etc/libao.conf ? if default_driver=alsa, change it to default_driver=oss
Solved the problem for me.
@raeb, I don't have this problem. That was my point. :) And I don't even have a libao.conf. I checked by running "sudo find -mount -iname 'libao.conf' " and nothing came up. -mount stops find from searching on mount points and iname allows for variation in capitalization.
@brutal-chaos: I found that using the following ~/.libao file worked for me:
driver=alsa
dev=default
Without dev=default, libao blocked other audio (unless something else was already using it, then it printed a warning every time a new song started).
@ABCDwp's solution worked for me as well. Not sure how he figured that one out though.
I think we can safely say this is not a pianobar bug.