On Sun, Feb 23, 2020 at 11:28:22AM +0100, Jeanette C. wrote: > Hi Alexandre, > thanks for your reply. I must apologise for my slightly inacurate description. > > The external clock source is sync'ed to my audio software. Midish follows it > nicely. It reacts to start and stop commands. But it seems that my hardware > synth doesn't lock onto the clock pulses. I have connect the synth directly > to the jack_midi_clock and it is absolutely on time. The synthesizer's > device is created statically at the beginning of .midishrc. So it exists > long before the external clock is dynamically added. Also the dclktx [dlist] > is immediately following the dnew statements. > > Still, the synth's LFOs drift like they were still connected to Midish's > normal internal clock source. If the synth were to get no clock at all, it > wouldn't noticeably drift backwards and forwards. It might slowly get out of > sync all together. But the LFOs never lag behind a full cycle, so they are > catching up to something from Midish. > > Considering that jack_midi_clock will send both start and stop and the clock > pulses, is there anything else that I should do within Midish? As you describe it, it's supposed to work. Could you send me the output of: for i in [dlist] { print $i ; dinfo $i; } end the vendor and model of your synth, I'll look if the manual says something abount synchronization to external clocks.Received on Tue Feb 25 2020 - 16:54:59 CET
This archive was generated by hypermail 2.3.0 : Wed Feb 26 2020 - 01:33:10 CET