What fixed it for me: I have three VSTplugin folders (no idea why): C:Programs (x86)SteinbergVSTPlugins C:Programs (x86)Steinbergvst C:VstPlugins C:ProgrammsVSTPlugins The last one is the one that worked for me.Anyone ever had issues with 64 bit Valhalla plugins in Windows.
Valhalla Room Vst Windows 7 Setup AndI am finishing up installing plugins on my new Windows 7 setup and I am having issues with Valhalla Vintage Verb and Freq Echo (the only Valhalla DSP I have) not showing up in either Tracktion or Studio One.
I had the same issue with NIs Replika and I was able to rename it to get it to work, (which I have had to do on a mac with other plugins before) but that didnt work with Valhalla. I tried re-starting computer, re-scanning plugins, re-installing into different folder and adding it to the DAW scan list, re-naming, re-downloading, etc. Valhalla Room Vst .Dll Files AreThe.dll files are in my VST folder for sure. Valhalla Room Vst 32 Bit Versions AndAs I was writing this, I decided to try installing the 32 bit versions and using Tracktion 32 bit and both plugins showed up. Obvious questions: 1 You are running 64 bit windows 2 Are you running 64 bit Studio One Ive no problems with Valhalla vintage verb 64 in studio one 64. Im pretty sure that the 32 bit version of Valhalla wouldnt even run in 64 bit studio one as studio one doesnt have a built-in bridge like some other daws do. Youd need something like jbridge just to run the 32 bit plug in 64 bit studio one (as I said Im about 80 sure this is the case). The 64bit versions work fine in Live 9 64bit and Win 8.1 64bit. No problems here with Valhalla 64bit on W7 in Cubase, Reaper, and Live (I also run 32bit Live on same system with each plug with no problems). If you had to rename it to get it to show that sounds like a bigger problem than Valhalla. Im sure its on my end because otherwise Im sure google would have turned up something. But I dont think its a DAW thing either since I get the same problem with both. I also had no problems with plugins from about 10 other vendors. I have had to do the renaming thing on my Mac for another random plugin in Studio One. I am indeed running 64 bit Windows and DAWs, I specifically had to go to the program folder of Tracktion to open the 32bit one and I never even install 32 bit plugins if I have the option. Keep in mind there are 32-bit versions and 64-bit versions, and usually they get installed to different folders. If the 32-bit version appears and the 64-bit version doesnt, that would imply you have either a 64-bit issue w your OSDAW or your 32-bit VST folder is included in the path, but not your 64-bit VST folder. So I just installed Studio One on my wifes computer with Windows 7 and tried VintageVerb and it worked fine at 64 bits. Im pretty bummed because I have tried everything I can think off, it was literally the last two plugins I needed to install, and those are the only reverbs I use. I will hit up Valhalla this week, but I am feeling oddly pessimistic at this point. SOLVED My pessimism was unfounded as Valhalla got back to me very quickly and let me know that a few folks have needed to install a Windows Visual C update. I installed the x64 version of that and everything works great. For anyone finding this thread with the same problem Google this: Microsoft Visual C 2010 Service Pack 1 Redistributable Package MFC Security Update.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |