Has anyone managed to get Kontakt 6.6 VST3 to scan and work in VEP7?
It's not seen by VEP here on Windows 10.
194,336 users have contributed to 42,916 threads and 257,955 posts.
In the past 24 hours, we have 2 new thread(s), 12 new post(s) and 82 new user(s).
Has anyone managed to get Kontakt 6.6 VST3 to scan and work in VEP7?
It's not seen by VEP here on Windows 10.
Hopefully VE-Pro 7 will be updated soon by VSL to support VST3 hosting.
This is very overdue. VST3 is becoming the current standard. Especially with Kontakt 6.6 now running as a VST3 only, VST3 support by VE-Pro 7 is badly needed.
Please VSL Development, update it so we can use VST3 instruments in VE-Pro 7.
Thanks,
Muziksculp
Kontakt 6.6 isn't VST3 only. The VST version of 6.6.0 still runs in VE Pro.
It is, however, a little ironic that VE Pro is available as a VST3, but doesn't support them.
Kontakt 6.6 isn't VST3 only. The VST version of 6.6.0 still runs in VE Pro.
Yes, that's right, but VST3 is becoming the current standard format. So, being able to host VST3 in VE-Pro 7 is an important feature that's missing.
Thanks.
For those currently hosting VST Superior Drummer 3 in VE Pro 7.
Toontrack recently upgraded their EZdrummer 2 to EZdrummer 3. It is worthy of note that this upgrade is only available in VST3 format (and AAX & AU).
Toontrack have said that their Dev Team have moved from VST to VST3 for EZdrummer 3.
Whilst Toontrack will not commit themselves to an unambiguous statement. It is likely that any future upgrades to Superior Drummer 3 are likely to follow suit. A sure sign of things to come.
VSL; Has there been any real progress on the VE Pro 7 VST3 hosting front?
Thanks.
Kontakt 6.6 isn't VST3 only. The VST version of 6.6.0 still runs in VE Pro.
Yes, that's right, but VST3 is becoming the current standard format. So, being able to host VST3 in VE-Pro 7 is an important feature that's missing.
Thanks.
You should also be advised that the VST3 format has some design flaws that can come up related to midi and vst3 instruments. A lot of people, including myself, will always use the VST2 version of any instrument when it is available. Eventually we may have no choice but to use the flawed VST3 versions...but generally speaking we are not there yet. For instrument use, you are better off using VST2.
The VST3 Api is considerably more complicated then VST2, so despite the fact that the VePro plugin comes in a VST3 version, the actual "hosting" of VST3 instruments is a completely different set of things to deal with and would probably require quite a re-architecture in VePro. In short what I am saying is that its a small deal, to make a VST3 version of a plugin, but its a much bigger effort to convert a host such as VePro into being able to support hosting VST3. I'm sure VSL will get there eventually...its all good, but in the meantime, you're actually better off using VST2 instruments anyway because of what I said in the first paragraph.
Has anyone managed to get Kontakt 6.6 VST3 to scan and work in VEP7?
It's not seen by VEP here on Windows 10.
Hi,
There are several ways to load a vst3 in a non vst3 supported host, for instance with Blue Cat's Patchwork Synth.
You load it as a VST-Plugin in VEP7, and there you can load your VST3..
Hope this will help..
Cheers!