Hi Please confirm if this is user error, a bug or not released for vstv3 at this point.
Best Regards
John
@hudson It probably just doesn't work for VST3 (for silly technical reasons described in some detail in this post). If your DAW can use the VST (VST2) version of Unify, I'd advise doing so. The VST3 version of Unify has absolutely no advantages over the VST.
@getdunne Thanks, yes that was it, i am happy to use vst2 Bitwg has a preference option which i had set to 3 no i have 2 availble and confirmed prog is rocking on 2. many thanks
Huds
one update, maschine does not vst 2 or audio units on mac silicon vst3 works fine but i am back in the no prog situation again.
I have one othe query that may be an alternative. is it possible to route prog change from external devices to vst's plugins in unify vst3?
maschine does not vst 2 or audio units on mac silicon vst3 works fine but i am back in the no prog situation again.
Some hosts are not able to send MIDI program-change messages to VST3 plug-ins. Gig Performer was recently updated to fix this problem.
To test whether PC messages are getting into Unify hosted in Maschine, temporarily switch off the MIDI Bank/Program Change and Bank/Prog error messages checkboxes in Unify's Settings view, and restart Maschine to ensure that the change takes effect. Then open an instance of the Unify VST3 and add an instance of the built-in MIDI Monitor plug-in as the instrument on the INST1 layer. Do whatever you do to send PC messages. If they show up on the MIDI Monitor, they're getting in. If not, you may need to contact Native Instruments support to report this issue.
Is it possible to route prog change from external devices to vst's plugins in unify vst3?
No, the Unify plug-in can only receive MIDI from its host.
