I have: SuSE 7.3 Linux 2.4.10-4GB i686 Ensoniq AudioPCI ES1371 @ 0xd000, irq 5 Sound Driver: 3.8.2-980706(ALSAv0.5.11 emulation code) I have artsd set to start automatically (default in Kontrol Center). If artsd is running, xmms complains: Please check that: 1. You have the correct output plugin selected 2. No other programs is blocking the soundcard 3. Your soundcard is configured properly. If I kill artsd, xmms operates properly. All other sound clients seem to operate properly after killing artsd, but most report that they do not have access to /dev/dsp if artsd is running ??? I need some hand-to-hand here. I am lost! -- Patrick Shanahan Registered Linux User #207535 @ http://counter.li.org
On Wed. Jul. 17, 2002 at 07:30:21 -0500 GMT, a lone cry was heard from
SuSEnixER
If I kill artsd, xmms operates properly. All other sound clients seem to operate properly after killing artsd, but most report that they do not have access to /dev/dsp if artsd is running ???
Yes, aRtsd locks /dev/dsp. The solution is either use all applications that supports aRtsd or not use aRtsd at all. If you want to use XMMS with aRtsd, use the the aRtsd output plugin located at: http://stukach.com/hosted/m.i.a/xmmsarts/xmmsarts-0.4.tar.bz2 Charles -- "Whip me. Beat me. Make me maintain AIX." (By Stephan Zielinski)
SuSEnixER
If I kill artsd, xmms operates properly. All other sound clients seem to operate properly after killing artsd, but most report that they do not have access to /dev/dsp if artsd is running ???
Only one application may have the device to itself at any given time
(leaving out cards with multiple inputs like SB Live!). So if artsd
has the sound device, no other app may access it.
As artsd, besides being a full featured synthesizer, is a sound
multiplexer, there are other ways of getting non artsd aware apps to
play along (pun intended :).
Instead of killing artsd, you could simply use the artsdsp wrapper.
This will make the app connect to artsd instead of directly to
/dev/dsp. You simply do 'artsdsp
On Wed. Jul. 17, 2002 at 15:06:26 +0200 GMT, a lone cry was heard from
Philipp Thomas
Instead of killing artsd, you could simply use the artsdsp wrapper. This will make the app connect to artsd instead of directly to /dev/dsp. You simply do 'artsdsp
'.
Interesting, didn't know that. Thanks. Charles -- "Open Standards, Open Documents, and Open Source" -- Scott Bradner (Open Sources, 1999 O'Reilly and Associates)
* Philipp Thomas
SuSEnixER
[17 Jul 2002 07:30:21 -0500]: If I kill artsd, xmms operates properly. All other sound clients seem to operate properly after killing artsd, but most report that they do not have access to /dev/dsp if artsd is running ???
Only one application may have the device to itself at any given time (leaving out cards with multiple inputs like SB Live!). So if artsd has the sound device, no other app may access it.
As artsd, besides being a full featured synthesizer, is a sound multiplexer, there are other ways of getting non artsd aware apps to play along (pun intended :). Instead of killing artsd, you could simply use the artsdsp wrapper. This will make the app connect to artsd instead of directly to /dev/dsp. You simply do 'artsdsp
'. For xmms there is an artsd output plugin, contained in the xmms-kde package if I remember correctly. Install the package and the choose artsd as output plugin from the xmms configuration dialog.
Thankyou Philipp. I downloaded the plugin libartsout.* and copied it into /opt/gnome/lib/xmms/Output. I can now load xmms with artsd running after selecting 'Output Plugin' aRts Driver. BUT, I get periods of clear good audio, then periods of mushie static background with the expected audio. I can sometimes clear the interference pause/resume the mp3, but not always. It seems to be related to internet io, or perhaps, disk io. I have an eth0 <--> router <--> cable-modem <--> cable internet. I also have an add-on ata-100 io card with a WD1000 on it. My sound card is on irq5, but I have no idea what irq eth0 or the ata-100card is on, or if that could be the problem. tks -- Patrick Shanahan Registered Linux User #207535 @ http://counter.li.org
::My sound card is on irq5, but I have no idea what irq eth0 or the ::ata-100card is on, or if that could be the problem. You can find out what's in the machine by executing 'lspci -vv | more' as root. Should give you all the info of what you have on the PCI bus. -=Ben --=====-----=====-- mailto:ben@whack.org --=====-- Tell me what you believe..I tell you what you should see. -DP --=====-----=====--
* Ben Rosenberg
::My sound card is on irq5, but I have no idea what irq eth0 or the ::ata-100card is on, or if that could be the problem.
You can find out what's in the machine by executing 'lspci -vv | more' as root. Should give you all the info of what you have on the PCI bus.
Thanks Ben. The ata-100 card is on irq 11, but:
00:08.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8029(AS)
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping-
Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
participants (4)
-
Ben Rosenberg
-
Charles Philip Chan
-
Philipp Thomas
-
SuSEnixER