-
Am I stranded?
Must I fly home to open my files? I am 7000 miles from home. I brought my Vienna Key and a clone of my sample data hard drive. When I try to open my Logic Pro 8 files, an error message appears: Logic Pro: Plug-In "Vienna Ins" not available! The Stand Alone application works, but the plug-in doesn't. Naturally, it's the plug-in that I need to open my files. Should I book a return ticket? Robert Randles Traveling with: 10.5.4 on MacBook Pro 2.6 GHz Intel Core 2 Duo 4GB RAM Two Acomdata 2TB Firewire 800 external drives
-
Tim, yes, one would think. That was the first thing I tried. As I said, the Standalone works, but the plug-in is not found. The Standalone is one of the four applications that are downloaded from the VI, if I understand what you meant. The others are the Directory Manager, the VI Library Installer and the VI Uninstaller. How or where does the plug-in fit into this? Is it an invisible file? Where does it live?
-
Thanks, DG. I'll check it out as a Logic problem. I'm still curious about where, exactly the plug-in lives. Strange thing is, the plug-in's place holder is showing up in the Apple area, not in the AU area. Perhaps as punishment for past sins, I had gotten used to Logic 8 and its not needing an XSKey, so I left it at home. For decades I have brought the kitchen sink along with me without really needing to, and ironically I thought I'd travel light this time. My selection of essentials is proving to be less than perfect—now I can't open a previous version of Logic that's sitting right there in front of me. At least I brought my son's favorite toys and my wife's favorite hair conditioner!
-
You might wanna try doing a re-validation of the audio units plugs for logic. Clearly something's gotten screwed up in there and sometimes letting it re-validate can clear the system. One can find the AU validator on the Logic Preference main menu .. it's called Audio Units manager. . If the standalone player is working fine then I very much doubt there's a problem with the VSL plugin itself. So give the validation manager a go and see if that helps. If nothing else it should help to ascertain if there really is a problem or not.
-
Could it be you're logged in to your macbook as a different user and your VI AU is sitting in HD/'other user'/library/audio /plugs etc.....?
Although by default one would expect the AU to be in the path as in the post above ie HD/library/Audio... etc
Just a guess, I'm not sure if this makes sense even....
-
Thank you, Maya and orchestralalala! You gave me the info on where to look to find out that the component had not survived Apple's Application Only Migration. Not there. I pulled it out of a backup of the drive I migrated from and popped it in. 24 other plug-ins had survived without problem, so maybe there's something different about VSL's? Thanks to everyone for your help and support. Now I get to stay put until spring!
Forum Statistics
183,091 users have contributed to 42,273 threads and 254,977 posts.
In the past 24 hours, we have 0 new thread(s), 2 new post(s) and 46 new user(s).