I cant get the error to appear today, and I really don't understand why. I did switch off and on everything yesterday (eurorack and wavestate - MIDI connected directly between them), so it should have solved it then. I tripple checked it, and had the problem each time. But today its working from first try? Strange. I even tried to make a new project yesterday that made the same error. I will see if I can provoke the error to happen again, and find out whats causing it, if it will happen again. The only reason I can think of for now is either a bad cable or connection, radio-interference or a glitch in the wavestate. So for now Thomas, see it as a "user-glitch" and forget about it. I will write if the problem appears again.
While I had the glitch yesterday, changing the division/multiplication of a tracks speed, caused strange behaviour on the MIDI track, making it almost impossible to get back to the original division. But...
...it could be a glitch in the Wavestate, even though it was switched off and on several times. I did try different patches on it, and if using a patch without arp, the notes was hit exactly on the beat. So it had to do with the sync, either externally or internally in the wavestate - but I tend to think of the latter. If it happens again, the first thing to try, is to switch of the wavestate for several minutes, perhaps even take out the power cable and turn it on before inserting the power cable again and turning it on.
I use internal clock in the NerdSeq, and didn't select external at any time - it was the value 0 that wasn't recalled, it started at +03 when I loaded it after upgrading to the official firmware. I am almost sure I saved it without swing in the RC5 version. But after saving it without swing with the new version, it reloads fine now.
But I may remember wrong, as I may have been doing some testing with swing on before upgrading (I always save before switching off), so if no one else has reported about it, just forget it ;-)
Thanks for your support - and for the great work you do.
And now, minutes after replying above, I get the problem again. I will attach the project.
It seems to happen if I play row 11 (**) with SHIFT+START and afterwards row 13 with SHIFT+START. Sometimes it hits on the beat, other times not.
Track 5 is the midi-track playing on channel 9. Track 4 is drums (trigger 16: 1-4 is drums, rest is trigs for Beads, etc.) which always start in sync.
All tracks only use steps 00-0B - though thats not how the ** tracks work (would be nice to be able to set the length of that too).
And now tested with a Hydrasynth. Same problem.
While I had the glitch yesterday, changing the division/multiplication of a tracks speed, caused strange behaviour on the MIDI track, making it almost impossible to get back to the original division. But...
...it could be a glitch in the Wavestate, even though it was switched off and on several times. I did try different patches on it, and if using a patch without arp, the notes was hit exactly on the beat. So it had to do with the sync, either externally or internally in the wavestate - but I tend to think of the latter. If it happens again, the first thing to try, is to switch of the wavestate for several minutes, perhaps even take out the power cable and turn it on before inserting the power cable again and turning it on.
I use internal clock in the NerdSeq, and didn't select external at any time - it was the value 0 that wasn't recalled, it started at +03 when I loaded it after upgrading to the official firmware. I am almost sure I saved it without swing in the RC5 version. But after saving it without swing with the new version, it reloads fine now.
But I may remember wrong, as I may have been doing some testing with swing on before upgrading (I always save before switching off), so if no one else has reported about it, just forget it ;-)
Thanks for your support - and for the great work you do.
And now, minutes after replying above, I get the problem again. I will attach the project.
It seems to happen if I play row 11 (**) with SHIFT+START and afterwards row 13 with SHIFT+START. Sometimes it hits on the beat, other times not.
Track 5 is the midi-track playing on channel 9. Track 4 is drums (trigger 16: 1-4 is drums, rest is trigs for Beads, etc.) which always start in sync.
All tracks only use steps 00-0B - though thats not how the ** tracks work (would be nice to be able to set the length of that too).
And now tested with a Hydrasynth. Same problem.