Here is an update. I opened up another project, and this did not happen at all. I let it run through the entire project, and everything worked as normal. Weird.
Sent from my iPhone > On Apr 2, 2015, at 12:34 PM, Chris Smart <[email protected]> wrote: > > Yikes. Is it a problem with specific hardware? > > At 12:16 PM 4/2/2015, you wrote: >> Hello, >> I have done extensive reading about this CPU error issue, and this is >> discouraging because it doesn’t look like there is a fix for this problem. >> Here is an accessibility question… How do you read the CPU usaage meter >> with voiceover? This is absolutely unbelievable that I have paid all this >> money for pro tools and I may not be able to use it. From what I have been >> reading on the forums, avid doesn’t seem to have any interest in fixing >> this problem. All I want to know is has anyone else on this list had this >> problem. This session has 10 tracks in it. There are no plugins on the >> session, and from what I was reading, it doesn’t matter if you have >> plugins in the session or not, the problem is still occurring. I am very >> frustrated. >> Brian >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Pro Tools Accessibility" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to the Google Groups > "Pro Tools Accessibility" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Pro Tools Accessibility" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
