04-01-2020, 02:54 PM
I never had any issues with being Midi-Slaved nor i got any bug reports regarding that.
So lets investigate further before moving it to the bad-bug crash topic.
I expect you use the latest version V1.21?
Does it switch to the weird BPM by itself? Does it switch when you change patterns/stop patterns? How do you know Ableton or your Midi-Interface is not causing this problem? When it returns to normal, is it still in sync with your ableton lines? Maybe you have some other gear that you can run also as slave clock with a thru box to just be sure that it only happens with the NerdSEQ.
Is it with all projects or project related? Are you editing and it suddenly happens?
I'm just curious because if Midi-Slaved, then everything is only related to the receiving ticks. So only with receiving ticks the sequencer is continuing and it doesn't create own ticks or timings (like it does when slaved to 1/16 clock).
So lets investigate further before moving it to the bad-bug crash topic.
I expect you use the latest version V1.21?
Does it switch to the weird BPM by itself? Does it switch when you change patterns/stop patterns? How do you know Ableton or your Midi-Interface is not causing this problem? When it returns to normal, is it still in sync with your ableton lines? Maybe you have some other gear that you can run also as slave clock with a thru box to just be sure that it only happens with the NerdSEQ.
Is it with all projects or project related? Are you editing and it suddenly happens?
I'm just curious because if Midi-Slaved, then everything is only related to the receiving ticks. So only with receiving ticks the sequencer is continuing and it doesn't create own ticks or timings (like it does when slaved to 1/16 clock).
PLEASE use the search function if something have been asked or discussed before.
Every (unnessesary) forum support means less time to develop! But of course, i am here to help!
Every (unnessesary) forum support means less time to develop! But of course, i am here to help!