I also accidently removed the FG-X comp and so on the same page I downloaded the latest copy and installed that. Then I re downloaded the latest version from the Slate site and it worked!
#SLATE VIRTUAL MIX RACK VS VBC INSTALL#
Then I also removed all the install files. UPDATE: Steven Slate and Perry replied and said to remove all VMR and VTM from the VST, VST3, and AU components directory. In the mean time if anyone has any fixes PLEASE post them here! I got sessions to do! If I have to go back on any the whole mix will have to be substituded and will probably change the whole feel! So next I will try loading an older version. I eliminated a few rogue plugins in the process but when I remove VMR and VTM from AU,VST and VST3 Reaper loads and shows those no loading of course. Seems like VTM locks reaper loading and VMR just throws a crash report. I guess I'll reinstall and choose the VST2 option instead if that is the problem.
Oh, and I installed the VST3 plugins - don't know if that makes a difference.Īh ok, they are mostly VST3. Are there any other settings I need to change to get this to work?įaulting application name: reaper.exe, version: 5.2.2.0, time stamp: 0x5787e5b9įaulting module name: VCC Channel.epl, version: 1.5.0.1, time stamp: 0x573ca369įaulting application start time: 0x01d1ed84719da334įaulting application path: C:\Program Files (x86)\REAPER\reaper.exeįaulting module path: C:\ProgramData\Slate Digital\Virtual Mix Rack\Modules\VCC Channel.epl\Contents\Win32\VCC Channel.epl I'm using 32-bit Reaper, with 32-bit plugins. "Run in dedicated process" works for one plugin: I can tell this as the UI is embedded in Reaper, and I haven't selected "Embed bridged UI". However, this isn't working for several of the plugins - they continue to run in the Reaper process. Normally, when plugins cause this I just choose "Run as dedicated process". I've just subscribed to the Slate Digital 'Everything' bundle, and I'm having a bit of trouble with the stability of Reaper.
0 kommentar(er)
