<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">On 1/27/22 1:08 PM, Paul Davis wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAFa_cKnWV1f+kF_yKvwtRsqF0ihT9+SHSYP8DA8h-qifAK3Qag@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div dir="ltr">
<div class="gmail_default"
style="font-family:arial,helvetica,sans-serif"><br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Thu, Jan 27, 2022 at
10:37 AM Tim <<a href="mailto:termtech@rogers.com"
moz-do-not-send="true">termtech@rogers.com</a>> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">On 1/27/22 3:42 AM, Wim
Taymans wrote:<br>
> * an 8 slot lookahead windows for repositions and tempo
changes (let <br>
> clients<br>
> prefetch data in time)<br>
><br>
<br>
This sounds tantalizing.<br>
<br>
Any possibility of implementing some kind of full shared
tempo map<br>
<br>
so that an app can read another's tempo map so that one
app's time-line<br>
<br>
can match what another (master) app's time-line says?<br>
<br>
<br>
I know there are some difficulties with that concept, but
could they be <br>
overcome?<br>
</blockquote>
<div><span class="gmail_default"
style="font-family:arial,helvetica,sans-serif"></span></div>
<div><span class="gmail_default"
style="font-family:arial,helvetica,sans-serif">Given that
we've seen plugins explode because Ardour uses exponential
tempo ramps (like humans do) rather than linear, I'm
pessimistic.<br>
</span></div>
<br>
</div>
</div>
<br>
</blockquote>
<br>
<p>Hiya Paul. Could you explain that a bit more?</p>
<p> Human exponential vs. linear, I don't quite understand.</p>
<p> And can you remember which types of, or specific, plugins would
fail, and why? I'd like to investigate.</p>
<p>Thanks.<br>
</p>
</body>
</html>