Another "Pro Tools crashing" issue

[Scott.Brownlee]

I have seen a few of these on here, so it appears I'm not the only one...

I realize there are a lot of moving parts to tech questions like these, so please bear with me. My knowledge of computer hardware is a lot lower than my knowledge of music theory.

I'm trying to write an orchestral piece with 23 instruments loaded (per the attached screen shot). To keep my computer happy, I usually Freeze the sections I'm not using. However, to make global tempo changes, I can't have any Frozen tracks.

This is where the problem starts.

All I have done with the attached is to Unfreeze all the tracks in my template, loading all the instruments back up, so I can change my tempo and meter. After I do that and save, I am unable to load the session back up again. Pro Tools just hangs with the lovely spinny blue circle of death and eventually goes non-responsive.

As far as I know, my machine should be able to handle a session like this, but it happens *all the time.* It's hard to tell from the screen shot, but I've loaded up the instruments within two instances of EastWest Play and four instances of Kontakt. I have a six-core computer, so that should potentially split the load among all six cores (I think).

Do I need a slave computer or something? Do I need to upgrade my existing computer again? Am I just asking too much of Pro Tools? I'm so baffled here and really need some help (explained in fairly basic terms).

Here are my full specs:
Windows 10 64-bit, Intel i7-8700 3.20 GHz, 6 cores, 32 GB RAM, SSD for main Windows drive and Pro Tools, instruments stored on a combination of internal HDD and external SSD (USB 3.0), Pro Tools sessions stored on internal HDD, running Pro Tools 2018.12.0.

[babaorum]

Do you have tried to increase the latency of your soundcard before re-open the project ?

[Scott.Brownlee]

I have not tried that, but I'm using a Scarlett Solo audio interface to drive my speakers (sorry, forgot to mention that above), so it's not likely a sound card problem...or am I wrong there?

[albee1952]

Originally Posted by Scott.Brownlee

I have not tried that, but I'm using a Scarlett Solo audio interface to drive my speakers (sorry, forgot to mention that above), so it's not likely a sound card problem...or am I wrong there?

Upping the buffer can help a lot but at the expense of latency. If tracking is finished, then this is not an issue, so pushing the buffer to 1024(or higher if available) will lighten the cpu load a lot. If you need that low buffer, instead of FREEZE, use Track Commit. When you use this option, you can choose what happens to the original track(Do Nothing, Make Inactive or Hide and Make Inactive). If you think you may need to make further edits, I would choose the "Make Inactive" option and MUTE the original after the COMMIT finishes(Inactive means it will use zero system resources, but should still respond to tempo adjustments). Set your new "commit" tracks to TICKS and enable Elastic Audio. That way, your printed tracks will also respond to tempo changes. You can always make an inactive track active again and re-commit if changes are needed

Another option is to decide on tempos early on and avoid those changes later(which might be tough, depending on how you like to work).

One more option that may help, depends on what plugins you use. Example: KeyScape pianos, which sound great, are real system hogs. If you substitute MiniGrand while building the piece, the cpu usage will be much lighter. Once you have the part and tempo finalized, swap back to the KeyScape plugin and commit the track.

[Scott.Brownlee]

Thanks for the tips. I didn't really know the difference between "Freeze" and "Commit," and enabling Elastic Audio would certainly make things easier. I'm finding it's bad when I begin a new project, because when I load up my orchestra template, everything begins as Frozen and I can't make any tempo changes that way when setting up the score. I'll give Commit a try instead.

The buffer idea still baffles me somewhat, but definitely worth a look.

I do find it surprising that my computer can't handle this many instruments at once, but I guess it's just a matter of deactivating them properly so it isn't overloaded.

[albee1952]

Originally Posted by Scott.Brownlee

Thanks for the tips.
1-I didn't really know the difference between "Freeze" and "Commit," and enabling Elastic Audio would certainly make things easier. I'm finding it's bad when I begin a new project, because when I load up my orchestra template, everything begins as Frozen and I can't make any tempo changes that way when setting up the score. I'll give Commit a try instead.

2-The buffer idea still baffles me somewhat, but definitely worth a look.

3-I do find it surprising that my computer can't handle this many instruments at once, but I guess it's just a matter of deactivating them properly so it isn't overloaded.

1-Time to make a new template

2-the buffer is an allowance of time(in samples) for the computer to process the audio. Big buffer means the computer gets more time to complete processing(more time=more latency). Small buffer means the computer needs to process everything in less time(lower latency) with more load on the system.

3-Very dependent on the plugins being used. Some require very little power from the computer, while others require lots of horsepower. It might help you to become familiar with which use more. That way, you can plan ahead(work those early and commit early), maybe choose different plugins(remember my comparison of MiniGrand to KeyScape's piano) or look into whether those "power hog" plugins offer a "lite" setting(example, leaving out ambiance samples or pedal noise. Or not loading stuff you won't really need, like 5 crash cymbals when you only need 1 or 2).

If you're wondering how to figure out which plugins are power hogs, start with a blank session and call up 10 stereo Instrument tracks. Note the cpu meter reading. Then holding the Alt key(PC) select one of your usual VI plugins on one track(holding Alt will load the same VI on all tracks). Once things settle and the plugin opens and completes the load, note the cpu meter again. Did it jump from 3% to 10%, or from 3% to 60% or higher? Repeat with each of your "usual suspects" and see what happens