I have a problem with MIDI sync using the official 1.25 firmware. On the earlier 1.25RC5 firmware it worked fine. I use the TRS-A MIDI expander.
When I start a row of patterns, the sequence (a patch with arp) I start on my wavestate doesn't always start on the beat, like if the midi-clock is delayed. It keeps sync but not on the beat. Sometimes I can be lucky and start it on the beat, but with the 1.25RC it always started on the beat. I will test further on other synths tomorrow, but as said, it did work without problems on the RC versions of the firmware.
(10-16-2021, 10:48 PM)JX3D Wrote: I have a problem with MIDI sync using the official 1.25 firmware. On the earlier 1.25RC5 firmware it worked fine. I use the TRS-A MIDI expander.
When I start a row of patterns, the sequence (a patch with arp) I start on my wavestate doesn't always start on the beat, like if the midi-clock is delayed. It keeps sync but not on the beat. Sometimes I can be lucky and start it on the beat, but with the 1.25RC it always started on the beat. I will test further on other synths tomorrow, but as said, it did work without problems on the RC versions of the firmware.
Hmm... I am going to test that as well. I wouldn't know if there is any issue with that. Swing zet to zero??
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!
Yes, swing at zero. Has earlier been set to +03 in same project (think I noticed a problem saving that value, a few saves ago, but it does save it now).
The current track is a lower speed track (/4), if it helps provoking the error. I wll try to make a new MIDI track to test it there too.
Just compared with sync out, and that is tight - and a bit ofset from the midi sync - depending on starting it on the beat or not.
About that the swing probably didn't save. Swing is only active if you use the internal clock. If you switch to external clock the swing is automatically set to 0.
About the sync issue. I just tried that, using midi in and out and in no way I could get it out of sync. It starts as it suppose to be and starting stopping several times works just fine.
I tried with slow and fast BPM and also with clock divisions (I assume you divide just a track with 4, right?) comparing 2 bassdrums one from the midi master and one from the slave, using 2 NerdSEQ and 2 sample channels to play the drums.
So the question is, how do you start/stop? Is the Wavestate or the NerdSEQ the master in the chain?
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!
10-17-2021, 12:07 PM (This post was last modified: 10-17-2021, 12:48 PM by JX3D.)
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.
Ok fine! I will try to reproduce it later today.
Do you use the normal launch mode or the sync launch mode?
Sorry for the trouble.
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!
10-17-2021, 01:46 PM (This post was last modified: 10-17-2021, 01:54 PM by JX3D.)
I am not really sure what it means (normal launch mode vs sync launch mode), but I do press SHIFT+START to start a row.
After reading page 18 in the 1.25 manual, I beleive I run in nomal launch mode. But again I may misunderstand what it means?
Just found it in setup, if its "Pattern Launch Type"? Its set to SYNC.
Also, I beleive I changed the "Reset FX on Seq Stop" to ON recently. And the problem is quite new to me, so it may have an impact?
I think the launch type might have impact here since it seems to be an issue after stopping a track (through **) and starting again.
Actually I don’t think in this combination that it is a sync problem. But that’s a ‘guestimation’ for now. Let’s see if I can reproduce it somehow first.
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!
10-17-2021, 03:21 PM (This post was last modified: 10-17-2021, 03:28 PM by JX3D.)
Yes I think it has to do with the use of ** too. It seems to become unstable after using that - and my odd pattern lengths may help provoking that problem - or not ;-)
Yes, tried to set it to Normal launch mode, saved the project and restarted. Then its in sync, even after using the ** row. But the its not acting as I planned. Well I can work with that, but would be nice if it worked in Synced launch mode too. The problem is connected to that - it seems.
I could reproduce the issue!!
It happens only in SYNC Launch mode. And it happens only indeed if the track was stopped using **. And then only if in combination with a clock divider on that track. Yes and only then :-)
So it is not related to Midi and not to sync.
If you stop the track regulary with the buttons then there is no issue, starting it again starts it nicely.
I think it should be a simple thing to fix. I will most probably have an update tomorrow. Until then either avoid ** or use the normal launch mode (which is the one as it used to be).
Sorry for the trouble, but also thank you for helping hunting for the problem.
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!
