| I'm on Mac. Prior to CC, my experience was that Pr was prone to corrupt its prefs and its own render files. My bane was the "Serious Error," not the one you reported.
I had a scatter gun approach to getting back to work that included refreshing the prefs, deleting renders and caches. That worked for a while, until the problems started recurring. But, then it was repeat the same procedure at every crash.
I also probably reinstalled the app 20 times. And to make things even more fun, Pr has an outright allergy to corrupt footage items. CS6 was a big improvement over 5.5, and the CC version has been nearly trouble-free by comparison.
And to be complete, I've also had hiccups that reinstalls of the GPU, CUDA and io card (AJA) drivers cleared up.
Another troubleshooting tip is to create a new project and try to import the same footage. If it imports OK, you may have a corrupt project. If it doesn't, the footage or codec may be the culprit.
Thanks Casey,
I realize everyone likes to get tons of info, was just looking to see if anyone has experienced this type of sudden change. The reason I didn't include all the codec info, etc is because it's been business as usual, then suddenly it stops importing correctly which is why I doubt it is any format or codec issue.
However - I'm using premiere pro version 6.0.5 and updated yesterday after experiencing issues but no change. I work on a PC, Windows 8.1. My routine has been pretty simple. I've been working in AE 6, outputting files to DNxHD, importing in to premiere and normally no problem. It may also import a file that didn't work on a second try or after restarting premiere.
In my mind, clearly a premiere issue. I did also do some conversions to ProRes using CINEC, also a standard procedure and it's had same symptoms with both before and after.
Eric
|