<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 2/23/2016 8:03 AM, Paul Davis wrote:<br>
<blockquote
cite="mid:CAFa_cK=-3jPundFpskZki3ftUzeyb5yG-oFW+nZu3cqY=ndcZA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>Every N msecs, your audio interface wakes up the CPU to
tell it to read and write X samples of audio data. The CPU
(and the OS) in turn wakes up JACK to tell it do the same,
along with any other processing that is part of that.<br>
<br>
</div>
<div>If it takes JACK N msecs to finish the task, the DSP load
is 100%.<br>
</div>
<div>If it takes JACK 0.0000001 msecs to finish the task, the
DSP load is very close to 0%.<br>
</div>
<div>If it takes JACK N/2 msecs to finish the task, the DSP load
is 50%.<br>
<br>
</div>
<div>Values about 80% appear unstable/unusable on all 3 of
Linux, OS X and Windows.<br>
</div>
</div>
</blockquote>
<br>
So, if one has a lot of things happening, multiple JACK instances
could make more use of available resources? The thought (in my
case) is to have one JACK connected to the single audio output, and
then have two more feeding in? I'm not sure how to get MIDI trigger
signals to the other two though...<br>
<br>
-- <br>
<div class="moz-signature">
<div style="color: #993300; font-size: 0.8em; font-style: italic;">
Jonathan E. Brickman <a class="moz-txt-link-abbreviated"
href="mailto:jeb@ponderworthy.com">jeb@ponderworthy.com</a> (785)233-9977<br>
Hear us at <a href="http://ponderworthy.com">http://ponderworthy.com</a>
-- CDs and MP3 <a
href="http://ponderworthy.com/ad-astra/ad-astra.html">now
available!</a><br>
Music of compassion; fire, and life!!! </div>
</div>
</body>
</html>