Blue Cat Audio

erezyaary · Post by **erezyaary** » Sun Jun 07, 2020 5:39 pm

Hi,

I'm taking first steps writing a MIDI Control Change filter script however am encountering an issue where the plugin does not see to receive or process Control Change events.

To test I've loaded the Midi Log script and there are no captured Control Change events.

Is there anything I'm missing?

Thanks

Blue Cat Audio · Post by **Blue Cat Audio** » Mon Jun 08, 2020 5:29 am

If using a DAW, have you created a MIDI track to route the events to the plug-in? Plug'n Script receives the MIDI events from the application it is loaded in, not directly from the MIDI interface (except for the standalone app)

erezyaary · Post by **erezyaary** » Mon Jun 08, 2020 8:04 am

Yes, I have loaded the plugin into Bitwig and placed it into a MIDI track. I'm monitoring incoming and outgoing (too hardware synth) midi events using a midi editor.

As I'm using the Log script, I am noticing only Note On, Note Off and Aftertouch events are registered as part of the plugin, however the midi monitor displays also control change and pitch wheel, both are not registered within the Plug'n Script plugin MIDI events list.

Blue Cat Audio · Post by **Blue Cat Audio** » Mon Jun 08, 2020 11:23 am

Are you maybe using the VST3 version of the plug-in? Steinberg has tried to drop MIDI support with VST3, and while we have implemented several common "hacks" that restore these features in most hosts, I am not 100% sure Bitwig implement them properly, so you may want to use the VST version instead.

Tj Shredder · Post by **Tj Shredder** » Sat Jul 04, 2020 6:38 am

I thought the latest VST3 specs added Midi again? Can we mail bomb Steinberg to include full Midi support in VST3? Especially now, as Midi 2.0 is official?
Isn’t Yamaha a core member of the Midi association?
I mean no Midi? Cubase started as one of the first Midi sequencers...

On the other hand, Bitwig is tricky. If you set an instrument in MPE mode, expressions do not arrive as Midi. Depending on the controller script.

I just got plug’n script and my first project would also be a Midi/Expression monitor. Is there a way to monitor VST3 expressions?

ilyaorlov · Post by **ilyaorlov** » Fri Jul 10, 2020 9:14 am

I'd be glad to help, but yet don't have much experience with that.

Blue Cat Audio · Post by **Blue Cat Audio** » Thu Jul 16, 2020 8:47 pm

Tj Shredder wrote: Sat Jul 04, 2020 6:38 am I thought the latest VST3 specs added Midi again? Can we mail bomb Steinberg to include full Midi support in VST3? Especially now, as Midi 2.0 is official?
Isn’t Yamaha a core member of the Midi association?
I mean no Midi? Cubase started as one of the first Midi sequencers...

They have indeed aded back a few missing pieces but it's still a hack...

On the other hand, Bitwig is tricky. If you set an instrument in MPE mode, expressions do not arrive as Midi. Depending on the controller script.

I just got plug’n script and my first project would also be a Midi/Expression monitor. Is there a way to monitor VST3 expressions?

Since VST3 expression is different from MPE (which is standard MIDI), I don't think it can be monitored inside Plug'n Script.

Tj Shredder · Post by **Tj Shredder** » Thu Jul 16, 2020 9:58 pm

But any VST3 should be able to receive expressions. That means it should be able to display them. Otherwise expressions would be useless and as far as I know they are not useless as the Steinberg plugins respond to them...
Of course that would not work in a VST2...

Blue Cat Audio · Post by **Blue Cat Audio** » Wed Jul 22, 2020 2:38 pm

Indeed, it would have to be an extension that is specific to VST3 plug-ins.

Tj Shredder · Post by **Tj Shredder** » Sat Aug 01, 2020 8:16 pm

Feature request...

Blue Cat Audio · Post by **Blue Cat Audio** » Mon Aug 03, 2020 8:10 am

I can't promise anything but we'll see what we can do. As it is proprietary to VST3, it would be an optional API anyway.

Blue Cat Audio

KVR Audio

Plug'n Script Control Change Events