In the meanwhile I've gone back to an auto save from yesterday, in hopes that I've gone to a version of the file that existed before things took a sour turn. I'll keep this thread updated to how that goes. You know. So you can all sleep comfortably at night.
I encountered a similar problem on a PC laptop with switchable graphics. I know nothing about Mac...but I do see that your MBP has switchable graphics.
First, are your GPU drivers up to date?
Look into your drivers...is there a way to switch to your GT 650M? Either manually or automatically when PPro starts up?
Does enabling/disabling MPE hardware acceleration for your project have an effect?
With my laptop, if I try running PPro with my higher-end GPU enabled, I would get a crash when touching media or dragging it down to the timeline. My only solution was to use my lower-end GPU.
Thanks Josh. The good news is, I think I've found a file that's back further enough that I'm seemingly OK.
Historically on this project I've bounced back and forth between two machines. One is a mac pro and the other is a mac book pro. The mac book pro is a bit newer, but...the ol' tower is still a power house. At least aledigedly. The problem first showed up there, so I went back to the last version I worked on via the ol' laptop...on the lap top, and all seems to be hunky dory. (At least thus far.)
I'm going to dig into those settings you mention on the tower and see if I can't get to the bottom of why it doesn't seem to be performing up to snuff. (It's got two 2.4 quad core xeon processors along with 24 gigs of ram, and two radeon HD 5770 1024MB graphic cards. In other words, it...should be up to snuffing.)
I appreciate your response.
I am having exactly the same issue. I returned to my project after a week or so of absence and everytime I click on a clip on the timeline the softwarre crashes with the same message:
I have a first gen Mac Pro 2.66 with 6GB RAM. I know it's getting a little elderly, but I have not had any problems with PPro since I upgraded to CC several months ago.
Any ideas anyone?
This has been fixed in our upcoming 7.1 release.
If you encounter this error please try closing the Info panel if open. This has resolved the issue for other user.