<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On 2015-04-17 12:17 -0500, Fernando Lopez-Lezcano <span dir="ltr"><<a href="mailto:nando@ccrma.stanford.edu" target="_blank">nando@ccrma.stanford.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">On 04/16/2015 01:16 PM, Don Estabrook wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">. . .</blockquote><span><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
So, just wondering whether others have seen any of these issues [with JACK2].<br>
</blockquote>
<br></span>
Not really.</blockquote><div><br></div><div>Good to know - it wouldn't be the first time it was only me. :-) </div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
If so, might it make sense for CCRMA (or, Fedora?) to switch to JACK1 ? Or are there dependencies on JACK2 functionality that would make that problematic?<br>
</blockquote>
<br></span>
I'm all for keeping jack2. Unless this has changed recently, jack2 is the only one that can schedule processes on more than one core if the jack connection graph dependencies allow it to do so. I think jack1 can't do that, and that is a deal breaker for me (I do want to be able to (ab)use all cores in modern machines).<br>
<br>
YMMV...<br></blockquote><div><br></div><div>From what I've read, I think you're correct, and I'm all for utilizing multiple cores too. Making a blanket choice between them seems to be not quite straightforward, with potential pluses and minuses on both sides</div><div><br></div></div></div><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px"><div class="gmail_extra"><div class="gmail_quote"><div><a href="https://github.com/jackaudio/jackaudio.github.com/wiki/Q_difference_jack1_jack2" target="_blank">https://github.com/jackaudio/jackaudio.github.com/wiki/Q_difference_jack1_jack2</a></div></div></div></blockquote><div class="gmail_extra"><div class="gmail_quote"><div> </div><div>and some of those might be more or less important, depending on what one is trying to do. As you say, taking advantage of more than 1 core isn't always possible. OTOH I think uninterrupted audio when connecting/disconnecting apps is very nice, especially when the output potentially goes somewhere that others can hear it. &c.</div><div><br></div><div>So despite how my initial question may have sounded, I'm not on any kind of ideological mission to get CCRMA or Fedora to change. :-) If I'm the only one seeing these issues, I'm quite okay with building JACK1 myself as a work-around for the time being. Just thought I'd let you know about it.</div><div><br></div><div>A4 can also connect directly to sound devices through ALSA - so no JACK needed - handy for someone using Ardour stand-alone. I haven't tried that yet.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
I don't know about Fedora (you would have to file a bug report) but I could package git as a test if there are improvements there. I fuzzily seem to remember some LAU/LAD post about jack2 improvements recently.<br></blockquote><div><br></div><div>Both of their Git repos have a number of commits since their last tags, and actually JACK2's latest is chronologically newer than JACK1's. Indeed, JACK2 has some very recent commits - within the last few days... Sometimes fuzzy memories are good ones!</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
>From the way you describe things it would appear these are bugs in Ardour4 (or in jack2 and they are uncovered by corner cases in Ardour4)....<span><font color="#888888"><br></font></span></blockquote><div><br></div><div>Could be. Paul has said that at least one issue is a result of A4 using a command-line option that JACK2 doesn't support. (I see arg parsing code for it in 1.9.10 and much earlier, but I'm guessing it doesn't work underneath.) AFAIK my issues were not related to this however. The hang-on-export problem was apparently a known issue with 1.9.9, and fixed after that - but for me it was 100% repeatable (well, 2/2 - all I had patience for) with 1.9.10.</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span style="color:rgb(136,136,136);font-size:12.8000001907349px">-- Fernando</span></blockquote><div><br></div><div>- Don </div></div></div></div>