![]() I'm aware Logic only uses Audio Units plug ins, I was generically speaking when I said "VST's".Pad controllers are available in all sorts of shapes and sizes to suit just about every production and performance task, from small-form pad-based sequencers, equally as home controlling a Eurorack setup as they are virtual instruments, through NI's Maschine range of controllers with dedicated software, right up to Ableton's Push 2, a pad controller specifically for controlling the company's Live DAW. I only checked the CS Setup in Logic 9.1.6 and it seems to be gone, it didn't tell me that Axiom Pro Hypercontrol in and out was not connected which it usually does when the Axiom is not connected so that seems like a good sign. All the steps you mentioned went smooth once I went to the Applications Folder in the Finder. After doing some further research I found out the "Show Package Contents" option could be accessed from the Applications Folder in the "Finder" (miscommunication). On my desktop there's an Applications Folder and I thought that's the one you were talking about. Your first suggestion worked but the miscommunication was "Applications Folder". Each version of Logic will scan new plug-ins if they haven't done so already.Īnd no, my suggestion is not limited to Logic Pro X. VST is such a popular plug-in format that it has become synonymous with "plug-in" for some people (especially Windows folks). Just to clarify, "VST" is a plug-in format which Logic does not support. Is your first suggestion limited to Logic Pro X and what impact will the older version of Logic scanning my new VST's have on Logic Pro X scanning for them (basically will it let me use them or could that have created a problem)? When this happens you can reopen it instead of force quitting it and if itcrashes again you can make it rescan problematic plug-ins again from the Audio Units manager (Logic Pro X menu > Preferences > Audio Units Manager.) The auvaltool sometimes crashes when scanning plug-ins, it's something that can happen depending on the plug-ins you install. This has nothing to do with our subject here. Applications/Logic Pro X.app/Contents/MIDI Device Plug-ins/Īnd because it was the first time opening Logic since loading up my new VST's, it scanned them and I was forced to "Force Quit" something called avaultool. You could also enter the following path in the "Go to Folder" dialog (from the Finder's "Go" menu): It has to be from the Applications folder. You can also try right-clicking if your mouse has two buttons.Ĭontrol-clicking it on the dock gives more options but not the one your talking about ("Show Package Contents"). To "Control-click" means to click on something while holding down the Control key. Sounds like you're not doing it correctly. ![]() ![]() I tried it with the older version of Logic (9.1.3) because that's were I configured it the first time but every time I try it just opens it - no options appear. ![]() What do you mean "didn't work"? Control-clicking the app in the Applications folder will give you a contextual menu and in it you will see the Show Package Contents option. I followed your first suggestion and the first step didn't work (control-clicking the Logic App in the Applications folder) However, I do know that the procedure I suggested will remove the hyper control stuff without leaving a trace.which sounded like what you were after. I don't know what the result of rebuilding defaults right after running the uninstaller would be. I basically just want one control surface ( Logic Remote ) controlling everything without confusion. I mentioned uninstalling manually (removing the Axiom Pro.bundle from the Logic app package) in case the uninstaller doesn't work for you (I think I remember someone having problems with it).īecause I don't like to throw things in the trash, would I get the same results if I ran the uninstaller and selected Logic Pro/ Preferences/ Control Surface/ Rebuild Defaults? I mean run the uninstaller and trach the cs prefs. an alternative to running the uninstaller? When you say besides this, do you mean trashing the control surface preferences as well as running the uninstaller or is trashing the cs pref. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |