Call For Feedback : KeySwitching

[jim]

I had some ideas for a dedicated module for KeySwitching, and wanted to ask anyone who has used this technique, either directly with a synth or as an ad-hoc controller, for information on how they used it, and how they might put such a feature to use in Numerology.

The rough design I was thinking about was a module with a keyboard, where you could define a key range, then generate both CV signals and ParamMod events from them. The module would have its own MIDI input selection to make it easier to setup within a stack.

Cheers,
Jim

[lut lei]

Excuse my ignorance, but keyswitching is not a term I'm familiar with. So I googled it:

I found this (http://www.youtube.com/watch?v=nnxFQfxuta0) video, demonstrating the keyswitching functionality in Structure, the Pro Tools RTAS plug in.

Guess this also relates to Artillery (http://www.sugar-bytes.de/content/products/Artillery2/index.php?lang=en) by Sugar Bytes, where you use the keys to trigger different effects. I actually thought of buying this, as it seemed like a good performance tool, but eventually realised that it could be done with Numerology, - and some effort.

Am I on the wrong track?

[jim]

A very handy video.... Yes, that is exactly the basic technique : using MIDI notes to switch between different layers in a sampler. You can extend the technique if you consider range of notes to be a set of control values, which you can map either to something like sample layers, or effect mutes, octave transpositions, etc. I was reading the review of Cubase 5 in Sound On Sound and how they have implemented a variant of key-switching and wondered what would be the right approach for Numerology.

Cheers,
Jim

[lut lei]

Haven't read the latest issue of Sound on Sound yet, but have you looked at the demo video of Artillery? I think that one's cleverly done.

Each zone has a "key amount"-value and a "mod amount"-value.

In numerology, maybe each zone could have an CV-input/output, and a optional ParamMod output. Then we only need a Key Amount value + Mod amount value per zone. Choosing the zones could be done by clicking and dragging in the modules GUI.

Just some thoughts, though.

[jue]

Hello,

normaly keyswitching is used in Giga Sampler, Kontakt or other Samplersoftware like in Structure to switch live between differend samplelayers.
Since I got Numerology I had stacks with a IntervalSeq more for just switching the layers of the samplers.
Your ideas for a KeySwitch module should go a little further.
Do you remember our discussion about a scanner module some time ago?
There we were talking about switching with gates for triggering sequences also.
So here my thoughts about this module:
A keyboard with 2 octaves were each note has a Gateout that is on as long as the note lasts.
The CVoutput should be this: the middle C of the keybord sends out 0 at its CVoutput, the low C sends -12 and the high C sends 12.
A MIDI input for external triggering and the possibility to set a note to on with the first mouse click and off with the second.
A possibility for setting the range, were the 2 octaves are.
Nothing more, everything else is ready in Numerology.
With this it would be possible to make your sequences playable by setting up sequences that are runninging as long as you are holding the note on the keyboard and the CVouts transpose your sequence to the key you are playing.
What a stack, the Keyswitch module and 25 IntervalSeqs, two FaderBoxes and 13 ParamMods to set up the IntervalSeqs, one GateSeq, one VelocitySeq and 25 NoteGens before the AUsynth.
You see my project is ready the only question is: Were is the Keyswitch module?
I know crazy people from the european outback but this will work nearly as my Zyklus Hardware Seq.
With this module it would be possible to start and stop complete stacks, up to 25, from your MIDI keyboard live.
best
jue

[dinraum]

one interesting variation of the key-switching idea can also be found in some great omforce plugins. they call this feature "Melohman" and it is a kind of sub preset morphing where a lot of parameters can change. but they also have some random/evolve modes implemented.

[kodama]

I also like the idea of expression through cycling through a set of cc values, moving a mod sequence on each key press.

[ZenPunkHippy]

Key switching sounds like a great plan :)

One obvious use of key switching is to select patterns in a drum machine. Would it be possible to implement key switching for stack presets?
Allowing the user to define the range of keys used (e.g. C-2 -> B-1), and also assign stack presets to specific keys.

This could be used to record preset changes on the timeline, for real-time arrangement, and would simulate the drum machine feature nicely.

Expanding on this, the ability to set a time parameter on a preset that controls how long it takes to evolve (or morph) the parameters from the previous preset would create some very cool possibilities. Clearly not all parameters are able to morph like this, but certain modules like the fader boxes are made for it.

Peace,
Andy.

[jim]

One obvious use of key switching is to select patterns in a drum machine. Would it be possible to implement key switching for stack presets?
Allowing the user to define the range of keys used (e.g. C-2 -> B-1), and also assign stack presets to specific keys.


Actually, you can do that already -- double-click on a preset name and assign a MIDI note to it. -- Much faster than what you'd have to do if using a KeySwitch module... I think you also need to assign the keyboard as the "MIDI Remote" input on the StackIn module.


This could be used to record preset changes on the timeline, for real-time arrangement, and would simulate the drum machine feature nicely.


Yes, that would be nice, on my list...

Expanding on this, the ability to set a time parameter on a preset that controls how long it takes to evolve (or morph) the parameters from the previous preset would create some very cool possibilities. Clearly not all parameters are able to morph like this, but certain modules like the fader boxes are made for it.


Already in my notes somewhere for the pro version, but I haven't set a priority for it yet. It is tricky, as it complicates the implementation of each module...

Cheers,
Jim