If I recall, I THINK it may have been I directed VSTi's from a lesser Cubase version, to a higher version with similar/same VSTi's though. ![]() I think it was because something I directed Cubase to didn't like something. ![]() ![]() I then had to wipe out the whole thing and start all over with my list, and everything was fine again. once actually removing plug ins that had been there already & working. Keep in mond, in my experience anyway, that sometimes directing a different folder for Cubase's VSTi plugs ins to use, has resulted in a FUBAR!. What I did at the time was move the dll's into Cubases' VSTi folder.yeah that easy! But as said, if you go into Cubase's VSTi plug-ins, re-direct whatever plug-in folder you wish to use, and refresh/update your list. I used to run VSTi's from Cakewalk inside Cubase some years back.
0 Comments
Leave a Reply. |