Yes, I looked into the VST3 specs - and here comes the real trouble.
Unfortunately Steinberg has completely rewritten the VST3 API.
So changing BASS_VST to support VST3 would mean, that it has to be completely rewritten - I am not even sure, if any backward compatibility would be possible, it really looks like a brand new BASS_VST3 add-on would be needed.
So I started to further investigate the VST3 API, but due to my lack of in-depth C++ knowledge and available samples at this time, I finally gave up.
It also seems, that almost no other application except Steinberg apps (like Cubase) today supports VST3 - and there are today only a very few VST3 plugins available at all.
But what is the real problem?
The real problem is, that if you want to build a 64-bit application which supports VST, you would need to go with VST3, as only the VST3 API supports native 64-bit plugins. The VST2 API is a pure 32-bit architecture.
Or you'll find a way to run all the available 32-bit VST2 plugins from within your 64-bit application.
And this is actually possible...
Most other 64-bit professional applications are providing a kind of 'vst2_host.exe' which acts as a bridge between the 64-bit and 32-bit world. This 'vst2_host.exe' bridge is a 32-bit process, which host the 32-bit VST2 plugins itself and which communicates with the/your 64-bit application via IPC (inter process communication) to exchange the sample data in real-time.
This is e.g. what
http://www.cockos.com/reaper/ is doing.
So I guess there are two steps needed:
a) Build a native 32-/64-bit BASS_VST3 add-on based on the new VST3 API.
b) Build a 'vst2_host.exe' and some BASS DSP interfaces to this bridge via IPC.
I guess I am not the right person to do both of them, as I am not skilled enough when it comes to C++.
So I guess somebody else would need to jump in and take over all this work....?!
