That works just about every time for Waves BUT not for Xpand!2. That is to Remove the path that leads to their location, press OK, wait for S1 to do a little “Unscan” then Add the path back in again. I tried the trick I use when new Waves plugins won't show. I did all the Scan and Blacklist Reset things. S1 even saw it when it needed Activation but not when time came to use it. The Xpand2.big file was in the right place, everything was but S1 still wouldn't pick it up. Knocking the anti-virus off didn't help either. Xpand!2 was going in all right but Studio One wouldn't see it. It took me three installs but I did eventually get Studio One 4 to see and work with Xpand!2.Īfter the first failure I tried the suggestions on this and other sites. Just try that, and hopefully it will work. There is more to say about a weird sub-directory structure, but I will leave that out for now. The installer did its thing, and then I pointed Studio One to scan C: Program Files => VST Plugins => AIR Music Plugins. And then I extracted the zip file there, and ran the installer. If I remember right (only a 52% chance of that! ), inside of C: => Program Files => VSt Plugins, I created the "AIR Music Tech" folder. Program Files => VST Plugins => AIR Music Plugins (For both Xpand and Strike) But I tried so many things before I got it all to work. but Strike was a real M'F-er !Īnyway, I suspect that whatever I did to get Strike to work (I had Strike first, then later I got Xpand) also worked for everything else by AIR. Interesting (now that everything works!)- Xpand2 setup worked without a hitch for me, actually. I'll try a few conglomerations of some of the install techniques you all did above for Strike 2 but I may PM sirmonkey who seemed to figure it out. I still have not been able to get Strike 2 installed - and I really want to use that one! Scottyo7 wroteIt's so nice to hear I'm not the only one.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |