Notifications
Clear all

vst3 cc out and reason rack plugin


elcotwitch
(@elcotwitch)
Active Member
Joined: 7 months ago
Posts: 10
Topic starter  

Hi all. When using a plugin in a midi layer of unify, is cc data out working properly if that plugin is vst3?

I've been using the vst2 version melda mccgnerator  in a midi layer to generate lfo's which can be used to modulate parameters of synths in instrument layers using "learn midi cc"  but i've never been able to successfully do the same with the vst3 version of mccgenerator.

now i'd like to use the reason rack plugin but sadly that only comes in vst3 format, so far i am unable to use any of it's excellent lfo's and envelopes  as cc messages.

anyone able to shed any light here? i know that ableton live and studio one have both had issues with utilizing midi cc data from the reason rack plugin and that has officially been put down to a problem specifically with vst3.  could something similar be happening with unify and vst3?

thanks.


Quote
getdunne
(@getdunne)
Member Admin
Joined: 1 year ago
Posts: 2025
 

@elcotwitch

This was fixed in Unify v1.1.7. Please check your version number.


ReplyQuote
elcotwitch
(@elcotwitch)
Active Member
Joined: 7 months ago
Posts: 10
Topic starter  

That's excellent, thanks Shane.   RRP is now happily sending out CC data.  I surprised myself by being a version or two behind hah.

Is there any plan for Unify's own macro knobs to be controlled by CC message data like this?

Thanks.

 


ReplyQuote
getdunne
(@getdunne)
Member Admin
Joined: 1 year ago
Posts: 2025
 
Posted by: @elcotwitch

Is there any plan for Unify's own macro knobs to be controlled by CC message data like this?

You could do this using an embedded Unify instance, with your instance of RRP before it. Unify v1.1.10, which will be out later today, makes this practical because it allows saving Macro CC assignments for embedded Unify instances in patches.


Nico Fyve liked
ReplyQuote
karlfranz
(@karlfranz)
Trusted Member
Joined: 10 months ago
Posts: 73
 

I don't know if this is relevant to the OP, but in the release notes for the newest Live 10 Beta (version 10.1.25b1) it states:

 

• Live now receives and routes MIDI CC, Pitch Bend, and Aftertouch events sent from a VST3 plug-in device to a MIDI-out bus. Note: this is supported in plug-ins built with VST SDK 3.6.12 or higher.


ReplyQuote
elcotwitch
(@elcotwitch)
Active Member
Joined: 7 months ago
Posts: 10
Topic starter  

@getdunne Awesome! worked like a charm, thanks.


ReplyQuote
elcotwitch
(@elcotwitch)
Active Member
Joined: 7 months ago
Posts: 10
Topic starter  
Posted by: @karlfranz

I don't know if this is relevant to the OP, but in the release notes for the newest Live 10 Beta (version 10.1.25b1) it states:

 

• Live now receives and routes MIDI CC, Pitch Bend, and Aftertouch events sent from a VST3 plug-in device to a MIDI-out bus. Note: this is supported in plug-ins built with VST SDK 3.6.12 or higher.

Cool, that's good to know although something I probably won't use much as I tend to use M4L Lfo's in Live.

Specifically my goal with Unify is to have completely self contained patches with modulators running internally controlling Unify's macro knobs.

Now with 1.1.1.0 it does this very nicely.


ReplyQuote
elcotwitch
(@elcotwitch)
Active Member
Joined: 7 months ago
Posts: 10
Topic starter  
Posted by: @getdunne
Posted by: @elcotwitch

Is there any plan for Unify's own macro knobs to be controlled by CC message data like this?

You could do this using an embedded Unify instance, with your instance of RRP before it. Unify v1.1.10, which will be out later today, makes this practical because it allows saving Macro CC assignments for embedded Unify instances in patches.

Ah I seem to run into a potential bug here.

Embedding a Unify instance works fine until the project is saved (either in Cubase or Live) and when i load the project later the embedded Unify layer is still there but it will not receive any midi information at all.

This is even with the simplest one layer containing just a Unify containing the initial Sine Wave.


ReplyQuote
getdunne
(@getdunne)
Member Admin
Joined: 1 year ago
Posts: 2025
 
Posted by: @elcotwitch

Embedding a Unify instance works fine until the project is saved (either in Cubase or Live) and when i load the project later the embedded Unify layer is still there but it will not receive any midi information at all.

Is this with Unify v1.1.10?


ReplyQuote
elcotwitch
(@elcotwitch)
Active Member
Joined: 7 months ago
Posts: 10
Topic starter  
Posted by: @getdunne
Posted by: @elcotwitch

Embedding a Unify instance works fine until the project is saved (either in Cubase or Live) and when i load the project later the embedded Unify layer is still there but it will not receive any midi information at all.

Is this with Unify v1.1.10?

Yep 1.1.1.0

I never tried that with older versions so cant compare.


ReplyQuote
getdunne
(@getdunne)
Member Admin
Joined: 1 year ago
Posts: 2025
 

@elcotwitch

Did you create your embedded Unify instance using the "built-in" Unify plug-in, or the VST/VST3? The built-in is best.

When I have time to get set up I'll test saving in Cubase. I have tested saving in Unify, and that works.

In Cubase/Live, are you using the VST or the VST3 version of the Unify plug-in? If using the VST3, please try the VST (aka VST2).


ReplyQuote
elcotwitch
(@elcotwitch)
Active Member
Joined: 7 months ago
Posts: 10
Topic starter  
Posted by: @getdunne

@elcotwitch

Did you create your embedded Unify instance using the "built-in" Unify plug-in, or the VST/VST3? The built-in is best.

When I have time to get set up I'll test saving in Cubase. I have tested saving in Unify, and that works.

In Cubase/Live, are you using the VST or the VST3 version of the Unify plug-in? If using the VST3, please try the VST (aka VST2).

It was with Unify VST3, and embedding the Unify VST3.

Now I've got Unify VST3 and embedded the built-in Unify and after one test, my instance has recalled correctly.  Cheers!


ReplyQuote
Share: