Pre-Purchase Follow-Up

Post Reply
earthling
Posts: 2
Joined: Tue Jan 16, 2018 10:12 pm

Pre-Purchase Follow-Up

Post by earthling »

Thank you Rob for your responses to my prior posting. I have few more questions as a follow-up if you don't mind.

1. From your previous response, I take it that I can run your software in stand-alone mode or as an audio insert when working with Cubase. Is this correct? If so, does Cubase see the Midi Expression device as a separate midi device when your controller software is in stand-alone mode?

2. I plan on getting a single Midi Expression device now and more in the future. Will a single instance of your software work with multiple 'individual' Midi Expression jacks at the same time as opposed to having one Midi Expression iO with multiple inputs?

3. Could you clarify whether the key command feature in your software allows for the use of number pad keys such as 1 - 9 as well as the * key on the pad? I ask because in Cubase the key command Number Pad * equals record. Could you also clarify whether the shift and alt keys are also available for use as key commands? And, am I correct in assuming that the single Midi Expression device with the micro USB connection supports key commands?

4. I have an M-Audio EX-P expression pedal. I plan to use it to control expression on certain plugins with your device. Will I also be able to use this same pedal to control volume rather than expression with your device and software?

Sorry for the lengthy number of additional questions but your answers count and will make a difference.

Thank you.
User avatar
Rob
Site Admin
Posts: 4780
Joined: Sat Aug 01, 2009 2:04 pm

Re: Pre-Purchase Follow-Up

Post by Rob »

earthling wrote:1. From your previous response, I take it that I can run your software in stand-alone mode or as an audio insert when working with Cubase. Is this correct? If so, does Cubase see the Midi Expression device as a separate midi device when your controller software is in stand-alone mode?
The control application does not communicate via MIDI so you don't have to worry about the control application preventing Cubase from accessing the device.
earthling wrote: 2. I plan on getting a single Midi Expression device now and more in the future. Will a single instance of your software work with multiple 'individual' Midi Expression jacks at the same time as opposed to having one Midi Expression iO with multiple inputs?
Yes. The control application can simultaneously configure up to four MIDI Expression devices at a time.
earthling wrote: 3. Could you clarify whether the key command feature in your software allows for the use of number pad keys such as 1 - 9 as well as the * key on the pad? I ask because in Cubase the key command Number Pad * equals record. Could you also clarify whether the shift and alt keys are also available for use as key commands? And, am I correct in assuming that the single Midi Expression device with the micro USB connection supports key commands?
Yes, it does allow you to map the key pads including the * key. Shit, alt, control, and Windows Key are all available as modifiers. All current and future generations of the hardware will support key commands.
earthling wrote:4. I have an M-Audio EX-P expression pedal. I plan to use it to control expression on certain plugins with your device. Will I also be able to use this same pedal to control volume rather than expression with your device and software?
The MIDI Expression just outputs MIDI. Inside of Cubase is where you decide what that MIDI controls. Some plugins have native support of the MIDI automation. For controlling Cubase itself, you can create a Generic Remote.

Regards,
Rob
Post Reply