I’m a very happy and satisfied Adobe Creative Cloud user. There’s no way I would have been able to use the suite without the monthly option given the budget I have right now. But there is a major problem Premiere Pro CS6 has in causing repeated kernel crashes on my MacBook Pro purchased in March 2012 and after about eight calls with even up to Tier 2 tech support, many hours of memory checks on my MBP, etc. I’m still having serious issues with PR working when it comes to using Photoshop .png elements in my videos and on export.
To their credit, Adobe’s Twitter representatives, particularly @AdobePremiere have been immediate and quite amazing. For the past three weeks I’ve had Mr. Abhishek Kapoor from Tier 2 tech support calling me on an-every-couple-of days-basis to ask if I’ve had more problems. His last diagnosis of why I was having issues was because I’d not ingested a series of videos via Adobe’s Prelude and Adobe’s Encoder and imported the metadata from my Canon HD video camera.
Dr. Barb MacLeod And Tortuguero Monument 6 Dramatic Reading
So with video shot Tuesday in Austin, Texas of Dr. Barb MacLeod, one of the leading Mayan epigraphers in the world, explaining the text of Tortuguero Monument 6, an Ancient Mayan glyph that talks about what’s expected to happen on Dec. 21, 2012, I went through the process of using Prelude and then converting the video to a .mov in Encoder.
Everything worked fine. And in all, I did five ingest sessions of clips and have produced nine spectacular new videos to go in Dr. Mark Van Stone’s upcoming 2012: Science & Prophecy of the Ancient Maya iBook–set to be sent to Apple for approval almost as soon as this new clip is done.
But to do this last video, I’ve made .png files of every glyph on the major panels of Tortuguero Monument 6 and then pulled them into Premier Pro CS6. That worked fine the first day. And since there are eight columns of 17 glyphs and four columns of five glyphs each, that means there are 156 .pngs rotating in and out of the clip as Dr. MacLeod reads the most current interpretations of this historical monument, it took some time to do–Like an entire day.
The clips then had to be placed in PR CS6 in the right order, glyph E-1 then F1, then E-2, F-2 all the way down and across two-by-two.
Then yesterday, I added an establishment piece on the back that showed the entire monument, with the famous right piece off to the side.
And then all hell broke loose. I had FOUR kernel crashes yesterday. That means my Mac died and the only thing I could do to it was reboot. Each time I kept going.
Today, I just deleted the background files that were added yesterday and decided I’d try to build in a crawl of the interpretive text underneath before adding the file that seemed to start the conflict.
And as soon as I began to try to play the crawl, kernel crash 1 of the day happened.
Kernel Crash Reports
I’ve also taken to putting Easter Egg messages in the kernel crash reports that are getting sent somewhere every time my machine crashes. I’ve offered a reward to someone to actually contact me from reading them, but alas, that’s yet to happen.
And what good does it do for tech support to not be able to comprehend them? For the five crashes I’ve now had in the past 24 hours, they all say that the crash happened at “Faulting CPU: 0x2.” Seems to me that should mean something to someone. Reports before have said Faulting CPU: 0x4 and Faulting CPU: 0x6, so there’s definitely something different about these crashes than the other ones. Right?!?!
I’m getting very angry about this. I’ve been more than patient, but this incessant crashing is costing me time and has caused delays in production of our product for our client.
I have Final Cut Express on my machine, but have purposely switched over to Premier Pro to do the massive, high-quality work the 2012 iBook project is demanding.
Adobe repeatedly has checked my machine and found there to be nothing wrong with it. The CPU is working. And Tech Support’s Kapoor has run a five-hour mem test on my machine to determine there’s nothing wrong with the RAM.
That leads to one of two conclusions: 1) Adobe Premiere Pro has a bug in it, or 2) Adobe Premiere Pro isn’t capable of handling video when .png graphic files also are included in it–ones made by Adobe’s Photoshop CS6.
Like I have said, I’m a very satisfied and happy Creative Cloud customer. I’m posting this because I’m asking for/seeking help and trying to raise awareness to this issue. I’d call tech support right now and ask for help, I’d even send Abhishek Kapoor an email asking for more help, but it’s Saturday now, and apparently creativity is supposed to come to a halt on the weekends? I don’t know. But I wish tech support had weekend hours, but not as much as I wish Adobe would fix the problem here….