A composer’s orchestral project in Logic Pro kept crashing because he had put plugins on individual tracks and there wasn’t enough CPU power to cope, and routing the instruments to buses instead stopped the crashes.
He was working with a recording of an orchestra that had been split into stems, importing them into his own Logic Pro system and mixing them, on a live project that he needed to get right in a professional capacity. He had been reading about stems and bussing his tracks and knew he needed to do it, but he’d got a bit stuck with actually putting it into practice. He had applied plugins on some of the tracks, and they were causing Logic to crash because it didn’t have enough CPU power to cope.
I had worked with him before on the same kind of project. That time I suggested that, with such large quantities of files to import, using Create Track Stack to make track folders would be a sensible approach. This time he wanted advice on using plugins.
The crashes made sense to me. Logic isn’t designed for you to put plugins on every instance of an instrument in a large, complex mix. It makes much more sense to route the instruments to buses and put the effects there, which is far easier on your CPU.
For example, you could have one reverb for all of the strings. My client might potentially end up with as many as 400 strings in this project, and feeding them all into one reverb makes life so much more simple in terms of CPU usage.
Once we had routed the instruments to buses, the crashes stopped and the tracks played back properly.
I also helped him with some files that had been moved out of their stem folders. It took a little bit of detective work to put them back in the right places.
In a large mix, effects such as reverb are better on a bus that the tracks feed into than on every track, and Logic’s CPU load stays far more manageable that way.
Not sure it’s the same problem? Ask a question first
