Audio Configuration window: Option-drag [Alt-drag] any effect. The window doesn't scroll, and you can't drag from one Audio Config window to another either.
Open the Audio Configuration window and use the handtool to move inserts. Using Option [Alt]-handtool will copy effects instead of moving them.
After installing Logic 6 from the software CD vol. 6 a problem might occur regarding the Mac OS X access permissions (Unix ownership) of the plug-in settings files. As a result it is possible that the parameters of the plug-in setting are not updated.
Immediate workaround: duplicate the plug-in settings folder and delete the original folder.
Solution:
1. The problem is fixed in the installer of software cd vol. 7 or higher,
or
2. Download: service.emagic.de/files_download/EmagicPluginSettings.dmg.gz
Save your song specific plug-in settings here:
[any path] \ [Song Name] \ Plug-in Settings \ [Plug-in Name] \ [Song Name] \ Setting.pst
Then make an alias (a shortcut on PC) of the "Song Name" folder (the one inside Plug-in Name).
Store the alias (shortcut) inside
[Logic path] \ Plug-in Settings \ [Plug-in Name] \
so that you see
[Logic path] \ Plug-in Settings \ [Plug-in Name] \ [Song Name] (or [Song Name.lnk] on Windows)
Double clicking the alias will bring you to
[any path] \ [Song Name] \ Plug-in Settings \ [Plug-in Name] \ [Song Name]
After doing the above, your plug-in's preset-menu will now contain a sub-menu with the name of your song, and the presets for this song & plug-in inside this sub-menu. Since you use an alias [shortcut], the actual presets are saved in your song's folder, and are thus automatically saved when you make a backup.
Example: your song "Worldhit" uses a Distortion plug-in with a custom setting called "Xtreme". The song is saved in a folder called "Worldhit". Inside this folder you create the folder hierarchy "Plug-in settings \ Distortion \ Worldhit" in which you save the Xtreme setting, yielding "Worldhit \ Plug-in settings \ Distortion \ Worldhit \ Xtreme.pst"
Create an alias [shortcut] of the last Worldhit folder, and put it inside the "Logic Application folder \ Plug-in settings \ Distortion \" folder.
Note: for a far more elegant way of working with song-specific EXS instruments, see the question "How do I save my song-specific instruments without cluttering the instrument-list?" in the Emagic plug-ins chapter of this FAQ.
In your Logic application folder, there's a directory called "Plug-In Settings". In that folder, you should see another one called "xxx" (where xxx is the name of the virtual instrument or plug-in you're dealing with). Place your *.fxb files in there and you should be able to access them.
They are plugin preset banks. You can't load them in Logic (yet?).
Each plug-in insert slot "occupies" 16 control numbers, starting from CC64. So, if you have a plug-in in slot #1 the controllers start at CC64, the second slot's plug-in starts at 80 and so on. If the plug-in has more than 16 parameters and you insert a second plug-in in slot #2, you won't be able to automate parameters 17 and up as the second plugin "occupies" everything from CC80 and up. The way around this is to insert the second plug-in in the 3rd slot instead of the 2nd, thus allowing the first plug-in to use 32 controllers instead of 16.
Here's how I usually setup such things (might sound like a lot of work, but as always, once you got used to it, it's very fast):
Just switch the plugin to the "Controls" interface and count from top to bottom. Since the first insert slot uses CC's 64-79, the 2nd slot uses 80-95, etc (16 CCs per slot), it's now easy to just count out which parameter corresponds to which CC. Example: the 2nd parameter in the 1st insert slot is controlled by CC 65, remember the number and automate the corresponding CC.
DX plugins can't be automated.
Hold down Option [Ctrl] before clicking on the insert slot. The slot has to be 'empty' when you do this. Now on stereo tracks, you should get the m/m and m/s plug-ins, and on mono tracks, you should get the s/s plugins.
Logic is the host. Host sync means you can synchronize a plug-ins parameter (e.g. the LFO of a synth plug-in) with the clock of the host. Since Pluggo also has some arpeggiated synths (and more timing dependant stuff) it would be nice to have them synced this way and not with the Pluggo sync plug-in which is kind of a workaround for not having host sync in VST-1.
If you Option-click [Ctrl-click] a plugin or VSTi in the environment, it will be bypassed.
PowerCore and UAD1 plugins are indeed rendered into the Freeze File. However, the plugins aren't de-instantiated to recover the DSP horsepower. They're bypassed, but as with any powered plugins this doesn't actually free up DSP.
Workaround: Save the preset of the plugin's parameters and de-instantiate the plugin. If you unfreeze the track, you'll have to re-instantiate the plugin(s) are recall said presets.
TDM doesn't have Freeze at all.
Question: I am somewhat confused by the info concerning VST, OSX and Logic. Is it correct that VST will not work ??
Answer: VST is not (and will never be) supported by Logic in OS X. VST is supported in Logic (including v6) on Mac OS9 though.
Question: Why in the world would you disable something that works for something in development (AU)??
Answer: VST support was/is there in the OS 9 version of Logic. It is a misunderstanding however to assume that because it works in OS 9 that it automatically works in the OS X version of Logic and that somehow they could've included its support without any work.
Simply put - both would have required development. Now as to why they would drop VST support, this has been mentioned numerous times before: the VST-documentation for *host* developers (as distinct from plugin developers) was never complete and Emagic apparently had to figure many things out by experimentation. Steinberg as a competitor would always want VST to work better in Steinberg products than anyone else's whereas Apple wants AU to work just as good in any application. Also developers on the LUG have stated that things will be better with AU.
Possible workaround for virtual instruments: I'd imagine that because of the way that OS X works and thus Logic, that any VSTi-supporting app that could act as a MIDI port to Logic (i.e., so you can send MIDI messages from Logic and receive messages back) could do the trick...
Note: as of April 2003, fxpansion make a "VST to AU wrapper", which will let you use any VST and VSTi in any AU-compliant host (such as Logic). This seems to be the definitive way to keep using your non-AU'ised plug-ins. Go to http://www.fxpansion.com/products_auadapter.html for more details.
This is described in some detail in the chapter on Inserts, Sends, Busses and Aux Objects of this FAQ.
Method 1. Select the track in the Arrange window. Then in the Environment window set the effect the way you want it in the Audio Object (channel strip) then put the effect in Bypass mode. Set the Audio Object to rec. mode and at the point you want the effect click on the bypass button again to make the effect active and then click again at the point you want to deactivate it. You can activate and deactivate the effects in the Audio Objects by holding the Option key and clicking on them. The changes will be recorded in MIDI form in the track of the audio object. If you need to you can slide them around to tweak the timing.
Method 2. Set up a separate Audio Object with the effect settings you want. In the Arrange window use the scissors tool to cut the section of the audio region you want to apply the effect to and slide the section you want to effect onto that track.
Method 3. Set up a Bus Object with the effect you want and use the effect send. BTW you can activate or bypass the effect send in exactly the same way i.e. by holding down the Option key and clicking on them.
The advantage of methods 2 and 3 is that for delay type effects the tails will not get cu off. The advantage of method 1 is that it uses up slightly less system resources.
Connect your synth's audio output to your soundcard's inputs. In the audio mixer, set one object (channel strip) to be an Input object. I.e. in the object's parameter pane pick the proper entry from the Cha popup, like "Input 1-2" if that's what your synth is connected to. Now when playing the synth, the audio goes into Logic and there can be treated with effects to your liking.
If you would now 'Bounce" your song to disk, the effected external MIDI synth's signal would also be part of the bounced file. You thus don't need to render the external synth's sound to an audio file first, import that into Logic, place it on a track, etc.
In order to render the effected sound to an audio file (in case you want to free up your soundcard's inputs again for example), assign an Arrange track to a 'regular' Audio object (like Audio-1, i.e. of type "Track" in the parameter pane), whose input settings also are Input 1-2. Insert the effects in the Input object, and record on the Audio-1 track.
Also see the chapter on Inserts, Sends, Busses and Aux Objects of this FAQ, which describes extensively how to monitor effects with/without recording them.
I, got a hot tip from UA tech support. Apparently they found a workaround for the infamous Logic problem, where you can't use UAD-1 plugs on tracks in "live" mode. The solution is to actually force all UAD-1 plugins to get called in "live" mode (the problem before was having UAD-1 plugs getting called in both live and non-live modes). To do this:
Another possible use for this trick is to force certain plugs to run on the main processor when in MP mode. In MP mode, usually the plugins run on the second processor. However, plugs on "live mode" tracks run on the first processor, so you can also use this trick with your native plugs to get even more processing happening in MP mode.