Adobe Community: The Mac CS6 "Serious Error" thread

Currently Being Moderated

280. Kevin Monahan,

Jul 23, 2012 9:27 AM in reply to tclark513

Report

tclark513 wrote:

Jason Van Patten wrote:

I suspect this thread is going to be locked or trimmed or something. Read this and see if you draw the same conclusion...

jas

Wow Kevin M! That is ridiculous!! It's very obvious that something is wrong here! I really suggest you read all these posts again because you don't know what you are talking about! I don't even work on a Mac and can understand why all these people are upset!

No, it's not ridiculous and I do know what I'm talking about. The post contains so many issues that it is hard to focus in on the actual problems. We need a compiled list of issues and make sure a bug report is filed for each one. Makes sense, right? BTW, I am a Mac user through and through, so I want to make sure we are addressing the actual issues.

|

Mark as:

Currently Being Moderated

281. ExactImage,

Jul 23, 2012 9:42 AM in reply to Kevin Monahan

Report

Issues that I am personally having (and know others are having).

1) Premiere Pro Crashes a Lot ! It could be for a number of reasons, but, disabling CUDA support helps a LOT. This is on both a MacPro (3,1) with a GTX 285 card AND a brand new 17" MBP with 6770 right out of the box with nothing but CS6 installed. I have since added Colorista II and Neat video, but the problem happened before they were added.

It would be helpful to us all in helping to diagnose the problem if the Serious Error dialog actually gave more information, i.e. Serious Error - CUDA, or Serious Error Audio etc. I've had projects that would crash the instant you tried to drag the CTI with CUDA enabled, but work perfectly with CUDA disabled.

2) Audio crashes. With audio tracks expanded to see the wave forms. Keep the tracks closed and it crashes less (Serious Error).

3) Audio becomes muted. After a Premiere Pro crash the system audio could become perminently muted. While this could easily be a Lion problem, it's caused by Premiere Pro crashing. Obviously if we can fix the crash it wouldn't happen, but if you can recreate it then it would be useful to try to undo what ever went wrong as you recover from it.

4) Problems where the audio would continue to play but the monitor would be black and the keyboard and mouse become unresponsive. The only way to recover it is to hard reboot.

For me, if we could get the CUDA & Audio Waveform crashes fixed, I'd be much happier.

|

Mark as:

Currently Being Moderated

282. genefama,

Jul 23, 2012 9:49 AM in reply to Kevin Monahan

Report

The three biggies seem to be

1) audio getting killed systemwide;

2) kernel panics/crashes and hanging exports; and

3) Dynamic Link bugs (After Effects clips getting unlinked from Premiere timelines etc.).

Some of us regularly experience all three.

Virtually every post is a variation on these three problems. If it seems endless, unfocused, and meandering it's because the problems haven't been addressed, much less fixed. And many of us have sent bug reports to no avail.

|

Mark as:

Currently Being Moderated

283. Strillogy,

Jul 23, 2012 9:53 AM in reply to genefama

Report

I'd be happy if the one big issue I have was at least addressed & fixed.

• I get a Kernel Panic without fail at least 2-3+ times a day now. It happens when I'm trimming video, scrubbing timeline, moving a clip, etc. All basic little edits end up killing the entire system. I wish it were just the Premiere app crashing, but it locks the entire system. I can recreate it on a 2011 & 2012 Macbook Pro (Lion), a 2011 iMac (Lion), and a 2008 MacPro (Snow Leopard).

If someone from Adobe would like to see it happen, I would be more than happy to film the entire process (since screen captures won't work when the kernel panic happens). I submit crash reports every time it happens, so there should be a nice big list under my license (assuming they store it that way?)

|

Mark as:

Currently Being Moderated

284. needles27,

Jul 23, 2012 10:03 AM in reply to Kevin Monahan

Report

1. Like others, lots of "Serious Errors." This is hard to pin down, because it happens at random times, under random circumstances, with no discernable settings, codecs, or parameters. Sometimes, it is simply opening a project and moving the playhead, sometimes while trimming. Turning the GPU acceleration off does seem to help, but not 100%. I have crash logs I can PM if that helps. (I posted one a few pages back with just the crashed thread.)

That's the only problem I have concerning this thread.

System:

MacPro 4,1

32GB RAM

GTX285 (latest drivers, latest CUDA)

Lion 10.7.4

All software updated

|

Mark as:

Currently Being Moderated

285. genefama,

Jul 23, 2012 10:07 AM in reply to ExactImage

Report

I haven't heard any conspiracy theories. I believe you that your boss didn't tell you not to post here, but if he had, that wouldn't be conspiracy. And the idea that Apple makes things rough on Adobe users has a long pedigree. We can't watch Flash videos on an iPad and it's not conspiracy—just a difference in design philosophies and business objectives.

|

Mark as:

Currently Being Moderated

286. Kevin Monahan,

Aug 3, 2012 1:12 PM in reply to ExactImage

Report

Thanks for the start of this compilation of issues Exactimage, and genefama. Add your issues and I'll add it to the list. Then we'll make sure a bug get filed for each one. Though the title of the thread is the "Serious Error" thread, it's become the "All problems related to Mac," so here are the ones I've found so far in this thread:

Premiere Pro CS6 on Mac OS (Snow Leopard, Lion, Mountain Lion) crashes sometimes with CUDA enabled on MacPro (3,1 and 4,1) and GTX 285: User reports, "It could be for a number of reasons, but, disabling CUDA support helps a LOT. This is on both a MacPro (3,1) with a GTX 285. With the Mercury Playback Engine in software mode, crashes do not regularly occur." Other user with MacPro 4,1 and GTX 285 reporting many more crashes on OS X 10.8, than in OS X 10.7. Reported "black screen" in Program Monitor, and problems with ray traced 3D rendering in After Effects. However, these problems are not evident in software mode. User reverted to OS X 10.7. Bug Filed?
Premiere Pro CS6 on Mac OS crashes sometimes with CUDA enabled on MacPro and Quadro 4000: Same reasons as above. Some report Serious Error warning without doing anything particularly taxing for the app. With the Mercury Playback Engine in software mode, crashes do not regularly occur. Bug Filed?
Premiere Pro CS6 on Mac OS (Snow Leopard, Lion, Mountain Lion) project crashes sometimes with CUDA enabled on MacPro upon reopening project after crash: Users have a problem where CUDA was enabled and Pr crashed. When ever the user would try to re-open the project it immediately crashes again before the user gets a chance to disable CUDA. The only way to recover the project is to create a NEW project with CUDA disabled, then import the old project in to the new one. Bug Filed?
Premiere Pro CS6 on Mac OS (Snow Leopard, Lion, Mountain Lion) crashes sometimes with OpenCL enabled on MacBook Pro with AMD 6770: This is with brand new 17" MBP with 6770 right out of the box with nothing but CS6 installed. Bug Filed?
Premiere Pro CS6 has slow performance and SBOD (Spinning Beachball Of Death) with CUDA enabled on MacPro and Quadro 4000: Sometimes moving and trimming clips gives slow performance, or enables the SBOD (Spinning Beachball Of Death). Bug Filed?
Serious Error Message Too Cryptic in Premiere Pro CS6: It would be helpful to us all in helping to diagnose the problem if the Serious Error dialog actually gave more information, i.e. Serious Error - CUDA, or Serious Error Audio etc. Bug filed? Yes, a bug has ben filed.
Expanding audio tracks crashes Premiere Pro CS6 on Mac OS: When audio tracks are expanded to see the wave forms. Keep the tracks closed and it crashes less (with the Serious Error warning). Bug filed?
Audio becomes muted after crash in Premiere Pro CS6 on Mac OS: After a Premiere Pro crash the system audio could become perminently muted. While this could easily be a Lion problem, it's caused by Premiere Pro crashing. A temporary fix for the issue was found by a user. Bug filed?
In Premiere Pro CS6 on Mac OS, sometimes audio continues to play with no picture, keyboard and mouse becomes unresponsive: The only way to recover it is to hard reboot. The latest update alleviates this problem somewhat. Bug filed?
Audio gets killed systemwide sometimes on Mac OS in Premiere Pro CS6: Bug filed?
Kernel panics/crashes and hanging exports on Premiere Pro CS6 with Mac OS: Bug filed?
Kernel panic when editing with Premiere Pro CS6 on iMac, MacPro and MacBook Pro on Mac OS: Kernel panic occures when trimming video, scrubbing timeline, moving a clip, etc. Bug filed?
Dynamic Link bug with Premiere Pro CS6 on Mac OS: After Effects clips getting unlinked from Premiere timelines. Dynamic link appears to "lose track" of certain clips, especially when reopening the program. Sometimes takes a long time to link all files, some just show as offline. Bug filed?
2GB file limit on AFP servers with Premiere Pro CS6 and earlier and Mac OS: There is a file size limit for video files shared on an AFP servers. This is a known issue, but please file a bug if you have this limitation. Bug filed?
Premiere Pro CS6 can't render certain files that CS5.5 and earlier could: Compiling errors sometimes occurs when rendering certain types of footage (possibly related to Video Co-Pilot plug-in, Video Co-Pilot acknowledges a problem. Problem could occur for AE comps dynamically linked into Premiere Pro). Bug filed?
Lag, or stuttering between picture and audio when playing, or scrubbing the Timeline or Program Monitor in Premiere Pro CS6 on Mac OS: When scrubbing, or placing the playhead to another place in the Timeline or Program Monitor, there is sometimes a lag in time between picture and sound. Some users having this issue have a lot of RAM. Please check to see if you have a bad stick. Bug filed?
Clicking around Timeline while Premiere Pro CS6 on Mac OS is rendering sometimes causes the app to crash: User reports on a case that is open right now. Bug filed?
After some time has passed while rendering, Premiere Pro CS6 on Mac OS can sometimes crash: User reports crash on an all-night render. Bug filed?
Adobe should release more precise documentation about the exact configurations of hardware, drivers, and software for each Mac, and Mac OS version for Premiere Pro CS6 on Mac OS: Users wish to know the ideal settings and hardware to have minimal problems. This is a known issue, and something we are working on right now. Bug filed?
Users report Premiere Pro CS6 on Mac OS crashing with certain third party plug-ins, or with drivers for hardware devices installed: After users install certain third party plug-ins, or hardware drivers, Premiere Pro CS6 crashes, or is more prone to crashing. Bug filed?
Serious Error sometimes occurs with simple editing tasks with Premiere Pro CS6 and Mac OS: Sometimes, simple editing tasks, such as, marking an In point with the I key, modifying volume, or duplicating a sequence will cause the Serious Error warning to occur. Bug filed?
System locks up sometimes occurs with simple editing tasks with Premiere Pro CS6 and Mac OS: Sometimes, simple editing tasks, such as, trimming, or moving a clip can cause the system to freeze up. A restart is necessary after this occurs. Bug filed?
Sluggish behavior with large projects in Premiere Pro CS6 and Mac OS: User reports, after media cache is created and the program is reopened, if existing media cache has not completely loaded, draging across a thumbnail in the Timeline could cause the app to crash. Bug filed?
Scrubbing footage in the Preview Monitor sometimes causes a kernel panic Premiere Pro CS6 on Mac OS: A user reports that scrubbing footage in the Preview Monitor will sometimes cause a kernel panic. Bug filed?

Jim Simon reports of a possible fix for the warning. He said, "I don't know if this will work for everybody (and I'd love to find out), but I was getting repeated Serious Errors yesterday shortly after opening an existing project. I was getting them for different reasons, like double-clicking a clip in the project tab and invoking a file>import from a keyboard shortcut. I deleted my prefs and media cache, and have able to work without errors since then. May be a coincidence. But, that seems to be a temp fix that's been working for me so far."

If your problems have not been addressed in the latest update, we apologize. Let's work together to file bugs to make sure that engineering knows about all your issues. The more bugs that are filed, the more attention an issue will likely receive. If you have filed a bug on any issue, please know that we read each and every one of them.

Users have reported that uninstalling and reinstalling the software, and/or zapping PRAM, and deleting Preferences has stopped the Serious Error warning from occurring. You may want to try these things first.

Keep in mind that employee participation is voluntary on this forum. If you don't see a response addressing your particular problem, it does not mean that we don't care or aren't fixing issues. Thanks!

|

Mark as:

Currently Being Moderated

287. Kevin Monahan,

Jul 23, 2012 10:12 AM in reply to genefama

Report

genefama wrote:

I haven't heard any conspiracy theories. I believe you that your boss didn't tell you not to post here, but if he had, that wouldn't be conspiracy. And the idea that Apple makes things rough on Adobe users has a long pedigree. We can't watch Flash videos on an iPad and it's not conspiracy—just a difference in design philosophies and business objectives.

Great thanks!

|

Mark as:

Currently Being Moderated

288. Kevin Monahan,

Jul 23, 2012 10:15 AM in reply to needles27

Report

needles27 wrote:

1. Like others, lots of "Serious Errors." This is hard to pin down, because it happens at random times, under random circumstances, with no discernable settings, codecs, or parameters. Sometimes, it is simply opening a project and moving the playhead, sometimes while trimming. Turning the GPU acceleration off does seem to help, but not 100%. I have crash logs I can PM if that helps. (I posted one a few pages back with just the crashed thread.)

That's the only problem I have concerning this thread.

System:
MacPro 4,1
32GB RAM
GTX285 (latest drivers, latest CUDA)
Lion 10.7.4
All software updated

The issues "System Error too cryptic," might be helpful to diagnose your system, please file a bug.

The issue: "Premiere Pro crashed a lot with GTX 285" should definitely be filed on an official bug report:

http://www.adobe.com/go/wish

If someone else files a bug, you should probably file one too. The more bug reports on any one issue, the more attention it is likely to get.

|

Mark as:

Currently Being Moderated

289. Kevin Monahan,

Jul 23, 2012 10:20 AM in reply to Strillogy

Report

Strillogy wrote:

I'd be happy if the one big issue I have was at least addressed & fixed.

• I get a Kernel Panic without fail at least 2-3+ times a day now. It happens when I'm trimming video, scrubbing timeline, moving a clip, etc. All basic little edits end up killing the entire system. I wish it were just the Premiere app crashing, but it locks the entire system. I can recreate it on a 2011 & 2012 Macbook Pro (Lion), a 2011 iMac (Lion), and a 2008 MacPro (Snow Leopard).

If someone from Adobe would like to see it happen, I would be more than happy to film the entire process (since screen captures won't work when the kernel panic happens). I submit crash reports every time it happens, so there should be a nice big list under my license (assuming they store it that way?)

I added your issue to the list. A bug report is different than a crash report. A bug report contains much more info. Please file a bug report for the issue: http://www.adobe.com/go/wish

|

Mark as:

Currently Being Moderated

290. RBemendo,

Jul 23, 2012 10:27 AM in reply to needles27

Report

@Kevin Monahan, I for one really appreciate your willingness to help us narrow down our issues, especially since you are a Mac user and from the sound of it not having an issues. So thank you for your participation.

@needles27, I agree, this is the biggest one for me and is the reason I have participated in this thread, thus the title of the thread.

The issues "System Error too cryptic," might be helpful to diagnose your system, please file a bug.
The issue: "Premiere Pro crashed a lot with GTX 285" should definitely be filed on an official bug report:
http://www.adobe.com/go/wish

I am getting the "Serious Error" crash inexplicitly as well with a Quadro 4000 for mac, which I will be adding in the description to my bug report.

|

Mark as:

Currently Being Moderated

291. Kevin Monahan,

Jul 23, 2012 10:31 AM in reply to RBemendo

Report

RBemendo wrote:

@Kevin Monahan, I for one really appreciate your willingness to help us narrow down our issues, especially since you are a Mac user and from the sound of it not having an issues. So thank you for your participation.

@needles27, I agree, this is the biggest one for me and is the reason I have participated in this thread, thus the title of the thread.

The issues "System Error too cryptic," might be helpful to diagnose your system, please file a bug.
The issue: "Premiere Pro crashed a lot with GTX 285" should definitely be filed on an official bug report:
http://www.adobe.com/go/wish
I am getting the "Serious Error" crash inexplicitly as well with a Quadro 4000 for mac, which I will be adding in the description to my bug report.

Not only am I a Mac user, I grew up down the street from the mothership, not far from Steve's garage! Also, I have worked there on the FCP and XSAN teams, but very happy to be here at Adobe now!

Thanks so much more submitting a bug report. I will add your issue to the list.

|

Mark as:

Currently Being Moderated

292. Kurrykid,

Jul 23, 2012 12:28 PM in reply to Kevin Monahan

Report

@ Kevin...I get a Kernel Panic whenever I try to scrub my video in the Preview window without fail. It also happens when I'm trimming video, moving a clip, etc. It locks the entire system and I get a hard error saying I have to reboot the system.

I don't have much else to report because I can't work in PPro more than a few minutes before it crashes.

MacBook Pro 15"

2.3 GHz, i7, 8GB RAM

OX 10.7.4

Dual Screen Config:

Resolution (laptop): 1680 x 1050

Resolution (Monitor): 1080p

|

Mark as:

Currently Being Moderated

293. tclark513,

Jul 23, 2012 12:35 PM in reply to Kurrykid

Report

Kurrykid wrote:

@ Kevin...I get a Kernel Panic whenever I try to scrub my video in the Preview window without fail. It also happens when I'm trimming video, moving a clip, etc. It locks the entire system and I get a hard error saying I have to reboot the system.

I don't have much else to report because I can't work in PPro more than a few minutes before it crashes.

MacBook Pro 15"
2.3 GHz, i7, 8GB RAM
OX 10.7.4
Dual Screen Config:
Resolution (laptop): 1680 x 1050
Resolution (Monitor):

Have you tried "multiple" video card driver versions to see if you have any different stability results?

|

Mark as:

Currently Being Moderated

294. Kurrykid,

Jul 23, 2012 12:36 PM in reply to tclark513

Report

No, the video card drivers are provided by the OS.

|

Mark as:

Currently Being Moderated

295. tclark513,

Jul 23, 2012 1:02 PM in reply to Kurrykid

Report

Kurrykid wrote:

No, the video card drivers are provided by the OS.

I have a suspicion that most of these problems are due to those drivers.

|

Mark as:

Currently Being Moderated

296. Kevin Monahan,

Jul 23, 2012 1:15 PM in reply to Kurrykid

Report

Kurrykid wrote:

@ Kevin...I get a Kernel Panic whenever I try to scrub my video in the Preview window without fail. It also happens when I'm trimming video, moving a clip, etc. It locks the entire system and I get a hard error saying I have to reboot the system.

I don't have much else to report because I can't work in PPro more than a few minutes before it crashes.

MacBook Pro 15"
2.3 GHz, i7, 8GB RAM
OX 10.7.4
Dual Screen Config:
Resolution (laptop): 1680 x 1050
Resolution (Monitor): 1080p

I added your issue to the list. Ensure that you've filed a bug report for this problem.

Thanks!

|

Mark as:

Currently Being Moderated

297. Kurrykid,

Jul 23, 2012 1:51 PM in reply to Kevin Monahan

Report

Thanks Kevin...bug report filed!

|

Mark as:

Currently Being Moderated

298. Kurrykid,

Jul 23, 2012 2:42 PM in reply to Kurrykid

Report

It should be noted that if I change the Mercury Playback Engine to "software Only", I do not get the crashes.

|

Mark as:

Currently Being Moderated

299. Kevin Monahan,

Jul 23, 2012 3:21 PM in reply to Kurrykid

Report

Kurrykid wrote:

It should be noted that if I change the Mercury Playback Engine to "software Only", I do not get the crashes.

Thanks, I'll add that note.

|

Mark as:

Currently Being Moderated

300. ExactImage,

Jul 23, 2012 3:59 PM in reply to Kevin Monahan

Report

Kevin,

Another one to add (and yes I'll file a report) is today I have a problem where CUDA was enabled and Pr crashed. When ever I try to re-open the project it immediately crashes again before I get chance to disable CUDA.

The only way to recover the project is to create a NEW project with CUDA disabled, then import the old project in to the new one.

|

Mark as:

Currently Being Moderated

301. Kevin Monahan,

Jul 23, 2012 4:21 PM in reply to ExactImage

Report

ExactImage wrote:

Kevin,

Another one to add (and yes I'll file a report) is today I have a problem where CUDA was enabled and Pr crashed. When ever I try to re-open the project it immediately crashes again before I get chance to disable CUDA.

The only way to recover the project is to create a NEW project with CUDA disabled, then import the old project in to the new one.

Thanks for your clarification and bug report!

|

Mark as:

Currently Being Moderated

302. dv416,

Jul 23, 2012 4:28 PM in reply to Kevin Monahan

Report

Well this is new...

Just got a kernal panic that ALSO managed to corrupt the project file.

Yikes.

|

Mark as:

Currently Being Moderated

303. Jim Curtis,

Jul 23, 2012 4:31 PM in reply to dv416

Report

dv416 wrote:

Well this is new...

Just got a kernal panic that ALSO managed to corrupt the project file.
Yikes.

Are you folks who are getting Kernel Panics running Disk Warrior afterwards?

|

Mark as:

Currently Being Moderated

304. Kevin Monahan,

Jul 23, 2012 9:20 PM in reply to Jim Curtis

Report

Jim Curtis wrote:

dv416 wrote:

Well this is new...

Just got a kernal panic that ALSO managed to corrupt the project file.
Yikes.

Are you folks who are getting Kernel Panics running Disk Warrior afterwards?

Sorry that happened. Could you please file a bug report? http://www.adobe.com/go/wish

Thanks in advance.

|

Mark as:

Currently Being Moderated

305. needles27,

Jul 24, 2012 1:49 PM in reply to ExactImage

Report

Good to see we are getting some organization. The more I have problems, the more it seems that it is (for me) a CUDA problem. In the crash logs, I am mostly seeing CUDA or GPU being referenced.

|

Mark as:

Currently Being Moderated

306. Kevin Monahan,

Jul 24, 2012 4:36 PM in reply to needles27

Report

Yes, I think the disorganization is what derailed the thread. Engineers are appreciating the thread too. We are making sure that we have bugs logged for each of these issues. We are having a hard time reproducing some of these bugs. I'll let you guys know which ones, so we can find a reproducible case. A reproducible bug is crucial to find a solid fix for it. Keep those bug reports (with reproducible cases) coming in. A "sometimes" reproducible bug is also really helpful.

Thanks guys, we're getting some good traction on this now. Keep 'em coming and I'll keep the list up to date.

|

Mark as:

Currently Being Moderated

307. tclark513,

Jul 24, 2012 6:21 PM in reply to Kevin Monahan

Report

I recommend people with issues should send their "problem" projects to Adobe to test.

|

Mark as:

Currently Being Moderated

308. ExactImage,

Jul 25, 2012 1:58 AM in reply to tclark513

Report

Great idea. Now how long will an 800GB project take over the web ?

|

Mark as:

Currently Being Moderated

309. needles27,

Jul 25, 2012 3:41 PM in reply to ExactImage

Report

I noticed that along with Mountain Lion update today (which is being recommended by Adobe, by the way) there is also a new CUDA driver. I have so much hope that this will solve the problems, and not cause too many others. After I clone my HD, I am going to make the plunge and try it out. I don't have much to lose.

|

Mark as:

Currently Being Moderated

310. ExactImage,

Jul 25, 2012 3:49 PM in reply to needles27

Report

I hope so too. I have a full time machine backup which I will keep ready if I need it, and now I'm waiting for my free update codes from Apple for a qualifying machine. Once that arrives I will certainly install it and see how it goes..... but for now ML is going nowhere near my production systems!

It's good to hear that Adobe think it's going to be more stable, but I'll be sad if 'you need to upgrade to ML' turns out to be the only solution to the problems because when ever I update the O/S 'something' breaks, like a driver for a peripheral etc. We'll see.

|

Mark as:

Currently Being Moderated

311. Jim Curtis,

Jul 25, 2012 3:54 PM in reply to ExactImage

Report

The only concern I have is that Adobe is saying that going to ML addresses issues with Open CL. So, for nVidia / Quadro 4000 users, it may not be the panacea we were hoping for.

Please let us know how it works!

|

Mark as:

Currently Being Moderated

312. tclark513,

Jul 30, 2012 5:52 AM in reply to Jim Curtis

Report

http://forums.adobe.com/message/4586892?tstart=0#4586892

|

Mark as:

Currently Being Moderated

313. Jim Curtis,

Jul 30, 2012 9:36 AM in reply to tclark513

Report

tclark513 wrote:

http://forums.adobe.com/message/4586892?tstart=0#4586892

Don't get your hopes up. I backpedaled on my initial optimism, after getting a Serious Error in Mountain Lion, and discovering some real problems with Ae and Pr as well. Back to Lion, in the meantime.

|

Mark as:

Currently Being Moderated

314. Kevin Monahan,

Jul 30, 2012 12:31 PM in reply to Jim Curtis

Report

Jim Curtis wrote:

tclark513 wrote:

http://forums.adobe.com/message/4586892?tstart=0#4586892

Don't get your hopes up. I backpedaled on my initial optimism, after getting a Serious Error in Mountain Lion, and discovering some real problems with Ae and Pr as well. Back to Lion, in the meantime.

I added OS X Mountain Lion to the list of OS X software giving the Serious Error warning.

For others that are having trouble with Premiere Pro on Mountain Lion, please file a bug report:
http://www.adobe.com/go/wish

|

Mark as:

Currently Being Moderated

315. Lewiz,

Jul 31, 2012 3:02 AM in reply to Kevin Monahan

Report

Amazing how this thread kept growing, reaching over 22.000 views and still counting. I can understand the frustration of both users and the Adobe engineers confronted with this chaotic list of both significant and non-significant error experiences, seemingly caused by different 'triggers' everytime and sometimes even more randomly than expected. To toss up a dirty word, I am a PC user, but remarkably enough my system contains a Quadro 4000 card which I suspect to play an important role in all of this.

Because no matter what cause: displaying waveforms in the timeline, scrubbing, dragging video, doubleclicking footage to open in the source windows etc. etc. all comes down somehow to the Great Mercury Playback Engine (addressing CUDA) which was very obviously rewritten between the versions 5.5 and 6, probably to solve a couple of older bugs or to please some graphic card manufacturer.

Too bad the new MPE screwed up for, at least, the NVidia drivers.

The proof is found simply enough: switch the MPE to "software only", disabling CUDA and in some systems the external preview monitor, and you will see NO ERRORS at all - this, in case of a PC. But something tells me that at least in this case Apple and PC have something in common.

My suggestion: revise the MPE by comparison with the 5.5 version and most problems will be solved ! As I tried to get under the attention before a long time ago, on this forum.

|

Mark as:

Currently Being Moderated

316. Jim Curtis,

Jul 31, 2012 6:52 AM in reply to Lewiz

Report

Here's what I think. In a moment of either abject stupidity or freakin' genius, I'm not sure which, Adobe decided to have any and all bugs or errors produce a generic "Serious Error" screen. Anybody who's spent time with Avid products is no doubt familiar with the "Flamethrower" and other colorfully named, yet specifically targeted error messages. At least the Avid engineers and users have a clue or a direction to track down an issue. Meanwhile, back at Adobe, their single all-purpose error message gives customers no indication whatsoever what caused the crash. Any and all crash triggers end with that screen.

While I don't have an argument with your general direction (MPE as the culprit), Lewiz, I do want to remind you that the Serious Error has struck 5.5 and 6 users on 10.6, 10.7 and 10.8 of the Mac OS, and also ATI and nVidia victims, IINM.

If you look at Kevin's compilation of error triggers on post 286, it appears that there isn't one bug causing this, it's lot's of them. Some are brought on by specfic actions and are repeatable; others are random and might occur once, and never again. The crash logs that have been posted seem to share no common thread. It's possible that the crashes are due to issues with the OS, the app, the GPU and video io card drivers.

[ BTW, a few posts back, I wrote "discovering some real problems with Ae and Pr as well." I meant Ps, not Pr. Actually, Pr felt pretty good under Mountain Lion. It's the fact that Ae and Ps aren't that I switched back to Lion. I use Ae as much as I use Pr.]

|

Mark as:

Currently Being Moderated

317. needles27,

Jul 31, 2012 11:16 AM in reply to Jim Curtis

Report

Just another data point - I installed Mountain Lion and gave it a shot. My experience was I encountered many more "serious errors" than on Lion. In fact, it was much worse - getting the "tightykilt" error, Ae was saying I needed CUDA 4.0 or later in order to load (I have the latest CUDA 5.0.17) Ae was getting stuck on "Ray Trace Engine" loading, Pr would only show black in the program monitor, etc, etc. All of this is related to CUDA, since I could run in software only mode with more luck.

I had hope. Back to 10.7.4.

Again, I am running MacPro 4,1 with the GTX 285.

|

Mark as:

Currently Being Moderated

318. Kevin Monahan,

Aug 3, 2012 10:52 AM in reply to Lewiz

Report

Lewiz wrote:

Amazing how this thread kept growing, reaching over 22.000 views and still counting. I can understand the frustration of both users and the Adobe engineers confronted with this chaotic list of both significant and non-significant error experiences, seemingly caused by different 'triggers' everytime and sometimes even more randomly than expected. To toss up a dirty word, I am a PC user, but remarkably enough my system contains a Quadro 4000 card which I suspect to play an important role in all of this.
Because no matter what cause: displaying waveforms in the timeline, scrubbing, dragging video, doubleclicking footage to open in the source windows etc. etc. all comes down somehow to the Great Mercury Playback Engine (addressing CUDA) which was very obviously rewritten between the versions 5.5 and 6, probably to solve a couple of older bugs or to please some graphic card manufacturer.
Too bad the new MPE screwed up for, at least, the NVidia drivers.
The proof is found simply enough: switch the MPE to "software only", disabling CUDA and in some systems the external preview monitor, and you will see NO ERRORS at all - this, in case of a PC. But something tells me that at least in this case Apple and PC have something in common.

My suggestion: revise the MPE by comparison with the 5.5 version and most problems will be solved ! As I tried to get under the attention before a long time ago, on this forum.

We're hard at work on fixes, I'm sorry your're having trouble. Thanks also for your feedback. Please file a bug report for your issues: http://www.adobe.com/go/wish We read each and every report.

|

Mark as:

Currently Being Moderated

319. Kevin Monahan,

Aug 3, 2012 12:10 PM in reply to Jim Curtis

Report

Jim Curtis wrote:

Here's what I think. In a moment of either abject stupidity or freakin' genius, I'm not sure which, Adobe decided to have any and all bugs or errors produce a generic "Serious Error" screen. Anybody who's spent time with Avid products is no doubt familiar with the "Flamethrower" and other colorfully named, yet specifically targeted error messages. At least the Avid engineers and users have a clue or a direction to track down an issue. Meanwhile, back at Adobe, their single all-purpose error message gives customers no indication whatsoever what caused the crash. Any and all crash triggers end with that screen.

While I don't have an argument with your general direction (MPE as the culprit), Lewiz, I do want to remind you that the Serious Error has struck 5.5 and 6 users on 10.6, 10.7 and 10.8 of the Mac OS, and also ATI and nVidia victims, IINM.

If you look at Kevin's compilation of error triggers on post 286, it appears that there isn't one bug causing this, it's lot's of them. Some are brought on by specfic actions and are repeatable; others are random and might occur once, and never again. The crash logs that have been posted seem to share no common thread. It's possible that the crashes are due to issues with the OS, the app, the GPU and video io card drivers.

[ BTW, a few posts back, I wrote "discovering some real problems with Ae and Pr as well." I meant Ps, not Pr. Actually, Pr felt pretty good under Mountain Lion. It's the fact that Ae and Ps aren't that I switched back to Lion. I use Ae as much as I use Pr.]

Hi Jim,

Thanks for your feedback. We know that the error message is not specific enough. We are working on that issue, and the underlying causes of Mac related problems. The compilation has highlighted issues for the team. As I have said, repeatable bugs are the most valuable ones, but I encourage people to submit report "sometimes" or "once" bugs.

|

Mark as:

Premiere Pro

More Like This

Incoming Links

Bookmarked By (6)

Answers + Points = Status

Premiere Pro

The Mac CS6 "Serious Error" thread

Jun 3, 2012 9:12 AM

More Like This

Incoming Links

Bookmarked By (6)

Answers + Points = Status