Automatable Params to MIDI CC without external MIDI loopback

Official support for: bluecataudio.com
Post Reply New Topic
RELATED
PRODUCTS

Post

I'm looking for a way to remap Automatable VST Parameters in Cubase/Nuendo to MIDI CC's for effects that offer such parameters but don't implement CC control.

Currently the only way to do this is by remapping VST parameters to Quick Controls and then controlling them by sending CCs from other tracks to an external MIDI device and back into the DAW to control the Quick Control.

Not only is this somewhat cumbersome to set up, but it also makes it impossible to do offline renders of a project.

Can BC's Remote Control create such a link without resorting to external loopback and can it work with offline rendering?

I really don't need any of Remote Control's other functionality than this, but it's important for me to find a solution to this problem.

Thanks!

Post

There really must be a better way of doing this than going external can you wrap the plug-ins in a chainer - they range from chainer xt to kore and mulab - these then allow midi cc for the fx without any loop back or anything like that

But I am pretty sure if you map them to quick controls you can then just record the parameters changes - no loopback or midi needed
I believe every thread should devolve into character attacks and witch-burning. It really helps the discussion.

Post

ericj23 wrote:There really must be a better way of doing this than going external can you wrap the plug-ins in a chainer - they range from chainer xt to kore and mulab - these then allow midi cc for the fx without any loop back or anything like that
You know, that's a great idea! Thanks! I tried it with Bidule and it worked. Sometimes you get so caught up trying to do things in a straightforward logical way... ;)

The problem with Quick Control and the Generic Remote is that they're designed to control parameters from outside the DAW. I really don't understand why Steinberg doesn't create a "MIDI CC to VST Parameter Mapper" that can receive from other MIDI devices within the project. It seems like such an obvious thing to implement... :shrug:

Post

Breeze wrote:
ericj23 wrote:There really must be a better way of doing this than going external can you wrap the plug-ins in a chainer - they range from chainer xt to kore and mulab - these then allow midi cc for the fx without any loop back or anything like that
You know, that's a great idea! Thanks! I tried it with Bidule and it worked. Sometimes you get so caught up trying to do things in a straightforward logical way... ;)

The problem with Quick Control and the Generic Remote is that they're designed to control parameters from outside the DAW. I really don't understand why Steinberg doesn't create a "MIDI CC to VST Parameter Mapper" that can receive from other MIDI devices within the project. It seems like such an obvious thing to implement... :shrug:
I would love that - you could then start mapping everything all over - like a giant modular

You can do this sort of thing in Live using Max, but is buggy as biscuits, in my experience, and has well documented PDC problems
I believe every thread should devolve into character attacks and witch-burning. It really helps the discussion.

Post

Thank you for your interest in our plug-in. It should allow you to transform MIDI CC messages into automation lanes that you can reassign, but I don't think Cubase will let you do the mapping in real time to plug-ins parameters.

Post

Blue Cat Audio wrote:...but I don't think Cubase will let you do the mapping in real time to plug-ins parameters.
Yep, Cubendo is the problem. Apparently Steinberg removed this functionality a while ago... probably because it wasn't well managed and created problems. When you think about it, the background routing can get extremely complicated if you're doing this across many tracks and plugins; it's the kind of thing you either implement properly, or you don't do at all. ;)

Post Reply

Return to “Blue Cat Audio”