[LAU] question about jackdmp's ability to detect its soundcard has disconnected

Len Ovens len at ovenwerks.net
Mon Oct 29 20:29:17 UTC 2012


On Mon, October 29, 2012 7:55 am, Ivica Ico Bukvic wrote:

> Either way, one of my concerns is that while in the old jack when one
> accidentally pulled the soundcard jack was trying to talk to (e.g. a USB
> soundcard), the jack would gracefully stop. The new version (and this
> could
> be Ubuntu quirk) instead of stopping is pegged in some kind of a spinlock
> that often times locks up the machine (this may be in part since I am
> running a lowlatency kernel with audio group given priority) and at times
> keeps it operational while hogging the cpu and making the computer barely
> responsive until jackd is killed. Apps connected to jack that I tested so
> far are also stuck in a loop waiting for a response from jack (although
> this
> could be the app's shortcoming)--jack never broadcasts a signal that it
> has
> lost the soundcard (AFAICT). FWIW I am running jackdmp through qjackctl...

Sounds like a bug. I will test it on my HW (both of them) to see what I
can see.

-- 
Len Ovens
www.OvenWerks.net



More information about the Linux-audio-user mailing list