Omnisphere or Keyscape controll hold pedal

General discussion about Gig Performer
1

Hi all,

I’m new here and I’m really impressed of the software so far. I have a question…
I’m using Keyscape and Omnisphere and I have multiple pedals assigned in the rack space so the midi signal is no longer send via routing.
Now I want to target the Keyscape plugin hold pedal but since I cannot assign it to automation I don’t know how to send it.
Can anybody help me?

Greetings, Michael

2

I’m not deeply familiar with Keyscape. If the plugin hold pedal (I assume you mean sustain pedal, by the way) doesn’t support host automation then you should probably contact them and complain :slight_smile:

However, I’m not sure I understand the problem. You say you have multiple pedals assigned in the rackspace. So how exactly do you want to control the plugin hold pedal? Do you have another physical pedal that you’re trying to use to control the plugin hold? If so, does it generate a MIDI value and what is it?

3

I’m not sure if this is what you need but maybe the following will help.

I loaded Keyscape and I note that it uses CC 64 for sustain/hold. I’m assuming that the problem is that you don’t have the ability to generate a MIDI CC 64 event, presumably because you’re already using that with something else in the rackspace/automation.

So on one of my keyboards, I have a button that produces CC 21. I connected a MIDI In to a MIDI Filter that blocks everything except notes but it also maps CC 21 to CC 64 (see image)

Then, when I press that button, I get the HOLD. So if you have some other pedal that generates a different CC value you should be able to map it

Does that help?

4

First of all thx for the answer.

What you suggest if of course working. But i do not see why there is only the possibility to send automation to vst plugins. Because when i need midi cc for some reason I’m not able to do so. Never the less i got this currently working by sending it to the LoopBe1 midi out and inserting this into the vst.

To use the sustain pedal not only for sustain and use it more as a controller on the surface and group and use it as multiple actions makes a lot of things easier. Also if it comes over a different channel i have to remap it to chan. 1 for and example and then to filter which makes things also more complex.

Maybe I’m prob. not on the right way in configuring the host. But i think doing it this way gives me a lot of flexibility.

I have another question(s)

  1. When I would change my midi device i would have to relearn all midi commands on my rack unit space. Is it possible that the learn on all inputs. Or maybe define some alias for the devices?
  2. Can you offer a function that if we copy things like rack unit controls or filter that it copies all parameters if we hold a certain key like shift for an example. That would make things easier to duplicate without reconfigure or only changing one simple parameter.

Again my compliments on this great product looking forward for new features and will by the license next week when the trail expires. I think that is the product to go with for my new setup.

Greetings,

Michael

5

As I mentioned earlier, I was unclear exactly what you were trying to do. If you want to control multiple plugin parameters simultaneously from a single pedal, then associate each parameter with a Gig Performer widget, one of which you also associate with your pedal and then assign all the widgets to a single widget group (see attached image) then when you turn any widget in the group, they will all turn.

Your (1) and (2) are already on our list - we understand the need/convenience of this.