Currently JUCE does not support MIDI note names for either plugins or hosting. This is very important for drum plugins or else the user has no idea what sound each key triggers. I have implemented for VST2 plugin and host. I will look into VST3 and AU next.
I have a branch here where I am working on it, please consider merging into develop.
Whoa this is what I’m looking for! Thank’s for sharing this. I think that merging this into main JUCE framework is good, too
Can I ask you a simple idiot question?
Are there big differences between VST3 and VST2?
Is full re-implement required for use this method in VST3 environment?
Yes, big differences between VST2 and VST3, they are completely different. However, I’ve just implemented for VST3 and I think it’s working, or at least it’s working with my host and my test plugin.
If anybody knows of any plugins to test with, that would be helpful. For VST2 I’m testing with Xfer Nerve, however they don’t have a VST3 version.
Oh, oh!
I tried to build the sample PitchNames, but it seems not working in my DAW. I’m using FL Studio on Mac.
I don’t know whether FL’s not supporting VST3’s key naming method, but umm, did you tried it?
I thought I can do something with vst2wrapper (the document also described it just by adding cpp and few lines of code.) But compiling has failed. there was no vst2.x folder in plugininterfaces, so I downloaded older version of vst3 sdk by searching web, but failed. I think it’s now right way.
This is awesome! Patched VST3 code, can confirm it works in Reaper (although labels didn’t show up when I lazily assignes same name to all notes at first). Labels don’t show up in Cubase, but apparently you’re supposed to use Expression Maps anyway, so they’re not that useful. Haven’t tried other VST3 hosts yet.