Hi.
I have Severn with all the recent rawhide channel updates, but got a problem with Sound and KDE's Arts.
Here is what happens.
Before I get inside KDE, the sound works fine, and I can test the soundcard using eox to play songs, or cat /etc/dsp. After I log in KDE, and the Arts server runs, I can't use any other application that uses sound. If I give a cat /dev/dsp it gives a "Resource Busy" response. If I try to run xmms or any other sound player, the same problem.
Does anyone has a way to fix this?
Regards, Thiago
On Sep 2, 2003 at 08:41, Thiago Vinhas de Moraes in a maddening rage wrote:
Hi.
I have Severn with all the recent rawhide channel updates, but got a problem with Sound and KDE's Arts.
Here is what happens.
Before I get inside KDE, the sound works fine, and I can test the soundcard using eox to play songs, or cat /etc/dsp. After I log in KDE, and the Arts server runs, I can't use any other application that uses sound. If I give a cat /dev/dsp it gives a "Resource Busy" response. If I try to run xmms or any other sound player, the same problem.
Does anyone has a way to fix this?
You need to use the KDE Kontrol Centre to release the device after a certain amount of time. Something like 30 seconds should do it.
ne... wrote:
On Sep 2, 2003 at 08:41, Thiago Vinhas de Moraes in a maddening rage wrote:
Hi.
I have Severn with all the recent rawhide channel updates, but got a problem with Sound and KDE's Arts.
Here is what happens.
Before I get inside KDE, the sound works fine, and I can test the soundcard using eox to play songs, or cat /etc/dsp. After I log in KDE, and the Arts server runs, I can't use any other application that uses sound. If I give a cat /dev/dsp it gives a "Resource Busy" response. If I try to run xmms or any other sound player, the same problem.
Does anyone has a way to fix this?
You need to use the KDE Kontrol Centre to release the device after a certain amount of time. Something like 30 seconds should do it.
Or configure XMMS to use artsd...
Em Ter, 2003-09-02 às 09:15, Steven Haigh escreveu:
Before I get inside KDE, the sound works fine, and I can test the soundcard using eox to play songs, or cat /etc/dsp. After I log in KDE, and the Arts server runs, I can't use any other application that uses sound. If I give a cat /dev/dsp it gives a "Resource Busy" response. If I try to run xmms or any other sound player, the same problem.
Does anyone has a way to fix this?
You need to use the KDE Kontrol Centre to release the device after a certain amount of time. Something like 30 seconds should do it.
Or configure XMMS to use artsd...
It doesn't work. Crashes.. But I need to run VMware and it can't open /dev/dsp too.
Thiago Vinhas de Moraes wrote:
Em Ter, 2003-09-02 às 09:15, Steven Haigh escreveu:
Before I get inside KDE, the sound works fine, and I can test the soundcard using eox to play songs, or cat /etc/dsp. After I log in KDE, and the Arts server runs, I can't use any other application that uses sound. If I give a cat /dev/dsp it gives a "Resource Busy" response. If I try to run xmms or any other sound player, the same problem.
Does anyone has a way to fix this?
You need to use the KDE Kontrol Centre to release the device after a certain amount of time. Something like 30 seconds should do it.
Or configure XMMS to use artsd...
It doesn't work. Crashes.. But I need to run VMware and it can't open /dev/dsp too.
that being the case, you'll have to 'killall artsd' before you run VMWare... I'm not sure if there's a way around it, but iirc VMware only uses direct access to /dev/dsp and can't/won't share with a sound daemon...
On Tue, 2 Sep 2003, Steven Haigh wrote:
Thiago Vinhas de Moraes wrote:
Em Ter, 2003-09-02 Ã s 09:15, Steven Haigh escreveu:
Before I get inside KDE, the sound works fine, and I can test the soundcard using eox to play songs, or cat /etc/dsp. After I log in KDE, and the Arts server runs, I can't use any other application that uses sound. If I give a cat /dev/dsp it gives a "Resource Busy" response. If I try to run xmms or any other sound player, the same problem.
Does anyone has a way to fix this?
You need to use the KDE Kontrol Centre to release the device after a certain amount of time. Something like 30 seconds should do it.
Or configure XMMS to use artsd...
It doesn't work. Crashes.. But I need to run VMware and it can't open /dev/dsp too.
that being the case, you'll have to 'killall artsd' before you run VMWare... I'm not sure if there's a way around it, but iirc VMware only uses direct access to /dev/dsp and can't/won't share with a sound daemon...
ESD provides a wrapper for launching applications that directly use /dev/dsp. I'm not too familiar with artsd, but perhaps it provides something similiar?
Looking at the arts package itself, artswrapper looks kind of promising, although the machine I'm on right now is 7.3, so things might have changed since then.
Gregory Boyce
gboyce@badbelly.com wrote:
On Tue, 2 Sep 2003, Steven Haigh wrote:
Thiago Vinhas de Moraes wrote:
Em Ter, 2003-09-02 Ã s 09:15, Steven Haigh escreveu:
Before I get inside KDE, the sound works fine, and I can test the soundcard using eox to play songs, or cat /etc/dsp. After I log in KDE, and the Arts server runs, I can't use any other application that uses sound. If I give a cat /dev/dsp it gives a "Resource Busy" response. If I try to run xmms or any other sound player, the same problem.
Does anyone has a way to fix this?
You need to use the KDE Kontrol Centre to release the device after a certain amount of time. Something like 30 seconds should do it.
Or configure XMMS to use artsd...
It doesn't work. Crashes.. But I need to run VMware and it can't open /dev/dsp too.
that being the case, you'll have to 'killall artsd' before you run VMWare... I'm not sure if there's a way around it, but iirc VMware only uses direct access to /dev/dsp and can't/won't share with a sound daemon...
ESD provides a wrapper for launching applications that directly use /dev/dsp. I'm not too familiar with artsd, but perhaps it provides something similiar?
Looking at the arts package itself, artswrapper looks kind of promising, although the machine I'm on right now is 7.3, so things might have changed since then.
Gregory Boyce
I actually tried this with an application I was trying to get going - gnomemeeting iirc.... There is an artswrapper binary, but I couldn't seem to get it working... YMMV as I didn't spend a great deal of time on it...
Em Ter, 2003-09-02 às 09:03, ne... escreveu:
Before I get inside KDE, the sound works fine, and I can test the soundcard using eox to play songs, or cat /etc/dsp. After I log in KDE, and the Arts server runs, I can't use any other application that uses sound. If I give a cat /dev/dsp it gives a "Resource Busy" response. If I try to run xmms or any other sound player, the same problem.
You need to use the KDE Kontrol Centre to release the device after a certain amount of time. Something like 30 seconds should do it.
I tried doing it and did not work. Shouldn't it be set by default?
Regards, Thiago
On Sep 2, 2003 at 09:36, Thiago Vinhas de Moraes in a maddening rage wrote:
Em Ter, 2003-09-02 às 09:03, ne... escreveu:
Before I get inside KDE, the sound works fine, and I can test the soundcard using eox to play songs, or cat /etc/dsp. After I log in KDE, and the Arts server runs, I can't use any other application that uses sound. If I give a cat /dev/dsp it gives a "Resource Busy" response. If I try to run xmms or any other sound player, the same problem.
You need to use the KDE Kontrol Centre to release the device after a certain amount of time. Something like 30 seconds should do it.
I tried doing it and did not work. Shouldn't it be set by default?
Did you quit KDE then go back in so that artsd is restarted? Artsd generally releases devices after a long while. Also check the permissions on /dev/dsp as well. Unfortunately I am not sitting at by Linux boxen at the moment.