Notifications
Clear all

Is there a way to access the parameter ports of VST plugins inside ComboBox?

9 Posts
2 Users
0 Likes
414 Views
 vVVv
(@vvvv)
Eminent Member
Joined: 2 years ago
Posts: 16
Topic starter  

I would really like to solve for some designs I have by running other plugins directly to the parameters of other plugins in ComboBox. In this specific instance I need to convert MIDI notes from my keyboard to CC (using piz midi notesToCC) then send that CC data to another plugin which has an automatable parameter for pitch inversion axis. I am aware that I could assign a MACRO knob to the pitch axis parameter and then go outside Unify to make an instrument track (in Nuendo) with a noteToCC instance which then sends the CC output to Unify input (and onto the MACRO knob), but I have a strong preference for doing this all inside ComboBox so I can house the end product as a module in there. Is there a way to do this?


   
Quote
(@getdunne)
Illustrious Member Admin
Joined: 5 years ago
Posts: 4410
 

@vvvv

You certainly can do this, by using the ComboBox-assigned names for the individual plug-ins within your parameter paths.

See this section of the ComboBox page in the manual for details.

 


   
ReplyQuote
 vVVv
(@vvvv)
Eminent Member
Joined: 2 years ago
Posts: 16
Topic starter  
Posted by: @getdunne

@vvvv

You certainly can do this, by using the ComboBox-assigned names for the individual plug-ins within your parameter paths.

See this section of the ComboBox page in the manual for details.

 

Thank you for the reply 🙂

I think you misunderstood me however-

With the solution you provide, I would still need to go outside Unify in order to add my plugin notesToCC converter, then direct that towards the CC of the assigned MACRO knob.

 

What I would like to do is access the automatable parameters of a plugin node inside ComboBox via another plugin node directed to it.

Can they be exposed for routing inside the ComboBox itself? 


   
ReplyQuote
(@getdunne)
Illustrious Member Admin
Joined: 5 years ago
Posts: 4410
 

@vvvv

Ah, I see. You want to use MIDI CC to control parameters of plug-ins inside ComboBox. That would require that ComboBox have its own macro knobs, to convert MIDI to automation, which it does not.

One option is to put your ComboBox instance inside an embedded Unify instance, and use that embedded Unify's macros to convert MIDI CC to parameter automation.

A second option is to use Kushview Element instead of ComboBox. Element is an excellent, free, souped-up version of ComboBox which does have its own macro facilities. At one time I was working with Element author Michael Fisher, to try to find a way for Element to share Unify's Known Plug-Ins list, but I don't think he ever did that, so you may have to scan your plug-ins a second time within Element. Or, if you don't mind mucking about with XML files, I can guide you through the process of copying Unify's list into Element.


   
ReplyQuote
 vVVv
(@vvvv)
Eminent Member
Joined: 2 years ago
Posts: 16
Topic starter  

@getdunne 

I was using Element to make module builds of multiple MIDI plugins, but it has been unstable in Nuendo.

Many times the options in the settings tab go dead, meaning that I can't save or load sessions.

Also, the "macro" knobs in Element often lose their connection to the host and become unusable. 

I was enjoying some features, such as MIDI in and out nodes which could be connected directly to drivers/ports, and also the power button located on the nodes for quick bypass.

 

"One option is to put your ComboBox instance inside an embedded Unify instance, and use that embedded Unify's macros to convert MIDI CC to parameter automation."

 

Yes, I thought of this but I am wary of going that route as I'm doing all MIDI plugins. A nested/embedded ComboBox inside a ComboBox will get the MIDI all the way back out to the front/top Unify instance, but a full Unify instance nested/embedded inside a ComboBox cannot (having no MIDI out of its own).

I do have BlueCat Connector but this solution becomes convoluted (routing MIDI from nested/embedded Unifys to the front/top Unify which is then using *another* BC Connector to get out the the host) and I worry about its stability. If it were one or two instances of this I wouldn't mind, but I'm looking at building a very large template out of hundreds of modules, many of which will have multiple layers of nesting (3 or 4?). 

 

If I use a Blue Cat Connecter in an embedded module that I need to copy/paste (say 16 times) each instance will instantiate with the same settings meaning all of the BCC's will default to the same port ID. To work properly they all need separate connector IDs. It would take 3 instances of BCC *minimum* to do one nested/embedded module (one going out of the embedded Unify, 1 in and 1 out for the top level Unify instance).

Doing copy/paste of such modules would quickly turn into a quagmire it seems. 


   
ReplyQuote
(@getdunne)
Illustrious Member Admin
Joined: 5 years ago
Posts: 4410
 

@vvvv

I could possibly make suggestions if I knew more about what effects you're trying to achieve.


   
ReplyQuote
 vVVv
(@vvvv)
Eminent Member
Joined: 2 years ago
Posts: 16
Topic starter  

@getdunne 

Hmmmm... that is not easy to describe quickly.

I am working on a system here for incorporating a lot of MIDI "modules" into a large orchestral template. The modules are to handle many different tasks with MIDI for DAW music creation. Harmonic, melodic, timbre and rhythm tools along with orchestration techniques. 

The screen shot below shows 11 stages (in order) for the overall design.

Each stage contains "modules" of some sort to process MIDI. In Unify (ComboBox) or Element, ideally, each "module" would be packed into a node and its relevant controls brought to the front on Macro knobs.

The "modules" would contain many types of plugins, from chord players to sequencers chained with MIDI utilities of different sorts- scale filters, note filters, channel tools, LFO and envelopes. 

A simple example would be a diatonic melodic inversion module:

MIDI in -> note inversion (axis at C3) -> filter scale (set to C major, round up) -> MIDI out

This would take a C major scale, played up from C3 transform it into a C major scale, going down from C3.


   
ReplyQuote
 vVVv
(@vvvv)
Eminent Member
Joined: 2 years ago
Posts: 16
Topic starter  

Adding a screen shot of the transformed C major scale:


   
ReplyQuote
(@getdunne)
Illustrious Member Admin
Joined: 5 years ago
Posts: 4410
 

@vvvv

Thanks for the details. I think I understand now, and I'm pretty sure this couldn't really be done without adding macros or some other kind of MIDI-to-automation functionality to ComboBox. I'll put this on the to-do list, but honestly, it's a huge chunk of work, and won't happen soon.

You'd probably get quicker results by reporting your difficulties with Element to Michael. He can probably fix the bugs in his implementation, which already exists (but is buggy), than I can create a new implementation in Unify.


   
ReplyQuote
Share: