VST3 DLL -> bundle change, smoothly on customer side? (win)

Since Juce 7.0.6 Projucer-generated MSVC projects build VST3s as bundles, instead of DLLs.

My own older test-host, which is based on Juce, does not manage to automatically replace the old version with the new one in the project.

Is there any practical experience on the customer side? Can Cubase, Ableton, FL, StudioOne etc… do this or are there problems?

1 Like

For CMake based builds this has already been the case since JUCE 6, so we are shipping bundle VST3s for quite a while now. Can’t remember any problem with that being reported on the user side

1 Like