Cockos Incorporated Forums - View Single Post

Ollie · 06-06-2011, 04:22 PM

The plug-in is at its proper place, the only way I can imagine how this could happen is that it crashed during scan so REAPER disabled it (never seen that happening with a REAPER plug-in though).

To check that, find reaper-vstplugins.ini (in REAPER's Application Support folder) and open it in TextEdit. Then look for the Reatune entry, it should look similar to this:

Code:

reatune.vst.dylib=806D09B29AB7CB01,1919251566,ReaTune (Cockos)

If the second block of numbers is missing, the plug-in was disabled during plug-in scan.

Removing the REAPER resource folder could fix that like clicking "clear cache and re-scan" in Preferences->Plugins or just removing said file - except it crashes again, so let's hope it won't.

06-06-2011, 04:22 PM	#11
Ollie Super Moderator (no feelings) Join Date: Dec 2007 Location: On or near a dike Posts: 9,836	The plug-in is at its proper place, the only way I can imagine how this could happen is that it crashed during scan so REAPER disabled it (never seen that happening with a REAPER plug-in though). To check that, find reaper-vstplugins.ini (in REAPER's Application Support folder) and open it in TextEdit. Then look for the Reatune entry, it should look similar to this: Code: reatune.vst.dylib=806D09B29AB7CB01,1919251566,ReaTune (Cockos) If the second block of numbers is missing, the plug-in was disabled during plug-in scan. Removing the REAPER resource folder could fix that like clicking "clear cache and re-scan" in Preferences->Plugins or just removing said file - except it crashes again, so let's hope it won't.