| 1 |
Daiajo Tibdixious posted on Thu, 16 Sep 2010 07:29:11 +1000 as excerpted: |
| 2 |
|
| 3 |
> I run firefox-bin with a large applet that plays music and other sounds. |
| 4 |
> I have it started via KDE run 'aoss firefox-bin'. When the applet is |
| 5 |
> running I can't get sound in mplayer. If I exit the applet, while |
| 6 |
> firefox is still running, I can then get sounds. Is there a way to get |
| 7 |
> sound in the applet and mplayer at the same time? |
| 8 |
|
| 9 |
I run 64-bit firefox, not firefox-bin, and while I run kde, I had |
| 10 |
absolutely /no/ idea what "aoss" was until I just googled it. It seems |
| 11 |
it's an alsa wrapper script, facilitating the use of alsa's OSS |
| 12 |
compatibility library. Also, I don't run proprietaryware and pretty much |
| 13 |
all my software is long since upgraded beyond the point at which it'd be |
| 14 |
trying to do exclusive locking. Based on those caveats, my help is |
| 15 |
obviously going to be limited, but as I see no one else has replied yet, |
| 16 |
perhaps it'll be of at least /some/ help. |
| 17 |
|
| 18 |
First thing, check the aoss manpage. As I implied, it's not installed |
| 19 |
here, but if you don't have a local manpage, it was the first non- |
| 20 |
sponsored hit (the sponsored one isn't even aoss, it's asos, whatever that |
| 21 |
is) on a google.com/linux search for "aoss". |
| 22 |
|
| 23 |
Of immediate interest here was the -32 argument, for 32-bit use on a |
| 24 |
normally 64-bit system. Given that I believe firefox-bin is 32-bit, this |
| 25 |
is the amd64 list, and I don't see a -32 in your command-line above, that |
| 26 |
could very well have something to do with it. |
| 27 |
|
| 28 |
If that alone doesn't work, the second google-linux hit is an archlinux |
| 29 |
forum post about aoss 32/64-bit issues (for wine in their case). Just |
| 30 |
skimming the discussion, it appears a bit technical and the suggestions |
| 31 |
may need adapted for use on gentoo, but at least one poster mentions that |
| 32 |
he got it working for him. There's another 32/64-bit hit on the first |
| 33 |
page as well. |
| 34 |
|
| 35 |
Beyond that, it gets hairy. One would look at whether you have hardware |
| 36 |
multi-audio-stream mixing and whether dmix is enabled. One would look at |
| 37 |
the device locking -- OSS devices often had exclusive access locks, and |
| 38 |
that's what your applet might be using, while alsa, thanks to dmix on |
| 39 |
hardware that doesn't support multiple hardware stream mixing, shouldn't |
| 40 |
need them. One would look at which devices mplayer is accessing -- if |
| 41 |
it's accessing the OSS devices (presumably without locking) and those are |
| 42 |
getting locked by the applet, that'd explain things. It should be set to |
| 43 |
use the alsa devices instead. |
| 44 |
|
| 45 |
Good luck. Troubleshooting sound issues like this on Linux has always |
| 46 |
been a challenge, so you'll need patience, some technical ability, and |
| 47 |
possibly a bit of luck. |
| 48 |
|
| 49 |
-- |
| 50 |
Duncan - List replies preferred. No HTML msgs. |
| 51 |
"Every nonfree program has a lord, a master -- |
| 52 |
and if you use the program, he is your master." Richard Stallman |
Archives