Hi! I have a strange thing going on with Reaper and VTM-M2. R2R and Tapebooster and every other plugin is showing up in Reaper 4.402, but not VTM-M2. In Cubase 6.5. however, no problem, there it shows up.
Is there something special I have to do regarding this plugin?!
Yes, I have: - checked the correct plugin path in 'Vst plugin settings' - I have pressed the button 'Clear chache/re-scan' - checked if the plugin perhaps has another name, but unlikely since it's showing up in Cubase 6.5. as VTM-M2
Can anybody help me out here? I just don't know why this is happening!
Last edited by dagovitsj on Sat Oct 12, 2013 6:53 pm, edited 1 time in total.
If Rescaning and Cache Cleaning doesnt work you could try to delete the reaper-vstplugins.ini file(options...Show Reaper resource path in explorer/finder. On restart every plugin folder is scanned completely new, takes a bit time but this way i could see the plugs which didnt appear with normal scan.
Just for "fun", could you try searching under "CDSoundmaster" in Reaper? If nothing, then maybe try uninstalling VTM-M2, open Reaper, close it, then re-install VTM-M2. I know it seems goofy, but try it. It's important to open and close Reaper in between the uninstall and reinstall so Reaper can "see" that it's gone.
Hi Dag, since it's not an Acustica items I'll continue help in email, but most likely it revolves around a change in setup, and if there are 32bit and 64 versions- I've noticed later updates of Reaper having issues differentiating the vstplug ID's if 2 are present. I found that, on a 64 bit OS running Reaper 64, simply removing the 32 bit version allows it to scan the 64 bit folder fresh on its own, and vice versa it will recognize the 32 bit version as long as it is in the x86 folder it shows VTM-M2 (CDSoundMaster x86) in vst list- when 32 bit removed and 64 bit fresh installed- it shows VTM-M2 (CDSoundMaster). I'll say more in email. Hopefully all happy and working asap!
dagovitsj wrote:@ Michael: I've sent the details. Just posted here to see if there was some obvious things I had forgot!
@SpliffSplaff: Thanks for the tip, but unfortunately it didn't work. Hope Michael can find out about it
PS: This is not related to the new version of Nebula as far as I know, 'cause I run 1.3.505. Just wanted to say!
In addition to what Michael just said, I can say with 100% certainty (as a long time Reaper user) that if you do want both 32 and 64bit versions of any plugin installed, make sure that the 32bit path is listed first in the scan path in Reaper.