Nerdseq as MIDI slave / bpm glitch

[marek]

Hi, I have Nerdeq set as MIDI slave. Clocked by Ableton Live. Everything works fine, rock solid. When I press start in Ableton, Nerdeq starts on selected row.
But I experienced something strange. When it was running, it changed bpm to like 1000, I mean very high value. Can't see it as Nerdseq is in slave mode. But project is about 6-7 mins long and it runs through it like 4 times in 10-15 seconds. Then it returns to normal. 
I started to use it this way for this project about week ago. It was running about 2-3 hours a day and it happened 2 times.

---

I think I should post it to "The really bad bugs -> crash" since it is unable to work with it in that state.

[XORadmin]

Do you switch to master mode and then it is at 1000 bpm?

Or did it run in slave mode at 1000 bpm 'as in' it doesn't slave well to midi?

[marek]

Do you switch to master mode and then it is at 1000 bpm?

Or did it run in slave mode at 1000 bpm 'as in' it doesn't slave well to midi?

No, it is in slave mode all the time. It happened randomly while playing. And it return to normal after few seconds.

[XORadmin]

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).

[marek]

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).

Hello Thomas. Yes, I have the latest version 1.21. It does switched by it self while playing. I have not touched anything. It was just playing and suddenly jumped to high bpm. I did not experienced this problem since I reproted it on the forum. Maybe it is problem with Ableton or my Audio interface. From what I observed I cannot tell. I experienced it only in this one project and it is the only project I did in 1.21v. Now it is finished and I am starting new project so I will see if it will happen again.