Hi,
I have a problem when i’m jamming with a 2 patterns chain.
The same roland se-02 patch is set on MIDI A track.
The cutoff cc value is set to 45 both on the se-02 and the DT.
I’m playing with the cutoff knob and when the pattern change, if the cutoff value if too far from 45 a ‘CLIC’ appears because of the gap between the current cc value and the default cc pattern value.
Is there a way to avoid this ?
If you prefer to control the parameter manually, don’t automate it in your sequencer patterns.
Not that I can see.
The parameters are saved with the tracks in a pattern.
Perhaps if you were to trigger the pattern change externally while using ‘Control All’ on the DT parameter, it might work.
Alternatively you could restrict your jamming a little by noting what value you need to be at (or close to) before the pattern change - get there in time and CLIC wouldn’t be so abrupt. Might create something rhythmically interesting to be returning to the same CutOff (or whatever) value each bar.
The cc cutoff is not automated in the DT but when i pass from A1 to A2, the default cutoff value is reloaded from the se-02 patch as well. The only way i found is to turn the cutoff knob faster at the start of the A2 pattern to force a newest value and avoid the ‘clic’ sound. It’s annoying to think about that when i’m jamming.
I’m doing this right now but it’s a bit tricky because A1 is a 4:4 patern and A2 a 2:2 so i’m not really at the better position when the pattern change is coming. I also think to set an LFO to automate the cutoff but i really like to manually move this one. I think i’m not the only one !
Maybe i should replace the cutoff knob on the se-02 to have a better view of the arrow position ?
hi @9uile this is my problem too, have you find another solution?
What happens if you put a parameter lock on cc at the end of first pattern to bring it back to 45…?
No, i think the mightlife answer i the best solution.
I don’t think that it was better because the problem will occurs when the pattern changes and also when it loops.
This happens because the CC changes are sent AFTER the first Note On message when a pattern change happens.
Any other sequencer would send the CC changes BEFORE the first Note On.
It’s really annoying and creates a lot of problems. I consider this a bug.
Ok. How about turn off LFOs on the trig page. Parameter lock a ramp lfo set to half wave about 8 trigs from the end of the pattern. Use fade to iron out the gaps. Does that work?