<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>See below (from the linux-audio-user list):<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Re: [LAU] question about jackdmp's ability to detect its soundcard has disconnected<o:p></o:p></span></p><div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p>Could this be the difference between 1.9.8 and git version?<o:p></o:p></p><p class=MsoNormal>On Oct 29, 2012 12:10 PM, "Robin Gareus" <<a href="mailto:robin@gareus.org">robin@gareus.org</a>> wrote:<o:p></o:p></p><p class=MsoNormal style='margin-bottom:12.0pt'>On 10/29/2012 03:55 PM, Ivica Ico Bukvic wrote:<br>> All,<br>><br>> I noticed since upgrading to Ubuntu 12.04 that the default Jack server is<br>> jackdmp (v.1.9.8). Please correct me if I am wrong but my understanding this<br>> is the smp-enabled version 2 that is being developed in parallel with 1.x<br>> series of regular jack.<br><br>correct. They are also API and ABI compatible.<br><br>> Either way, one of my concerns is that while in the old jack when one<br>> accidentally pulled the soundcard jack was trying to talk to (e.g. a USB<br>> soundcard), the jack would gracefully stop.<br><br>In my experience it stopped but never gracefully (ie it crashed). but<br>it's been a while since I used jack1.<br><br>> The new version (and this could<br>> be Ubuntu quirk) instead of stopping is pegged in some kind of a spinlock<br>> that often times locks up the machine (this may be in part since I am<br>> running a lowlatency kernel with audio group given priority) and at times<br>> keeps it operational while hogging the cpu and making the computer barely<br>> responsive until jackd is killed. Apps connected to jack that I tested so<br>> far are also stuck in a loop waiting for a response from jack (although this<br>> could be the app's shortcoming)--jack never broadcasts a signal that it has<br>> lost the soundcard (AFAICT). FWIW I am running jackdmp through qjackctl...<br>> Any thoughts on this matter would be most appreciated.<br>><br><br>I can't reproduce this. jack2 stops the backend when the device is<br>disconnected. You can switch to a new backend using jack_control<br>(sending some Dbus messages to jackd) without re-starting jackd. No CPU<br>hogging here. - I'm running jack2 - aka 1.9.9.4 from git.<br><br>robin<o:p></o:p></p></div></div><div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><div><div><p class=MsoNormal><o:p> </o:p></p></div></div></div></div></div></body></html>