It also means that plugin developers can fix the mess they have already made using different UIDs for VST2 and VST3 without breaking backwards compatibility.ĪLL of this requires the plugin developer to implement it - it’s not a ‘automatic’ thing. Although currently I can only think of NI Kontakt that this VST3 equivalence might be useful for…and that’s because the made a bit of a mess of the plugin name. You might find a solution, or a report waiting to be confirmed. Cubase does not support VST 2 when running natively on Apple silicon Macs. VST 2 plug-ins only run in Rosetta 2 mode on Apple silicon Mac. This software version does not support 32-bit plug-ins. The latest VST3 SDK means that the plugin developer has more options to tell Cubase/Nuendo that the plugin is an equivalent, not just VST2 > VST3 but also from different version of VST3. Hello all, If you would like to report a bug in Cubase for other users to confirm, please start a new topic in the Cubase category with the tag ‘issue’ please follow these easy rules: Before you post a new report, use the search function to see if it was already reported. Cubase does not support VST 2 when running natively on Apple silicon Macs. It’s possible/probable that those same developers will keep making life difficult by not implementing this new(ish) VST3 feature. Some plugin developers don’t do this unfortunately…and it’s annoying. In fact you’ve probably noticed that if you have a VST2 and the same plugin in VST3 that cubase ‘hides’ the VST2 plugin from you (in most cases!) Most developers used the same UID for VST2 and VST3 and so the transition should have already been seamless. This was already available and working fine in most circumstances. It would make it easier for us to replace older VST2 versions of plugins with newer VST3 counterparts - correct?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |