In this particular case I am speaking of the Octave up/down buttons on the Novation Launchkey 25 MK3 MIDI Keyboard Controller. If for example I use an octave transpose Scriptlet such as “Octav_V1_0_6”, this will allow me to transpose the virtual keyboard up or down 3 octaves BUT will not transpose my performance up or down the keyboard. It will therefore still be in the same range of the keyboard, transposed. The Octave up/down buttons allow you to play in a different range of the keyboard. SO, of course I can simply press the Octave up/down buttons on the Launchkey 25, but what I was hoping to do is to automate this with a key stroke connected to a widget, or some other method that makes the process automated (rather than an extra action).
Hi, if Gig Performer is the only sound generator connected to your Novation then there might definitely be several ways to do this, like putting a a midi in block before the ones that do the splitting and transposing.
Could you please explain or post a screenshot to better understand your midi flow within the rackspace.
Does this help?
If I understand the question, you’re looking for a way that you could press either a widget or an octave button on the keyboard and achieve the same thing?
I don’t believe you can do that with the Launchkey (or other Novation) keyboards. I think shifting the keyboard range is something you’ll have to control either on the keyboard (which will shift the notes in the midi stream) or in GP (which will shift them before sending them to plugins).
I do the latter myself. My keyboard will always be un-shifted and if I want to move it up or down an octave I do it within the Rackspace or Variation.
In a typical setup for me I have the Novation keyboard split within GP and often one side transposed by an octave. In many rackspaces I’ll have the left side of the keyboard set for a widget-configurable bass sound, some of which will be transposed, some not.
My rather simple and crude approach is that I often have four different plugins wired to that left-hand zone, with midi filters and the appropriate octave transpose in front of them. I control which one(s) are actually playing by toggling widgets that allow note-on events through.
There are different ways to approach it, but with that keyboard I think your best solution will be to handle all the transposing in GP.
Thanks so much for your responses. I will now work through your suggestions. The MIDI Transposer does not work as it simply transposes the virtual instrument up or down but NOT the region on the keyboard.
What do you mean by transposing the “region”? Isn’t the goal to have the instruments transposed?
Sorry for the confusion. By transposing in the ‘region’ (I could be using the wrong term) I mean in a different area of the actual physical keyboard. But I have found a solution. Thanks for all your suggestions. Your suggestions sparked an idea that has worked. I have now placed everything in the same ‘keyboard region’ and by using the MIDI filter GP addon I have created buttons that will either activate or deactivate note on commands. That seems to be the solution rather than me trying to work out how to get GP to force what I am playing to be transferred to another region of the keyboard (which may be impossible). But thanks so much. What you all said made me realize that I could use the MIDI filter commands to turn on and then off one of the two virtual synths that I am using in the same region of the keyboard. SO, what I was doing prior to this is placing each layer in a different region of the keyboard, which is essentially splitting the keyboard. That works fine when you are using a 5 octave keyboard. But in my case the Novation Launch Key that I am using is only 2 octaves, and so so access the second sound I have to use the octave up/down bottom. Which is fine in a way, but my part is so complicated (and not from a musical point of view) that I am trying to have to do the least possible in the performance. In other words, if I forget to press the octave up down button I end up with either nothing or the wrong sound. It’s one single concert with an orchestra and so not a gig where I can get it right the next time around. So thanks so much for your suggestions. I am actually so happy that I got these great responses. What a community. Super great.
I’m glad you found a solution within Gig Performer that fits even better than your original idea.
Still there might be some use cases for it, like when your gig file has been set up for 88 keys but you temporarily only have a shorter keyboard on vacation, in the office, on the toilet… - so this would be the answer to your initial question:
In this case you would use only one MIDI input whose transpose is controlled by a widget. You would then do the splitting with “fake” MIDI In blocks (like the MIDI In OSC) that are only used for key zones and filtering.
Wow. Great idea Florian. Thanks so much.