Here's a tip that might save you some headaches. If your using Flex Editing and you do a good number of trax with Flex, Be sure you record your flexed tracks to an audio channel, then shut off your flex mode and mute your original trax. I typically use 5 microphones at a time so each group have 5 different audio trax from which I might do my flex editing before I record the mixed down tracks, or even after the mixed down, I some times use Flex on the finished track. The point is, after you have flexed your track, Bounce it out or record it to an audio channel and save yourself some CPU strain. My groups look like the screen shot below. If you were to leave the groups in the Flex mode and simply mute them and disable all their plug ins, your CPU is still crunching the numbers for Flex on those trax. I had done some flex work on a large number of trax and did not shut off the flex mode. That gave me a loaded down CPU with over load messages. I was puzzled since I had 1024 for buffer size and an 8 core mac. It was the Flex mode running in the back ground. You can always turn the flex mode back on and all work is retained. If you try and freeze the track with Flex mode, no good, Flex is not a plug in and eats CPU big time. Hope that saves you a headache and any bumps you might hit in a project. [img]http://mojaveampworks.com/scrn/choke.jpg[/img]

Nice Tip Victor!! Thanks for sharing :)

Thanx. I've had that problem. Now I know why