![what would prevent a vst not opening in reason 9.5 what would prevent a vst not opening in reason 9.5](https://d29rinwu2hi5i3.cloudfront.net/article_media/f79db443-1e59-483e-bab3-bd7213d97fae/main.jpg)
- #What would prevent a vst not opening in reason 9.5 upgrade#
- #What would prevent a vst not opening in reason 9.5 pro#
I do understand what you're saying about wanting the freedom to change the plug-in architecture, and that identical settings in Pro-Q 1, 2, and 3 may sound different because you changed things under the hood. But with Kontakt 6 they've finally changed that: Kontakt 6 is known as plug-in "Kontakt" - and that strongly implies that if they decide to come out with Kontakt 7.0 in the future (which I'm sure they'll charge for) there won't be a need for users to replace older versions of the plug-in, since it will automatically upgrade. Kontakt 1, 2, 3, 4, and 5 were completely separate products, with separate authorizations, and separate plug-in ID's. NI used to have the same approach as FF with Kontakt. Hopefully this explains our thoughts a bit! Since we typically only release new major versions every four, five years, I'm not too worried about the growth of old versions that we need to support. In short, the current approach allows us to start "fresh" with each new major plug-in version which has very real benefits. For Pro-Q 2, we moved to an entirely different EQ engine which creates subtly different curves: again we wouldn't have been able to do that if we had needed to remain 100% compatible. We wouldn't have been able to do that otherwise.
#What would prevent a vst not opening in reason 9.5 pro#
That created problems for people controlling these parameters with a MIDI controller or a Pro Tools control surface, so in Pro-Q 3, we split these into separate "used" and "enabled" parameters. That means you can't change anything to the sound, which is really limiting, and you can't reorder or change parameters.įor example, in Pro-Q 2 there is a "state" parameter for each band with three options: unused, enabled, or disabled. I personally, however, don't think the current way of handling the issue is an elegant solution.īelieve me, we have thought about this a lot! The problem is that if you don't rename the plug-in and use a new plug-in identifier, you really need to be 100% backwards compatible. It's just when looking at Fabfilter's "additional downloads" page for legacy installers, I wonder what it will look like in a few years.Īgain, some people may not mind installing 10+ additional legacy installers if they need to recall an older project a few years down the line.
#What would prevent a vst not opening in reason 9.5 upgrade#
Then again, it may not be a huge issue - Pro-Q2 is still working prefectly fine and nothing keeps me from skipping the current upgrade and just continue using version 2. In addition, if it is supposedly possible to load presets from Q2 into Q3 - why not call the plugin "Pro-Q", keep the version number inside the plugin and transfer the settings automatically from older versions upon loading a project in your DAW? I also understand when developers stop supporting 32-bit versions or an outdated OS.īut I had the impression Pro-Q3 added mainly new features and filter types, but did not make any changes to the basic sound?
![what would prevent a vst not opening in reason 9.5 what would prevent a vst not opening in reason 9.5](https://i.ytimg.com/vi/JTmdd6nbiKE/maxresdefault.jpg)
![what would prevent a vst not opening in reason 9.5 what would prevent a vst not opening in reason 9.5](https://3.bp.blogspot.com/-TZAQtgl5t28/WDzCuU74-8I/AAAAAAAAAH8/Q3xisEd33-AG3y6D6crxEXp4sbAU4OJBQCEw/s320/iptv-vancouver-computer-tech-support.jpg)
Now, of course I agree with you that one can not demand 100% backwards compatiblity when there are fundamental changes to plugin algorithms, such as the filter model. My experience and a quick google search seem to suggest otherwise: Plugins from Waves, Soundtoys, Melda, Sonnox, Celemony and HOFA are supposedly at least backwards compatible to the previous version and should load upon opening an older project, or am I mistaken?