Quote:
Originally Posted by Justin
Sounds like you added a VLC folder to your VST plug-ins search path?
|
Hi Justin,
I've been using REAPER for a couple years and overall have been quite happy, even somewhat amazed by REAPER's capabilities.
However, recently I had a problem installing and organizing some plugins in REAPER in Windows 7 Pro 64bit. One plug-in I just installed in the regular "Program Files" folder. Then it didn't show up in the plug-ins scan. So I went into REAPER Preferences to set the search path to include "Program Files" so REAPER could find the plug-in, since I've got a lot of other plug-ins that auto-installed in the "Program Files" folder that work fine. I didn't think a scan could cause a serious problem. Big mistake, apparently... Not only did this crash REAPER almost immediately, now REAPER won't even start, but neither will it stop trying to start. I get the same messages over an over as REAPER tries to start:
"The program can't start because QtCore4.dll is missing from your computer. Try re-installing the program to fix this problem.
"The program can't start because libgegl1-0.2-0.dll is missing from your computer. Try re-installing the program to fix this problem."
At this point I spent several days getting REAPER set up and organized with all the plug-ins, so I'm hoping to avoid re-installing and organizing hundreds of plug-ins. I see in the Windows menu sidebar an option for "reset REAPER configuration to factory default" - will this solve the problem? What will I lose if I choose this option?
Any better ideas?
Now I can't get to the screen that tells me the REAPER version I've got, but the "Whats New.txt" inside the REAPER folder says "v5.26 - October 5 2016".
Installing plug-ins is actually the biggest problem I've had with REAPER, and I already had to do a complete re-install of REAPER once before because of a similar problem (i.e. confusion about where/how to install a plug-in). Also, by default REAPER always seems to automatically restart with the last open project, which sometimes creates a problem for me, when REAPER crashes for some reason and then gets stuck in a loop because it automatically goes to the last state, even if the last state was something that caused a crash. There's probably an option in the preferences somewhere for me to prevent this, but by then it's too late. Also it can cause a problem if I want to start a new project, and the last open project was a big one, and then I have to wait for all the files of the last project to load in order to close it to start a new project.