1.) I generally create all of the tracks using MIDI, VI's etc. I then Bounce the tracks to audio and keep the original MIDI tracks within the project. I Freeze/Protect/Hide these MIDI tracks so I can use them later for editing purposes. I tend to have 8 or so stereo Audio tracks when all said and done. Will this help the project open much quicker, and lower CPU STrain??
Watch out for the EXS. Logic tries to keep the samples in memory but if it cannot hold them across projects, they will get reloaded and big sample libraries take their time to load. Not only the EXS, all sample players need time to load the libraries. Hiding the tracks does not prevent the samples from loading.
For playback purposes I recommend bouncing everything and removing the instrument tracks. Projects with audio only load super fast because the audio data doesn't get preloaded.
2.) Will a little automation contribute to a slower opening of the project?? (simple volume, pan...) ALthough I realize that ANY insert plugins will slow down this process
Automation does not slow you down so far I know. Plugins do, you see it everytime you open a project. It will not be different on stage
🙂
But if you bounce all audio for backing tracks you would not have any automation. Just projects with audio files, ready to play.
3.) I will be using 4-8 outputs. Will this slow things down??
No.
... I am trying to send multiple stems of stereo audio to FOH, and also have the ability to run video, have MIDI messages control DMX lighting, etc...
Ok, so you will have a couple of MIDI tracks. But no need for virtual instruments or did I miss something? If you want quick song switching, audio and MIDI tracks are ok. Virtual instruments and a lot of big plugins may not be ok for you.
I realize that Logic Pro is intended for studio use, and I do alot of work with it there as well, but I am simply trying to make it work for me on stage as well.
I think my statement
"This is a studio application!" came across the wrong way. Of course you can use Logic on stage and it is very powerful there. I just wanted to say that it is not thought for that and has no convenient interface nor specialized functions for live performances. Maybe the following examples describe what I mean:
- Backing tracks only: Logic.
- Very simple backing tracks: maybe the Mac's Finder is enough.
- Convenient and quick song switching with backing tracks, probably MIDI controlled: use something else.
- Backing tracks and live instruments with short setup time: Mainstage.
- Complicated systems with playback, light control etc: Logic.
- For gigs that involve a lot of switching but a few MIDI processing: Mainstage.
- Systems with complicated functions and much MIDI processing: Logic.
- For CPU-hungry plugins: Logic or standalone programs plus Mainstage, if the computer is strong enough.
- and so on ...
I hope this makes it clear. There is no jack-of-all-trades application. Since Mainstage we have a specialized application but we still have to think about the system we need, test it and find out what is best for the particular usage.
It seems logical that the program one is most familiar with, is the first candidate for the live performance too. But this is not always the right decision. One single feature you may need can make the work on stage complicated if the program does not support it on its own.