11-28-2020, 08:27 AM
(This post was last modified: 11-28-2020, 08:29 AM by MrBlaschke.)
I tried to reproduce this error for the last 2 hours - nevermind, just wanted to play with the NDLR and experimented with the settings anyway 
I recreated your setup but i do not have Cakewalk - i used my AUM (iPad) as a Clock and the NDLR stays rock solid.
The 2nd difference is i am on FW 1.1.070.
No chance to get him off the clock.
Do you have another clock to verify that - maybe the clock from Cakewalk is jiggly?
Another try would be to reset the device, but in that case i would suggest to update to 1.1.70/1.1.71.
You will loose the stored Rhythms/Patterns in that case!! Be aware of that.
Damn - during testing and writing my prev questions there where some answers...Sorry...Should have refreshed before writing.
I would strongly request testing with another clock as i have some „unstable“ clocks in my arsenal for sure that tricked me from time to time.
I recreated your setup but i do not have Cakewalk - i used my AUM (iPad) as a Clock and the NDLR stays rock solid.
The 2nd difference is i am on FW 1.1.070.
No chance to get him off the clock.
Do you have another clock to verify that - maybe the clock from Cakewalk is jiggly?
Another try would be to reset the device, but in that case i would suggest to update to 1.1.70/1.1.71.
You will loose the stored Rhythms/Patterns in that case!! Be aware of that.
Damn - during testing and writing my prev questions there where some answers...Sorry...Should have refreshed before writing.
I would strongly request testing with another clock as i have some „unstable“ clocks in my arsenal for sure that tricked me from time to time.