I am relatively new to Premiere Pro CS6 (gradually switching from Final Cut), so forgive me if there's any details I'm missing. I'm having real issues with getting the application to work, unfortunately.
Here's the problem:
I can create and save projects just fine. Nothing is slow or appears wrong. However, every time I want to import clips (in any project/sequence setting or codec, as well as different types of camera clips), Premiere Pro instanty throws up a message - without a delay - to say:
"Sorry, a serious error has occured that requires Adobe Premiere Pro to shut down. We will attempt to save your current project."
There is literally no way around this, as far as I can tell. I've attempted all different types of clips, all different methods of importing (e.g. drag and drop, Media Browser, File > Import), but nothing. It's not even a movie issue - the same applies even if I just try import images. Amusingly, with the grag and drop method - if it's a video clip, PP even registers how long the clip is, highlighting where the clip will insert - as it normally would - but then instantly crash upon dropping and/or trying to play back. This has lead me to believe (because I haven't ever seen a single frame of visuals in Premiere Pro) that there could be some graphics bug – potentially something wrong with my system.
Any support or suggestions would be greatfully recieved. I've attached the crash report below, and a few specs of my system.
MacBook Pro 15" (Retina Display) - Mid 2012
2.6GHz Intel Core i7
8GB 1600 MHz DDR3 RAM
OS X 10.8.2 (12C60)
Intel HD Graphics 4000 512 MB
Premiere Pro Version 6.0.2 (072 (MC: 264587))
P.S. Just gunna do a full update of my OS X to bring it up to 10.8.3. I doubt this will fix the problem, but it's worth a shot, and if iit does I'll let you all know.
Hi everyone, just to update:
I seem to have fixed the issue!
No idea what it was, but it would either have been:
a) rebooting my MacBook (unlikely!)
b) updating the Apple firmware
c) updating the Apple Retina Display update
d) ....all of the above!
It actually started working before going onto 10.8.3, so not related to OS X.
In which case, apologies for the lengthy post - hope it helps anyone in the same situation in the future. Moral of the story: update the Apple software!