08-07-2019, 01:08 PM
Some interesting ideas there Tim, thanks!
For the Key and Mode setting, maybe there is something we can do to make it so you don't have to enter it for every step. Otherwise, its a very powerful part of the sequencer which lets you play "any" chord by switching key or mode to get to a different root. However, I see how you might not want to have to set it for every step, but it doesn't take too long either. Maybe it should keep the last Key and Mode for the next step if the next step duration is 0. Would be interested to hear how people would like this to work.
I think what you are looking for here is a PAD sequencer. The Chord Sequencer is a global chord sequencer for all of the NDLR parts, not just the PAD. The PAD gate length is something we've discussed a few times in the past. We'll still keep it on the wish list but it would be quite a challenge to re-architect the code to control PAD gates separately from the other parts. We never thought of the PAD part as a general purpose chord player, but rather a PAD player in the synth sense. Where a PAD patch typically has a rich evolving texture kind of like a polyphonic drone. So the scope of its feature set might be a bit narrow compared to something that lets you record a sequence while playing for example. The Arturia Keystep is actually great for that as you can insert rests to limit the chord duration. Oh, and Steve is looking into doing that too, so maybe there is hope :-)
Using patterns as a chord sequence works great for doing algorithmic like sequencing where you are not too concerned with timing or specific notes. The pattern doesn't know anything about notes because its relative to the note pool based on the key and mode. Where in the chord sequencer you explicitly choose these things. Think of the pattern as an LFO as a custom waveform rather than a sequence and you will get the idea. The other downside with pattern controlling chord is its not possible to time chord type with chord changes like you can in the sequencer.
For the Key and Mode setting, maybe there is something we can do to make it so you don't have to enter it for every step. Otherwise, its a very powerful part of the sequencer which lets you play "any" chord by switching key or mode to get to a different root. However, I see how you might not want to have to set it for every step, but it doesn't take too long either. Maybe it should keep the last Key and Mode for the next step if the next step duration is 0. Would be interested to hear how people would like this to work.
I think what you are looking for here is a PAD sequencer. The Chord Sequencer is a global chord sequencer for all of the NDLR parts, not just the PAD. The PAD gate length is something we've discussed a few times in the past. We'll still keep it on the wish list but it would be quite a challenge to re-architect the code to control PAD gates separately from the other parts. We never thought of the PAD part as a general purpose chord player, but rather a PAD player in the synth sense. Where a PAD patch typically has a rich evolving texture kind of like a polyphonic drone. So the scope of its feature set might be a bit narrow compared to something that lets you record a sequence while playing for example. The Arturia Keystep is actually great for that as you can insert rests to limit the chord duration. Oh, and Steve is looking into doing that too, so maybe there is hope :-)
Using patterns as a chord sequence works great for doing algorithmic like sequencing where you are not too concerned with timing or specific notes. The pattern doesn't know anything about notes because its relative to the note pool based on the key and mode. Where in the chord sequencer you explicitly choose these things. Think of the pattern as an LFO as a custom waveform rather than a sequence and you will get the idea. The other downside with pattern controlling chord is its not possible to time chord type with chord changes like you can in the sequencer.