When Helix receives MIDI Clock, tempo changes cause delay pitch morphing even with Tap Tempo Pitch set to Transparent

[eightthree]

Recently I started exploring using an external tracks rig sending MIDI clock to my Helix so that my tempo is always in sync with the song we're playing. Helix is receiving MIDI Clock and adjusting without issue, however, when the tracks rig stops playing, the MIDI Clock stops transmitting. Once Helix is no longer receiving MIDI Clock, the tempo will reset to whatever is defined on the preset or snapshot – and this causes noticeable delay morphing and pitch changes. In my global settings & preferences I specifically have tap tempo pitch set to Transparent. Tap tempo doesn't cause morphing, changing between snapshots with different tempo values also doesn't cause these pitch issues either.

 

So, my question is – is there a way to also have the Helix respect this transparency setting after MIDI Clock stops transmitting? Is this a bug? Is there something I'm missing?

 

Ideally, I would love for MIDI Clock to set the tempo, and then if that clock ever stops transmitting I'd love for Helix to just stay at whatever the last known tempo was until I explicitly change it (either by tapping, changing snapshots, or changing presets). Is there a better way to accomplish this?

[DunedinDragon]

For the last few years I've been using my Helix in the same manner with external tracks but I quickly began to understand the deficiencies that can arise using an external MIDI clock.  So in my case, because I have a separate preset for each song, I save the tempo to be consistent with the track it will be used with and that works flawlessly.  There may be other ways to configure it to share a common clock, but my approach is bullet-proof, so I've never pursued anything else.  I know the MIDI clock definitions and functions will be changing soon with the new MIDI specifications now coming out, but that won't affect me.