Good idea, but…(hehe) it´s like a drone that I will be changing the waveform and effects, etc…so, no, I can´t sample it. But thanks, good idea.
ok, and the breath control set to 0 for the last step didn’t work? hmm how about you send a 4 note chord to kill all the available polyphony at once (choke the old note) but at the same time p lock the track level to 0 using a volume cc on the midi amp page and set the level from the filter page where it reflects the 6 cc value knobs? you could try cc 95 for track level, or if that doesn’t work you could try cc 7 which should be the value for volume on the amp page. I mean again, no guarantees but if you really need this to work try whatever you have to.
Could the second note, on the incomming pattern, be a pitch bend CC p-lock, instead of a note?
Hiw do I change the pitch bend on that note when I change the pattern without affecting to the other notes? Maybe I could use 2 different tracks. 1 for the drone, 1 for the melody
So you want a drone and the melody on the same sound, coming from the same synth. You can’t play the drone manually with the melody, so you want that part automated.
Have I described the problem reasonably?
Pattern change to a shorter pattern where you can stop the note after 64 steps.
1 Like
So, I thought about it, and while you can’t P-lock a midi channel change, you can assign a new midi channel to a new pattern. If you change the channel as the pattern changes, won’t that kill the drone note also? It should read as note off as soon as trig data from (example) channel 1 disappears (receives the channel off command) and channel 2 picks up. I understand you don’t want to kill the drone note UNTIL the pattern change occurs so you can’t really switch to a fixed length pattern without interrupting the drone, but at the pattern change the note is going to change anyways. If the synth is multitimbral I also think the 2 channel method would work, but if nothing else we’ve suggested worked so far, I’d see if changing to a new midi channel at the pattern change and just having the same patch assigned to channel 2 will end the note data for channel 1 and allow you to move seamlessly into the second pattern.
1 Like
Yes, correct. Thanks
1 Like
I don’t know if this has been answered but you can trigger the same note again, making sure that you send a note off message for that dame note number. You will get a double note trigger but the note off should kill both notes.
So on the beginning of the new pattern, put a very short note trigger and that should solve it. Not ideal but simple.
You’re right, you can’t select VEL=0. My mistake.
Can you really hear VEL=1 at LEN=0.smallest_I_cant_remember_the_number_but_its_really_short
1 Like
This is, of course, my favorite number and I’m surprised you’ve heard of it. You should join our BBS.
2 Likes
What if you did like already suggested - program the shortest note possible with the lowest velocity on the first step of the 2nd pattern - as well as assigning a MIDI CC to filter cutoff and parameter lock the cutoff at 0. I can’t imagine anyone would hear that.
how about this…
- pat 1: pattern with INF trig
- pat 2: you want to change patterns, make new duplicate pattern of pat 1 with a TRIG release set to fade out at the length you’d like
- pat 3: new pattern
Trig release? How? Thanks
did @antispop ever find an acceptable workaround?
I have basically the same problem on syntakt, and the most reasonable suggestion here seemed to place a trig with low velocity and time on the final step of the sequence. I gave the first, infinite trig a 1st-only condition, and I gave the final cutoff trig a fill-only condition.
This enables me to switch to any pattern and cut off the drone. So when I know I want to switch to a pattern which doesn’t have the drone, I first do a fill, wait for the fill to be active, then select the new pattern. The difficulty is remembering to do it, doing it in that order and waiting for the fill cycle to start before selecting the new pattern (otherwise you change to the new pattern without your fill and choke note ever occurring). In OP’s case, where they’re also trying to play other notes or manipulate other gear, it’s totally understandable why this is not a completely acceptable solution.
Wondering if anyone else has had any other takes on this problem?