TwoToneshuzz
01-19-2012, 10:23 PM
I've found a new use for the Drumsequencer.
I use global triggers to trigger each mono notes main trigger.
A three tiered system.
Global trigger output to Main Trigger GateSequencers trigger input. Main Trigger Gate's output to MonoNote or other sequencers trigger Input.
This gets me control over the whole arrangement th Global trigger's and control over the individual sequence how long it plays and if there is any short snippets from a longer sequence or if a sequence plays three times and stops etc.
What I've experienced though is this setup takes a massive amount of space in an open stack..Also I use Gate triggers outputs into the CV bus, this uses up all my 16 CV busses pretty quickly. I use the first 4 CV busses for harmony control. That leaves me with 12 busses for triggers..
So I have to use Midi to CV modules to get more inter stack communications going than just these 16 busses..
Now this is where the Drumsequencer comes in.
It has up to eight midi outputs, one per track..
I now have got it setup so that these eight outputs are routed out a Dedicated Midi trigger control bus. With just 3 Drumsequencers I can have access to up to 24 trigger signals..
In my present project I use 3 Drumsequencers set to 6 tracks each giving access to 18 triggers.
This gives a very conprehensive overview of the whole project. Which group of sequences out of a total of 18 are playing can quickly be setup and verified.
I just setup each Drumsequencer tracks midi channels to seq one 1-6, sequence two 7-12 and sequence three 13-18 route it out two midi busses,midi bus 5 covers 1-12 and midi Bus 6 covers 13-18. On the receiving three main gate trigger stacks I have connected the midi inputs to 6 Midi to CV modules per track, These modules Gate outputs go into the Main Trigger gates trigger inputs. The main trigger gates play mode is set to "CV trigger Play" mode, Loop is set to off.
I need my main gates to just turn on and be on for the whole length of the section of playing time now because I'm also using these gates to generate auto on and off of my software plugin instruments and effects. Earlier I'd set it up so that these Main Trigger Gates had alot of breaks to create the 1,2 or 3 bar spaces in the midisequencers outputs. So I use the Super triggers to control the general arrangement. The main triggers control how long the sequencers play on an individual basis.
The Drumsequencers events list only needs to generate a one step inpuls to start the main triggers to play. I use a 32 step sequence length with a Clock division set to four whole notes to give me 128 bars of playing time. The project runs at a slow tempo of around 35 to 50 Bpm. so 128 bars gives me more than two minutes of time overview and 18 sequencers by looking at just three 32 step Drumsequencers in their dedicated trigger stack..
But wait there is more. to control how long each sequence plays on an individual basis from the Super trigger stack. I've setup 3 Fader boxes going into 18 paramod slots, with module destination the 18 individual Main GateSequencers , parameter "Start Step". Now I can choose exactly how long the individual sequence plays by moving my faders, I've set the range to match my Main Trigger Gates 32 steps and the Fader mode is set to Quantize.
There are still more elements to make up the whole set up. For access to more than 128 bars I will need something that will behave as if I have a Super Super Trigger gate control..
For this Super Super tirgger gate control I use a Super Super Trigger gate stack, in combination with presets to gain access to hours of playing time if I should so wish..
The Super Super trgger gate control stack is basically set up using a:
Trigger gate set to send a trigger every 32 x 4 whole note period
One Velocity Sequencer set to output range 1-16 this is the preset number chooser.
a program change module for calling up the presets on the Super trigger stack.
A number of presets on the Super Trigger setup, set to remote on "Program Change" I set the recieve dhannel to 16 and the preset numbers within the range of 1-16 gives access up to 16x 128=2048 Bars in the arrangement!
Paramod module with inputs from the velocity out of the preset chooser with a destination module ProgramChange module, Parameter/ Program Num, and and input from the Gate out of the trigger gate oges into slot two, destination "Send now". completes the list of tools.
The trigger from this Super Super trigger stacks Gatesequencer also goes into the Velocity sequencers trigger input. The Velocity sequencer is set to "CV trigger step" mode. This advances the Velocity sequencer one step every 128 bars.. Unfortunately there is some slew in this CV trigger step modus, so it often skips more than one step when recieving a impuls from the gate sequencer. I mitigated this problem by doubling each program change number step at the Velocity sequencer . So I have a 32 Step sequencer where program number 1 gets up to 4 steps. This will give me one preset advance every 128 bars! I'd do this at the preset playlist mode but it only give access to 32 bars not enough, no no not at all.
Each trigger ideally will advance the program number one step and press the send now button on the program change module..
Setting upto 16 presets this way I have access to 16 x 128 bars/3 minutes 48 minutes of variable output. I could double the range of the Velocity sequencers output for access to 96 minutes very easily..
Super Super trigger stack calls up the program changes on the Super Trigger stack, The Super Trigger stack starts 18 gate sequencers spread over three Main Gate trigger stacks, these work horses in turn starts the transports on 18 midi note generating sequencers spread over 6 stacks. Is that enough control? Of course not!!!!
What about the spaces within the phrase?. The above setup only takes care of the global playback function. Spaces within the phrase need more gates!!! The global mute stack, and the mute stack.
I detailed how I use the mute stack in Gates Gates and more Gates under tricks and tips..
But now I've refined this setup as well. Instead of dumbly just connecting a Gate sequencer into a single paramod slot with paramod module destination/MonoNote sequencer parameter/Main Mute, I now use two paramod slots per MonoNote that I want to mute. Slot one uses the output from the Gate Sequencers Sequence Step output to align the steps of this sequencer to the recieving mono note. this is setup by choosing this paramod's modules very own module as the destination and the parameter is set to "parameter index" set to "2". The second slot on the module is routed to the destination MonoNote, and parameter MuteStep. Now instead of Global mutes I mute each step individually in the sequence. This solves a vexing problem I've been having when using Sequencer "main mute" to achieve the many short rests which too often was giving stuck me notes..
Not finished yet! I detailed How I've used CV switches to achieve a varied project wide "Global Rest" under Tips and Tricks "using CV switches in new ways!" Often getting things to stop all at the same time to create space for Great silences, or Reverb Tails is just whats needed. For this I still use the Sequencers "Main Mute" as the parameter in the paramods.
So each Sequence is influenced by
Super Super Trigger gate= whole arrangement length with variable content.
Super Trigger= When each sequence is playing.
Main Trigger= on/off instruments effects and individual sequencers
Mute Stack= rests/spaces within each individual phrase.
Global Mute stack= rests/spaces in the whole arrangement.
The whole is constructed from a desire to create space withing an individual line, as well as control the Arrangement on a Global level.
Regards
Wade
I use global triggers to trigger each mono notes main trigger.
A three tiered system.
Global trigger output to Main Trigger GateSequencers trigger input. Main Trigger Gate's output to MonoNote or other sequencers trigger Input.
This gets me control over the whole arrangement th Global trigger's and control over the individual sequence how long it plays and if there is any short snippets from a longer sequence or if a sequence plays three times and stops etc.
What I've experienced though is this setup takes a massive amount of space in an open stack..Also I use Gate triggers outputs into the CV bus, this uses up all my 16 CV busses pretty quickly. I use the first 4 CV busses for harmony control. That leaves me with 12 busses for triggers..
So I have to use Midi to CV modules to get more inter stack communications going than just these 16 busses..
Now this is where the Drumsequencer comes in.
It has up to eight midi outputs, one per track..
I now have got it setup so that these eight outputs are routed out a Dedicated Midi trigger control bus. With just 3 Drumsequencers I can have access to up to 24 trigger signals..
In my present project I use 3 Drumsequencers set to 6 tracks each giving access to 18 triggers.
This gives a very conprehensive overview of the whole project. Which group of sequences out of a total of 18 are playing can quickly be setup and verified.
I just setup each Drumsequencer tracks midi channels to seq one 1-6, sequence two 7-12 and sequence three 13-18 route it out two midi busses,midi bus 5 covers 1-12 and midi Bus 6 covers 13-18. On the receiving three main gate trigger stacks I have connected the midi inputs to 6 Midi to CV modules per track, These modules Gate outputs go into the Main Trigger gates trigger inputs. The main trigger gates play mode is set to "CV trigger Play" mode, Loop is set to off.
I need my main gates to just turn on and be on for the whole length of the section of playing time now because I'm also using these gates to generate auto on and off of my software plugin instruments and effects. Earlier I'd set it up so that these Main Trigger Gates had alot of breaks to create the 1,2 or 3 bar spaces in the midisequencers outputs. So I use the Super triggers to control the general arrangement. The main triggers control how long the sequencers play on an individual basis.
The Drumsequencers events list only needs to generate a one step inpuls to start the main triggers to play. I use a 32 step sequence length with a Clock division set to four whole notes to give me 128 bars of playing time. The project runs at a slow tempo of around 35 to 50 Bpm. so 128 bars gives me more than two minutes of time overview and 18 sequencers by looking at just three 32 step Drumsequencers in their dedicated trigger stack..
But wait there is more. to control how long each sequence plays on an individual basis from the Super trigger stack. I've setup 3 Fader boxes going into 18 paramod slots, with module destination the 18 individual Main GateSequencers , parameter "Start Step". Now I can choose exactly how long the individual sequence plays by moving my faders, I've set the range to match my Main Trigger Gates 32 steps and the Fader mode is set to Quantize.
There are still more elements to make up the whole set up. For access to more than 128 bars I will need something that will behave as if I have a Super Super Trigger gate control..
For this Super Super tirgger gate control I use a Super Super Trigger gate stack, in combination with presets to gain access to hours of playing time if I should so wish..
The Super Super trgger gate control stack is basically set up using a:
Trigger gate set to send a trigger every 32 x 4 whole note period
One Velocity Sequencer set to output range 1-16 this is the preset number chooser.
a program change module for calling up the presets on the Super trigger stack.
A number of presets on the Super Trigger setup, set to remote on "Program Change" I set the recieve dhannel to 16 and the preset numbers within the range of 1-16 gives access up to 16x 128=2048 Bars in the arrangement!
Paramod module with inputs from the velocity out of the preset chooser with a destination module ProgramChange module, Parameter/ Program Num, and and input from the Gate out of the trigger gate oges into slot two, destination "Send now". completes the list of tools.
The trigger from this Super Super trigger stacks Gatesequencer also goes into the Velocity sequencers trigger input. The Velocity sequencer is set to "CV trigger step" mode. This advances the Velocity sequencer one step every 128 bars.. Unfortunately there is some slew in this CV trigger step modus, so it often skips more than one step when recieving a impuls from the gate sequencer. I mitigated this problem by doubling each program change number step at the Velocity sequencer . So I have a 32 Step sequencer where program number 1 gets up to 4 steps. This will give me one preset advance every 128 bars! I'd do this at the preset playlist mode but it only give access to 32 bars not enough, no no not at all.
Each trigger ideally will advance the program number one step and press the send now button on the program change module..
Setting upto 16 presets this way I have access to 16 x 128 bars/3 minutes 48 minutes of variable output. I could double the range of the Velocity sequencers output for access to 96 minutes very easily..
Super Super trigger stack calls up the program changes on the Super Trigger stack, The Super Trigger stack starts 18 gate sequencers spread over three Main Gate trigger stacks, these work horses in turn starts the transports on 18 midi note generating sequencers spread over 6 stacks. Is that enough control? Of course not!!!!
What about the spaces within the phrase?. The above setup only takes care of the global playback function. Spaces within the phrase need more gates!!! The global mute stack, and the mute stack.
I detailed how I use the mute stack in Gates Gates and more Gates under tricks and tips..
But now I've refined this setup as well. Instead of dumbly just connecting a Gate sequencer into a single paramod slot with paramod module destination/MonoNote sequencer parameter/Main Mute, I now use two paramod slots per MonoNote that I want to mute. Slot one uses the output from the Gate Sequencers Sequence Step output to align the steps of this sequencer to the recieving mono note. this is setup by choosing this paramod's modules very own module as the destination and the parameter is set to "parameter index" set to "2". The second slot on the module is routed to the destination MonoNote, and parameter MuteStep. Now instead of Global mutes I mute each step individually in the sequence. This solves a vexing problem I've been having when using Sequencer "main mute" to achieve the many short rests which too often was giving stuck me notes..
Not finished yet! I detailed How I've used CV switches to achieve a varied project wide "Global Rest" under Tips and Tricks "using CV switches in new ways!" Often getting things to stop all at the same time to create space for Great silences, or Reverb Tails is just whats needed. For this I still use the Sequencers "Main Mute" as the parameter in the paramods.
So each Sequence is influenced by
Super Super Trigger gate= whole arrangement length with variable content.
Super Trigger= When each sequence is playing.
Main Trigger= on/off instruments effects and individual sequencers
Mute Stack= rests/spaces within each individual phrase.
Global Mute stack= rests/spaces in the whole arrangement.
The whole is constructed from a desire to create space withing an individual line, as well as control the Arrangement on a Global level.
Regards
Wade