VST3 in Reaper
-
- KVRian
- 1094 posts since 23 Sep, 2006
Should do, up to today i was using Reaper 4 (64bit VST2) and Adobe Audition (VST3) and everything works as expected, you wouldn't know they were different plugin types.
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122 - KVRAF
- 14339 posts since 15 Mar, 2008 from Czech republic
Hmmm, Reaper has VST3 support?
Anyway it depends on the host. The plugin interface is just a connection between the host and the plugin. Our plugins have the exact settings for all of them. But of course, the host needs to find the right one and use it properly.
Anyway it depends on the host. The plugin interface is just a connection between the host and the plugin. Our plugins have the exact settings for all of them. But of course, the host needs to find the right one and use it properly.
-
- KVRian
- 1094 posts since 23 Sep, 2006
By the way, I switched over to VST3 in Reaper today, everything is fine. However, obviously everything shows up twice in reaper now. I was hoping if i removed VST2 plugs that Reaper would be smart enough to remap old sessions using VST2 plugs to VST3 versions, unfortunately that's not the case and they dont load. Therefore, i'm having to keep the VST2 stuff for compatibility reasons with old sessions, and have just switched out my favorites folders over to VST3 so future ones will use VST3. Shame there's not a better solution to this.
-
- KVRist
- 360 posts since 12 Mar, 2005
What you can do to ease the pain:
Open your reaper-vstplugins64.ini file and locate the VST2 versions of the plugins.
like this: MAnalyzer.dll=88161429C2C1D001,1296131426,M-Analyzer
Remove everything after the first ID so you will have this:
MAnalyzer.dll=88161429C2C1D001
The plugin wont show up in Reaper anymore but WILL be loaded in any project still using it.
Open your reaper-vstplugins64.ini file and locate the VST2 versions of the plugins.
like this: MAnalyzer.dll=88161429C2C1D001,1296131426,M-Analyzer
Remove everything after the first ID so you will have this:
MAnalyzer.dll=88161429C2C1D001
The plugin wont show up in Reaper anymore but WILL be loaded in any project still using it.
-
- KVRian
- Topic Starter
- 975 posts since 10 Jan, 2007 from London
Vectorwarrior, I've been wondering along the same lines.
Vojtech would probably say don't worry about it, just leave both VST2 and VST3 where they are, and after all (in Reaper at least) it is clear in the FX browser which is which.
The suggestion by Mace404 is interesting, but I guess if you were adamant about losing the VST2's you'd have to go through all your old projects, manually replacing VST2 with VST3 and loading the same preset (if an internal Melda preset), but if you had used a Reaper (rather than Melda) preset you'd have to save your VST2 settings as an internal (Melda) preset, then load the VST3, then load that saved preset...hmm, lot of work...
and I wonder how Reapers Parameter Modulation/ Automation relates to the 'new' plugin??
Vojtech would probably say don't worry about it, just leave both VST2 and VST3 where they are, and after all (in Reaper at least) it is clear in the FX browser which is which.
The suggestion by Mace404 is interesting, but I guess if you were adamant about losing the VST2's you'd have to go through all your old projects, manually replacing VST2 with VST3 and loading the same preset (if an internal Melda preset), but if you had used a Reaper (rather than Melda) preset you'd have to save your VST2 settings as an internal (Melda) preset, then load the VST3, then load that saved preset...hmm, lot of work...
and I wonder how Reapers Parameter Modulation/ Automation relates to the 'new' plugin??
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122
- KVRAF
- 14339 posts since 15 Mar, 2008 from Czech republic
Hey folks, as golgglob correctly anticipates, don't worry about it! 
There isn't a big difference in the plugin formats. The main reason for VST3 development was that VST2 doesn't officially support sidechains. But in Reaper it doesn't matter as it technically doesn't support sidechains, well it does, but it basically takes all inputs at same level. It's great for flexibility, bad for workflow, which is quite expected.
So in Reaper VST3 doesn't bring much improvement. Maybe the sample accurate automation, but if you already did something using VST2, I think it's actually better to keep it that way. It's just a plugin format...
There isn't a big difference in the plugin formats. The main reason for VST3 development was that VST2 doesn't officially support sidechains. But in Reaper it doesn't matter as it technically doesn't support sidechains, well it does, but it basically takes all inputs at same level. It's great for flexibility, bad for workflow, which is quite expected.
So in Reaper VST3 doesn't bring much improvement. Maybe the sample accurate automation, but if you already did something using VST2, I think it's actually better to keep it that way. It's just a plugin format...
-
- KVRist
- 360 posts since 12 Mar, 2005
You will have to redo automations afaik.goldglob wrote:Vectorwarrior, I've been wondering along the same lines.
Vojtech would probably say don't worry about it, just leave both VST2 and VST3 where they are, and after all (in Reaper at least) it is clear in the FX browser which is which.
The suggestion by Mace404 is interesting, but I guess if you were adamant about losing the VST2's you'd have to go through all your old projects, manually replacing VST2 with VST3 and loading the same preset (if an internal Melda preset), but if you had used a Reaper (rather than Melda) preset you'd have to save your VST2 settings as an internal (Melda) preset, then load the VST3, then load that saved preset...hmm, lot of work...
and I wonder how Reapers Parameter Modulation/ Automation relates to the 'new' plugin??