First time here? Check out the FAQ!
x

Unable to select Audio Device

0 votes
142 views

Hello,

After about an hour of playtime my Pacarana lost its Audio Device and I can't seem to select the Audio Device again. The device is listed in the drop down. After selecting the device I get the loading (clock) icon and after about 20 seconds the drop down menu goes back to Silent Device.

Kyma 7.42f3 (18 February 2024)

Apple M1 Pro

macOS 14.4.1 (23E224)

asked Apr 23 in Hardware & Interfaces by js (210 points)
Please try using the other FireWire port on the back of the Pacarana to see if that improves. Also please check that the FireWire cable has some support under it and is not getting pulled by gravity on the Pacarana end (https://kyma.symbolicsound.com/connecting-the-hardware/tips-for-achieving-firewire-bliss/)
Thanks ssc,

I ended up reseting my 828mk3 to factory default usings the front panel controls, Paca picked it up after that (probably a coincidence). Now just playing some light sounds and getting random "out of real time" messages and once followed by a "searching for audio interface" on the actual unit. The FireWire cable connections look solid. Several months ago it was a tank, only thing that changed is my macOS and latest Kyma update. I'll keep playing around and see if I can get anything reproducible, maybe it's time for a pacamara :).
Quick update on this... It might've been a pacarana <-> macbookpro connection issue. I had pacarana and macbookpro connected to a switch that was connected to a media room switch at the other side of the building :). I connected pacarana directly to my macbookpro via ethernet cable now and it's been solid for the last 3-4 hours. I guess a clue could've been the painfully slow loading times of sounds using (pacarana <->  switch(s) <-> macbookpro) setup yesterday when the issues were happening...

@ssc would this explain the behavior I was seeing yesterday, would a spotty ethernet connection cause audio interface(s) to get lost?
Interesting... yes, it could have been slowing down all messaging or they could have been getting buffered up and sent out in a burst that was too fast.

Glad it's working now!

Please log in or register to answer this question.

...