02-09-2020, 12:15 PM
Seeing your video together with what is in the patterns matches. I don't see an issue here. It looks like it does in the video exactly what it should do.
Also testing the sent program changes together with your sequences it always behaved as it should. Only program changes are sent if the pattern passes the pattern row and if it wasn't the same program before on the midi channel. (And it sent them exactly on position 3A in the row as intended)
A stop of the pattern (pressing stop once) never sent an extra program change, only if the pattern played until the end and also here passed the program change command on 3A with a different value. (with your settings, 'On change' turned on)
Let me explain how program change works and why i added the feature to either send it always or just 'on change':
Program changes in Midi are usually to change the instrument of a midi device, eg. Change from a Piano sound which is on Program #0 to a String sound which might be program #4. So the moment the sequencer passes the row with the program change command #4 it will change the instrument to a String.
The NerdSEQ never sends any Program Change messages except for the ones that are filled in the patterns and only if it passes them.
Then they are many Midi devices which need some time until the instrument changes to another instrument. Sometimes half a second to a second. Even new synthesizers sometimes have that. And these also have this 1 second timeout if you change from Program #4 to Program #4 which would happen if you play a pattern twice. A timeout of 1 second when receiving the program change message. For that reason i added the feature of either send the program change always or on change. So with 'On Change' it sends the program change ony if the last program change command for the same midi channel was a different 'instrument' than before. With that the timeout is avoided except for the very first time. For the rest it is of course 'smart' programming of your sequences to take care the program changes are being sent when wanted.
If the elektron device uses the program change command to change patterns thats fine. And of course that have to happen before the current pattern is ready (same with nerdseq, you choose the next playing pattern before it is finished and it also finishes first before the new one is going to play). I don't know if it queues the pattern change, if it keeps the queue also when the sequencer is stopped. Maybe that could explain that you think the pattern on the Elektron has been changed even if you pressed stop, but in fact, it sent the change on 3A and the elektron took that command and changed the pattern after it was finished. I wouldn't use it with the 'On Change' feature as then you wouldn't be able to control to play a pattern on the elektron twice or more (if it changes by itself automatically to next patterns).
So i assume that the function works as it should. I don't see a bug at all here.
But of course if you got more info to show me that i'm wrong, let me know!!
Also testing the sent program changes together with your sequences it always behaved as it should. Only program changes are sent if the pattern passes the pattern row and if it wasn't the same program before on the midi channel. (And it sent them exactly on position 3A in the row as intended)
A stop of the pattern (pressing stop once) never sent an extra program change, only if the pattern played until the end and also here passed the program change command on 3A with a different value. (with your settings, 'On change' turned on)
Let me explain how program change works and why i added the feature to either send it always or just 'on change':
Program changes in Midi are usually to change the instrument of a midi device, eg. Change from a Piano sound which is on Program #0 to a String sound which might be program #4. So the moment the sequencer passes the row with the program change command #4 it will change the instrument to a String.
The NerdSEQ never sends any Program Change messages except for the ones that are filled in the patterns and only if it passes them.
Then they are many Midi devices which need some time until the instrument changes to another instrument. Sometimes half a second to a second. Even new synthesizers sometimes have that. And these also have this 1 second timeout if you change from Program #4 to Program #4 which would happen if you play a pattern twice. A timeout of 1 second when receiving the program change message. For that reason i added the feature of either send the program change always or on change. So with 'On Change' it sends the program change ony if the last program change command for the same midi channel was a different 'instrument' than before. With that the timeout is avoided except for the very first time. For the rest it is of course 'smart' programming of your sequences to take care the program changes are being sent when wanted.
If the elektron device uses the program change command to change patterns thats fine. And of course that have to happen before the current pattern is ready (same with nerdseq, you choose the next playing pattern before it is finished and it also finishes first before the new one is going to play). I don't know if it queues the pattern change, if it keeps the queue also when the sequencer is stopped. Maybe that could explain that you think the pattern on the Elektron has been changed even if you pressed stop, but in fact, it sent the change on 3A and the elektron took that command and changed the pattern after it was finished. I wouldn't use it with the 'On Change' feature as then you wouldn't be able to control to play a pattern on the elektron twice or more (if it changes by itself automatically to next patterns).
So i assume that the function works as it should. I don't see a bug at all here.
But of course if you got more info to show me that i'm wrong, let me know!!
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!