--bcaec55555d2e2301204cd353e31
Content-Type: text/plain; charset=ISO-8859-1
Could this be the difference between 1.9.8 and git version?
On Oct 29, 2012 12:10 PM, "Robin Gareus" wrote:
> On 10/29/2012 03:55 PM, Ivica Ico Bukvic wrote:
quoted text > > All,
> >
> > I noticed since upgrading to Ubuntu 12.04 that the default Jack server is
> > jackdmp (v.1.9.8). Please correct me if I am wrong but my understanding
> this
> > is the smp-enabled version 2 that is being developed in parallel with 1.x
> > series of regular jack.
>
> correct. They are also API and ABI compatible.
>
> > 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.
>
> In my experience it stopped but never gracefully (ie it crashed). but
> it's been a while since I used jack1.
>
> > 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...
> > Any thoughts on this matter would be most appreciated.
> >
>
> I can't reproduce this. jack2 stops the backend when the device is
> disconnected. You can switch to a new backend using jack_control
> (sending some Dbus messages to jackd) without re-starting jackd. No CPU
> hogging here. - I'm running jack2 - aka 1.9.9.4 from git.
>
> robin
>
>
--bcaec55555d2e2301204cd353e31
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Could this be the difference between 1.9.8 and git version?<=
/p>
On Oct 29, 2012 12:10 PM, "Robin Gareus&quo=
t; <robin@gareus.org > wrote:<=
br type=3D"attribution">
On 10/29/2012 03:55 PM, Ivica Ico Bukvic wrote:
quoted text > All,
>
> I noticed since upgrading to Ubuntu 12.04 that the default Jack server=
is
quoted text > jackdmp (v.1.9.8). Please correct me if I am wrong but my understandin=
g this
quoted text > is the smp-enabled version 2 that is being developed in parallel with =
1.x
quoted text > series of regular jack.
correct. They are also API and ABI compatible.
> Either way, one of my concerns is that while in the old jack when one<=
br>
quoted text > accidentally pulled the soundcard jack was trying to talk to (e.g. a U=
SB
quoted text > soundcard), the jack would gracefully stop.
In my experience it stopped but never gracefully (ie it crashed). but
it's been a while since I used jack1.
> The new version (and this could
quoted text > be Ubuntu quirk) instead of stopping is pegged in some kind of a spinl=
ock
quoted text > that often times locks up the machine (this may be in part since I am<=
br>
quoted text > running a lowlatency kernel with audio group given priority) and at ti=
mes
quoted text > keeps it operational while hogging the cpu and making the computer bar=
ely
quoted text > responsive until jackd is killed. Apps connected to jack that I tested=
so
quoted text > far are also stuck in a loop waiting for a response from jack (althoug=
h this
quoted text > could be the app's shortcoming)--jack never broadcasts a signal th=
at it has
quoted text > lost the soundcard (AFAICT). FWIW I am running jackdmp through qjackct=
l...
quoted text > Any thoughts on this matter would be most appreciated.
>
I can't reproduce this. jack2 stops the backend when the device is
disconnected. You can switch to a new backend using jack_control
(sending some Dbus messages to jackd) without re-starting jackd. No CPU
hogging here. - I'm running jack2 - aka 1.9.9.4 from git.
robin
--bcaec55555d2e2301204cd353e31--