rasure Posted June 16, 2021 Share Posted June 16, 2021 All Spectrasonics products have been updated. A few bug fixes and the addition of VST3 https://www.spectrasonics.net/news/news-content.php?id=125 4 Link to comment Share on other sites More sharing options...
Olong Johnson Posted June 16, 2021 Share Posted June 16, 2021 FYI, the Windows software update for Stylus RMX has a broken link. I emailed support. Link to comment Share on other sites More sharing options...
Fleer Posted June 16, 2021 Share Posted June 16, 2021 But, above all, they’re M1 native now Link to comment Share on other sites More sharing options...
locrian Posted June 17, 2021 Share Posted June 17, 2021 In the past you could simply replace a VST2 file with the same-named VST3 version and Cubase would register the latter for a seamless update. Doing this after the current update causes existing projects, containing the older VST2 file, to generate an error message saying that Omnisphere/Trilian are not found. Oh well, back to VST2... Link to comment Share on other sites More sharing options...
kitekrazy1 Posted June 17, 2021 Share Posted June 17, 2021 That's odd since Vst 2 and Vst 3 are not in the same folders. Link to comment Share on other sites More sharing options...
locrian Posted June 19, 2021 Share Posted June 19, 2021 On 6/17/2021 at 2:38 AM, Paul Young said: That's odd since Vst 2 and Vst 3 are not in the same folders. Contrary to the two Spectrasonics' VST3 plugins, the new NI VST3 plugins *did* switch successfuly in Cubase 11. By that I mean, despite swapping my old NI FX plugins from VST2 to VST3, they're all still recognized in my old projects (which originally used VST2). This did not happen with the Omnisphere and Trilian plugins. Link to comment Share on other sites More sharing options...
X-53mph Posted June 19, 2021 Share Posted June 19, 2021 6 hours ago, locrian said: Contrary to the two Spectrasonics' VST3 plugins, the new NI VST3 plugins *did* switch successfuly in Cubase 11. By that I mean, despite swapping my old NI FX plugins from VST2 to VST3, they're all still recognized in my old projects (which originally used VST2). This did not happen with the Omnisphere and Trilian plugins. I don't have cubase, but does it have an option to automatically replace VST2 with VST3 in projects (like CbB). If so, you could try turning that off (opting out) if it lets you Link to comment Share on other sites More sharing options...
locrian Posted June 19, 2021 Share Posted June 19, 2021 2 hours ago, Philip G Hunt said: I don't have cubase, but does it have an option to automatically replace VST2 with VST3 in projects (like CbB). If so, you could try turning that off (opting out) if it lets you I don't think so, but thanks for the suggestion. Cubase automatically chooses the latest plugin if more than one exists. If you don't want the one it chooses, you have to remove it (which is what I did for Omnisphere and Trilian). Link to comment Share on other sites More sharing options...
abacab Posted June 20, 2021 Share Posted June 20, 2021 On 6/19/2021 at 3:55 AM, locrian said: Cubase automatically chooses the latest plugin if more than one exists. If you don't want the one it chooses, you have to remove it (which is what I did for Omnisphere and Trilian). Studio One also does this. But I have learned that it takes two to be compliant. (1) The software dev has to set the proper flag in the plugin, AND (2) the DAW has to support it as well. 1 Link to comment Share on other sites More sharing options...
TheSteven Posted June 20, 2021 Share Posted June 20, 2021 Spectrasonics is pretty much on top off fixen bugs that they are aware of. So as long as someone somewhere has filed a bug report it should get fixed sooner than later. Link to comment Share on other sites More sharing options...
locrian Posted June 20, 2021 Share Posted June 20, 2021 1 hour ago, TheSteven said: Spectrasonics is pretty much on top off fixen bugs that they are aware of. So as long as someone somewhere has filed a bug report it should get fixed sooner than later. I just sent them an email describing the (Cubase VST3) problem. 1 Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now