[PlanetCCRMA] Jack and KDE

[Roy Vestal]

Over the weekend I tried this, killing artsd, and setting it NOT to 
start. Didn't work. I still get the hw:0 busy error, but now it's saying 
"no alsa-driver found for this hardware". *sigh*

It's a SB16 PnP, and according to www.alsa-project.org it's supported...

Ideas?


Jan Depner wrote:

>Make sure you kill -9 artsd prior to starting jackd.  I usually put that
>in my qjackctl startup script.
>
>On Wed, 2006-04-26 at 09:13 -0700, Fernando Lopez-Lezcano wrote:
>  
>
>>On Wed, 2006-04-26 at 09:20 -0400, Roy Vestal wrote:
>>    
>>
>>>I'm getting an error starting Jack in my KDE environment. This is a new 
>>>install/build of FC3 and I'm wondering if ARTS is turned on. I'm 
>>>assuming this would be the cause of my Jack start errors. I believe the 
>>>error is "jackd could not start hw:0 in use". At the time of this 
>>>writing I am not able to get to the machine for the exact error.
>>>
>>>My question: Can ARTS be active and jackd still work or does it need to 
>>>be off? I'm assuming off is the correct answer at this time.
>>>      
>>>
>>Jack normally takes complete ownership of the sound card, all other
>>programs that use it have to be "off". 
>>
>>-- Fernando
>>
>>
>>_______________________________________________
>>PlanetCCRMA mailing list
>>PlanetCCRMA@ccrma.stanford.edu
>>http://ccrma-mail.stanford.edu/mailman/listinfo/planetccrma
>>    
>>