<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Yes I often use Ardour and Mixbus32c but I do not actually use it
for this problem: I just use seq24, seq64 and Giada:<br>
<br>
I am on ubuntu studio64 with 2 multiface II sound cards + ESI M4U Xt
midi usb interface<br>
<br>
<u><i>Try to create a minimal setup, which still exhibits the
problem</i></u>:<br>
<br>
With seq24 I control 4 synthesizers : SE-02, Andromeda, Solaris and
a Q Rack with midi pattern + the DSI Tempest set as slave and all
are connected in seq24 interface. The seq24 different patterns are
connected to the different synthesizers by this way: just right
click in the pattern and choose the midi bus. In the option menu of
seq24 I put on the midi clock on the midi channel of the tempest :
[4] 28:3 (ESI M4U XT midi 4) ---> on <br>
<br>
At this time everybody work fine but when I wanted to record the
pattern loops in Giada (audio software) I had to connect Giada and
seq24 to jack to make them synchronize and at this time I had the
problem with the Tempest: 77 bpm <span class="tlid-translation
translation" lang="en"><span title="" class="">instead of 120 bpm.
At the beginning I thought that it was the fault of Giada but </span></span><span
class="tlid-translation translation" lang="en"><span title=""
class="">when I eliminated Giada of the setup, </span></span><span
class="tlid-translation translation" lang="en"><span title=""
class="">the problem persisted.</span> <span title="">It
appears when I connect seq24 to jack.<br>
<br>
So </span></span><span class="tlid-translation translation"
lang="en"><span title=""><span class="tlid-translation
translation" lang="en"><span title="" class="">to summarize
the moment when the problem appears, I do not use audio
software, only midi with seq24 which drives the synthesizers
and the Tempest as Slave.<br>
</span></span></span></span><br>
<span class="tlid-translation translation" lang="en"><span title=""><span
class="tlid-translation translation" lang="en"><span title=""
class=""><span class="tlid-translation translation"
lang="en"><span title="">To have a minimal setup now </span></span></span></span></span></span><span
class="tlid-translation translation" lang="en"><span title=""><span
class="tlid-translation translation" lang="en"><span title=""
class=""><span class="tlid-translation translation"
lang="en"><span title="">which still exhibits the problem,
now I have only seq24 connected to the Tempest. <u><i><br>
<br>
</i></u></span></span>(I also tried to connect the
Tempest to my master midi i/o multiface but the problem
persist.)<br>
<br>
Philippe<br>
</span></span></span></span><br>
<br>
<div class="moz-cite-prefix">Le 03/10/2019 à 17:10, Christopher
Arndt a écrit :<br>
</div>
<blockquote type="cite"
cite="mid:e6752f63-4a3d-da3f-5fce-a18ac73c269d@chrisarndt.de">(Re-directing
the discussion to the mailing list again.)
<br>
<br>
Am 03.10.19 um 15:03 schrieb Philippe GARCIA-ORTUNO:
<br>
<blockquote type="cite">Yesterday I made a test to connect seq24
(in seq24 send the clock to midi Throught and then connect midi
Trought to Ardour MMC, Ardour+seq24+Tempest played well at 120).
<br>
</blockquote>
<br>
So is Ardour normally involved in your setup? Can you describe
exactly, which (audio) software you are running and what is
connected where and to what (audio and midi, ALSA, JACK and
hardware MIDI connections)? Try to create a minimal setup, which
still exhibits the problem.
<br>
<br>
<br>
<br>
Chris
<br>
_______________________________________________
<br>
Jack-Devel mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:Jack-Devel@lists.jackaudio.org">Jack-Devel@lists.jackaudio.org</a>
<br>
<a class="moz-txt-link-freetext" href="http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org">http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org</a>
<br>
<br>
</blockquote>
<br>
</body>
</html>