Might well need to sort out my registry.but that could be a dangerous path. Slate Digital were quite helpful but suprised that there was an issue using Reaper and couldn't give any new suggestions. So this really indicates an installation issue and not a Reaper issue. VST2 also wouldn't load from the standard VST2 location in Reason standalone version 11.
Slate digital vmr 1.5 install#
May have been the same problem then? Or maybe there is a problem with this old install from a while back where I may well have installed the standard VST3 and VST2 locations leaving something somewhere which is preventing Reaper from loading VRM these locations now. Prior to this VRM installation, I know I installed VRM a while ago but uninstalled it soon after demoing. The installer allows you to choose a different location for the VST2 version if you wish. Just some problem somewhere with Reaper not being able to locate something correctly when the plugin is installed to the standard VST3 and VST2 locations (which are the locations the VRM plugin installer initially allocates. The problem was not to do with Reaper not locating the plugins on startup as they appeared in the reaper-vstplugins64.ini file as:. I only reinstalled VMR because I purchased the FG-Stress for a good price. Yes, got it working by installing the VST2 version to another folder that I have assigned for plugins on my hard drive. Although I can't actually find a sentry.dll file. "Settings" include the names of dictionary files to open and options to enable." This would seem to indicate a connection to Reason's use of VST plugins. But, on searching online, it "reads and writes its settings in the system registry. I am always deleting stuff from the reaper-vstplugins64.ini file to keep it manageable and never noticed a "sentry.dll" entry before. The "sentry.dll=00F7F73CC70BD701" only appeared after trying to load VRM VST2 in Reason so it's not an issue in the case of VRM not appearing in Reaper. The reaper-vstplugins64.ini file now shows this:-įrom the reaper-vstplugins64.ini file whilst trying to install it correctly. As an act of desperation, I tried to load VRM VST2 in the latest version of Reason but came up as an error with the Reason plugin management section showing the plugin's manufacturer as not recognised and "unknown error". This following very probably has no relevance.but just incase.Īctually I told a little lie there. But this doesn't seem to be an iLok issue as I think a screen would come up either whilst loading Reaper or whilst loading the plugin within Reaper itself, to request authentication if this wasn't done automatically.
Slate digital vmr 1.5 license#
The VST2 and 3 versions are installed to standard locations where my other plugins are located.Ĭhecked everything to do with iLok - all correct - iLok license activated and inserted in this PC. But no sign of them in Reaper's fx browser once Reaper opens. Once installed, both formats then get recognised by Reaper when starting up as indicated in the load up screen. I deleted the Virtual_Mix_Rack entries from the reaper-vstplugins64.ini file after each fresh install before loading Reaper. Installed various combinations of just the VST2, both the VST2+ VST3 and just the VST3. Slate Digital's Fresh Air appears correctly like this:-įresh_Air.vst3=00D1EEBA86C1D601,1158173615,Fresh Air (Slate Digital) With no plugin and developer's name, this would seem to indicate an error. The reaper-vstplugins64.ini file shows this:. Been spending the last 4 hours trying to get Slate Digital's Virtual Mix Rack VST2 or VST3 latest version 2.5.7.0 to appear in my Reaper 5.99 fx browser with no success.
0 kommentar(er)
