Highlighted

The Mac CS6 "Serious Error" thread

Enthusiast ,
Jun 03, 2012

Copy link to clipboard

Copied

It looks like there are 4-6 disjointed threads about some big problems Mac users are finding with CS6 (and 6.0.1)  To give us a better place to figure out solutions and for others to find with a search, maybe we can post a discussion here.

The Adobe engineers are participating and receiving crash logs, and hopefully a pattern can develop.

I'm on a MacPro 4,1, Lion 10.7.4, CS6.0.1, 32GB RAM, GTX 285 with the latest nVidia and CUDA drivers.  I am seeing 2 primary issues:

Lots of Serious Error crashes.  This happens without any noticeable pattern - sometimes with the title tool, trim monitor, or simply just scrubbing the timeline.  It seems to happen more frequently with Dynamic Links in the timeline.  Also, I believe it is happening more often (or maybe exclusively)  with the MPE GPU option enabled.  I think in Software Only mode, it may not be present, although further testing required.

Also, I am having an issue where Pr will display black only in the source and program monitors, unless I click around the timeline and will get flashes of images.  This is remedied by changing over to Software Only for the MPE.  It seems to be worse if Safari is running.

Wil - an Adobe engineer - has taken a look at my crash logs and seems to think something is funky with the graphcs drivers in both cases, but crash logs from other users seem to not agree. 

CS6 on the mac - for  me and a few others - is incredibly flaky.  If you are having issues, can you post and explain what you are seeing and what your hardware/driver config is.  Any patterns we can find will help the engineers troubleshoot and get this taken care of. 

Views

153.3K

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

The Mac CS6 "Serious Error" thread

Enthusiast ,
Jun 03, 2012

Copy link to clipboard

Copied

It looks like there are 4-6 disjointed threads about some big problems Mac users are finding with CS6 (and 6.0.1)  To give us a better place to figure out solutions and for others to find with a search, maybe we can post a discussion here.

The Adobe engineers are participating and receiving crash logs, and hopefully a pattern can develop.

I'm on a MacPro 4,1, Lion 10.7.4, CS6.0.1, 32GB RAM, GTX 285 with the latest nVidia and CUDA drivers.  I am seeing 2 primary issues:

Lots of Serious Error crashes.  This happens without any noticeable pattern - sometimes with the title tool, trim monitor, or simply just scrubbing the timeline.  It seems to happen more frequently with Dynamic Links in the timeline.  Also, I believe it is happening more often (or maybe exclusively)  with the MPE GPU option enabled.  I think in Software Only mode, it may not be present, although further testing required.

Also, I am having an issue where Pr will display black only in the source and program monitors, unless I click around the timeline and will get flashes of images.  This is remedied by changing over to Software Only for the MPE.  It seems to be worse if Safari is running.

Wil - an Adobe engineer - has taken a look at my crash logs and seems to think something is funky with the graphcs drivers in both cases, but crash logs from other users seem to not agree. 

CS6 on the mac - for  me and a few others - is incredibly flaky.  If you are having issues, can you post and explain what you are seeing and what your hardware/driver config is.  Any patterns we can find will help the engineers troubleshoot and get this taken care of. 

Views

153.3K

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Participant ,
Jun 03, 2012

Copy link to clipboard

Copied

My system is a Mac Pro 5,1, Lion 10.7.4, 32GB RAM, Quadro 4000 with the latest nvidia and CUDA drivers.  My project is entirely comprised of dynamic links with After Effects for the video and Audition for the Audio.  I converted all the video clips to AE C6 and imported them fresh. Havent done so with the audio, as it's a more complicated surgery.

My problems are four:

1) Premiere Pro CS6 is painfully slow. I installed the Quadro soon after CS6 came out to take advantage of the expanded CUDA functions. That plus PP was crawling with the ATI Radeon card that shipped with my computer. Doing anything, even nudging a clip dowm the timeline resulted in a spinning beachball. The CUDA card had a negligible effect (it might be slightly faster than the ATI but it's also less stable). Some beachballs never went away and I had to force quit. I tried clearing caches, reinstalling, doing PRAM resets, repairing permissions (even inside the terminal), opening in safe mode and all the other things people suggest. It got slightly better with the last update patch from Adobe, but only slightly. I stilll have to hold onto a clip and wait for the beachball to stop spinning to move it.

2) Premiere Pro CS6 crashes. It got to the point where I was getting "serious error" messages without doing anything. Wil is looking at my crash report.

3) Premiere Pro CS6 can't render clips that rendered without issue in PP5.5. I get compiling errors midway through. These may be related to a Video Copilot plugin effect called Twitch. I'm testing this.

4) Premiere Pro CS6 and Dynamic Link constantly lose track of my clips. The media is incredibly slow to load with lots of italicized "pendings" that last longer than five minutes. Some clips never load. Others claim to be loaded but show "Media Offline" in the project panel and timeline. I relink these one by one, which is a slow process (still can't figure out how to relink all files at once the way Final Cut and Aperture do). Sometimes relinking works and other times it knocks other things that were linked offline. Things that were rendered earlier with "Render Entire Workspce" are rarely if ever rendered the next time I open the project. Sometimes a compiling error (see (3) above) will knock all the clips offline, resulting in a sea of red tiles. This and the crashing are the worst.

All of my problems seem related to Dynamic Link. None occurred in CS5.5. I'm guessing the Dynamic Link engine was reinvented somehow in CS6 that's ill-considered, buggy, and possibly unstable.  For instance, did DL always render linked clips in CS6 in the background via the After Effects render engine?  Why does it restrict that engine to a single core when rendering via Premier Pro but use all the cores when rendering in After Effects? It must be hard to get consistency across the suite but I was hoping CS6 would clean some of this up, like that page down would advance a frame the way it does in AE or that AE would do it with the right arrow like PP. Or that the spacebar would convert the arrow to a dragging hand in PP like it does in AE.  The pieces of the suite aren't as coordinated as they could be, and Dynamic Link, on my system at least, is a disaster.

I couldn't stand Final Cut Pro X and switched to CS5.5.  It was a move I was very happy with for a long time, but CS6 has me seriously considering going back to FCP.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Engaged ,
Jun 03, 2012

Copy link to clipboard

Copied

All of my problems seem related to Dynamic Link. None occurred in CS5.5

but CS6 has me seriously considering going back to FCP.

Wouldn't it be easier to go back to CS5.5 until CS6 is fixed?

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Participant ,
Jun 03, 2012

Copy link to clipboard

Copied

tclark,  Maybe. I tried it briefly and some of the errors seemed to have transferred over.  I have enough effects work to do that I can focus on After Effects for the time being. So far AE CS6 is much less temperamental than PP CS6.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Enthusiast ,
Jun 03, 2012

Copy link to clipboard

Copied

Genefama and Jason - I may have asked before, but do you see all of these problems happening when you turn off GPU acceleration and go into software only mode?  That could help rule out some issues with the nVidia drivers or the graphics card. 

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Advisor ,
Jun 03, 2012

Copy link to clipboard

Copied

What you all seem to have in common is lots of RAM.  So, have you checked your RAM to make sure you don't have a bad stick? 

That could cause all kinds of havoc.  I had a stick go bad in a G4, and it about drove me crazy until I finally ran a RAM test.

You all have Macs, too.  Have you run Disk Warrior?  I've had problems with Pr CS5.5 that were apparently related to bad directories, because running DW fixed them, too.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Participant ,
Jun 03, 2012

Copy link to clipboard

Copied

Needles and Jim,

Good suggestions.  I'll test them first thing tomorrow.  The software-only didn't help last I tried it, but it could be a possible culprit. I'll test it too.

g

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Advocate ,
Jun 03, 2012

Copy link to clipboard

Copied

Jim -

Jim Curtis wrote:

What you all seem to have in common is lots of RAM.  So, have you checked your RAM to make sure you don't have a bad stick? 

That could cause all kinds of havoc.  I had a stick go bad in a G4, and it about drove me crazy until I finally ran a RAM test.

You all have Macs, too.  Have you run Disk Warrior?  I've had problems with Pr CS5.5 that were apparently related to bad directories, because running DW fixed them, too.

The challenge I see here is: I didn't experience any of these issues with Premiere Pro CS5.5, on the same, exact rig.  I'm fairly convinced the issue isn't memory-related or FS perms related; because issues aren't showing up in any of the other software I run.

What I haven't tried yet is to disable hardware MPE.  That'll be my next test, but I don't have high hopes...

jas

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Enthusiast ,
Jun 03, 2012

Copy link to clipboard

Copied

I agree - RAM problems would be awfully coincidental, since it seems like we weren't having this issue with 5.5.  But thank you for trying to pitch in with a solution. 

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Advocate ,
Jun 03, 2012

Copy link to clipboard

Copied

Jason Van Patten wrote:

What I haven't tried yet is to disable hardware MPE.  That'll be my next test, but I don't have high hopes...

As I somewhat expected: disabling hardware MPE made no difference whatsoever.  I was able to easily reproduce the laggy Program Monitor issue with it on and off.

For what it's worth, my source material is:

2 AVCHD inputs (one forward camera, one rear camera)

1 WAV file for sound

The video from the rear camera is PiP'd on top of the front camera, flipped horizontally, and cropped from the bottom.  The audio from both AVCHD inputs is unlinked and deleted; the audio is from the WAV file.

(If any of that matters...)

jas

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Advisor ,
Jun 03, 2012

Copy link to clipboard

Copied

I was thinking that perhaps CS6 was using memory space that CS5.5 wasn't.  I'm a watcher of Activity Monitor, and Menu Meters.  I've only used all my RAM when using Ae, doing long RAM-Previews.  It was a shot in the dark, to be honest.

You never know.  Troubleshooting is often a routine of eliminating what the problem isn't. 

I also have 32G RAM, and I'm on a Mac Pro 3,1, running 10.6.8, and I'm not having the issues you guys are.  JVP didn't list an OS, but two of you are on 10.7.4.  Coincidence?

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Advocate ,
Jun 03, 2012

Copy link to clipboard

Copied

Jim Curtis wrote:

I also have 32G RAM, and I'm on a Mac Pro 3,1, running 10.6.8, and I'm not having the issues you guys are.  JVP didn't list an OS, but two of you are on 10.7.4.  Coincidence?

It's 10.7.4 as well.  I think my issue has more to do with this thread.

jas

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Advisor ,
Jun 03, 2012

Copy link to clipboard

Copied

I don't work with AVCHD.  There's a known issue with AVCHD spanned clips.  

You could try using ProRes, DNxHD or some other intraframe codec, and see if you can eliminate your source footage or a particular codec as the issue.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Advocate ,
Jun 03, 2012

Copy link to clipboard

Copied

Jim Curtis wrote:

I don't work with AVCHD.  There's a known issue with AVCHD spanned clips.

I assume the phrase "spanned clips" means source footage that's actually more than one file?  Because my 20+ minute track videos would definitely fall into that bucket.

You could try using ProRes, DNxHD or some other intraframe codec, and see if you can eliminate your source footage or a particular codec as the issue.

Yep, I could do that.  Seems a bit wasteful (from a time and disk space perspective) to do so, but you're right...  It'd be better if the problem could be fixed.

jas

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Enthusiast ,
Jun 03, 2012

Copy link to clipboard

Copied

I upgraded to 10.7.4 and the latest nVidia drivers at the same time - so I don't know if one, both or neither are the issue here. But, it does seem to be a common factor for the people having all sorts of problems.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Participant ,
Jun 03, 2012

Copy link to clipboard

Copied

If you have 32GB installed and a bad memory stick, would clicking "About this Mac" show total memory as 24GB instead of 32GB?

By the way, if anyone reading this is running Premiere Pro CS6 on a Mac Pro with no problem, we'd love to hear from you too.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Enthusiast ,
Jun 03, 2012

Copy link to clipboard

Copied

genefama wrote:

If you have 32GB installed and a bad memory stick, would clicking "About this Mac" show total memory as 24GB instead of 32GB?

No, not necessarily.  You can use this little piece of freeware to check your memory.  If you are really curious, let it run a few times overnight.

http://www.kelleycomputing.net/rember/

Although I don't think RAM issues are causing the "Serious Problem" errors, the beachball problems you have do seem like bad RAM could be a culprit.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Participant ,
Jun 04, 2012

Copy link to clipboard

Copied

I'm guessing Apple, Adobe, and nVidia would recommend that everyone use the latest version of their own and eachother's software, correct? And if you have a recognized nVidia card you should set it to CUDA and not software only, correct?  Why are we talking about castrating our machines to run a spiffy rew update?

ps: needles, my memory checks out as fully installed, recognized, and problem-free.  Thanks for the idea though, and any others that might come to mind.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Enthusiast ,
Jun 04, 2012

Copy link to clipboard

Copied

Wil from Adobe told me that they are in the process of testing out a MacPro with the latest nVidia drivers and 10.7.4.  If they can reproduce the problem then they will have a much better chance of chasing down some answers.  Funny that we still haven't heard anyone running 10.7.4 post that they are problem free.  There must be, but if not, then it will definitely shoot to the top of the engineer's troubleshooting list.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Enthusiast ,
Jul 12, 2012

Copy link to clipboard

Copied

Arrgghh!!!   OK - so now the last Serious error has also broken my sound - with my audio muted and grayed out too.   Even iTunes won't play and is stuck at 00:00.

This is NOT a hardware problem.  I have a dual boot system and if I boot in to Snow Leopard the audio works fine.  It's broken in this installation of Lion.

I've tried running the script (located elsewhere on this site) that is supposed to restore it - and it does - once in three or four tries.   I've also tried doing all SMC resets etc and nothing works.

Thanks to who wrote this particular bug.  It's about to cost me 24 hours of restoring a full system, hopefully to find it works again but if not I'm going to be pretty peaved as I have a deadline looming.

Does anyone know what got corrupted on the HDD to cause this audio muting?   It can't be hardware otherwise Snow Leopard would be broken too.

The thing that makes it worse is that no one from Adobe is even acknowleding that these problems exist, let alone saying they are working on a fix.  Even knowing they are working on it would help..... but the silence makes me worry that they are going to leave it until CS6.5 comes along.   Come on Adobe - someone - please speak up!   You are about to lose another customer.  You may not care about one, but one turns in to two, then ten, then a hundred, a thousand and so it goes. 

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
New Here ,
Jul 12, 2012

Copy link to clipboard

Copied

I agree...I have the same audio issue, along with others   MP 10.7.4  Also tried running the Script with little joy.

So far I am sticking with rebooting, sometimes several times to get it to work. Very frustrating to say the least, but I am not getting Serious error messages, well only 1 so far.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Participant ,
Jul 12, 2012

Copy link to clipboard

Copied

The routine I posted earlier to fix the muted audio still works for me 8 times out of 10. Last time, however, the mute symbol in the menu bar stayed gray even after the audio returned.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Enthusiast ,
Jul 12, 2012

Copy link to clipboard

Copied

Well, fortunately I've managed to do a partial restore from Time Machine (just the boot drive) from last night and everything is back to normal - so this is definately a file / lion thing. 

Next time it happens I'm going to try to figure out what changed between 'now' and the last time machine backup.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Enthusiast ,
Jul 12, 2012

Copy link to clipboard

Copied

Maybe Mountain Lion will make all of our problems magically disappear....

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Advisor ,
Jul 12, 2012

Copy link to clipboard

Copied

genefama wrote:

The routine I posted earlier to fix the muted audio still works for me 8 times out of 10. Last time, however, the mute symbol in the menu bar stayed gray even after the audio returned.

I don't know if this will help with the folks that are having audio problems, but theres a utility in Digital Rebellion's Pro Maintenance Tools System Toolkit that will flush the Audio Component and Unit Caches.  Highly recommended suite of apps for Mac users.  I use the Preference Manager a LOT, since the prefs on Pr get corrupted at the drop of a hat.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Advisor ,
Jul 12, 2012

Copy link to clipboard

Copied

needles27 wrote:

Maybe Mountain Lion will make all of our problems magically disappear....

That's HILARIOUS!

I expect a whole new crop of problems, incompatibilities, crashes and lock-ups.  I won't jump until 10.8.4, most likely.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Enthusiast ,
Jul 12, 2012

Copy link to clipboard

Copied

@needles27 - Ha!  I'm not holding my breath - nor will I be an early adopter finding the 'new' problems before they are well documented either.

It took me 8 months to upgrade to Lion..... I'm not going to be doing ML unless I see lotsof people telling me all the problems are fixed and there are no new ones

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Enthusiast ,
Jul 12, 2012

Copy link to clipboard

Copied

Maybe a smiley face would have shown that I was joking. 

I want to quit editing.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Advisor ,
Jun 05, 2012

Copy link to clipboard

Copied

3) ... I get compiling errors midway through. These may be related to a Video Copilot plugin effect called Twitch. I'm testing this.

Just to add to the knowledge base, VCP has acknowledged to me that there are problems with Twitch and AeCS6.  So, it would stand to reason that it's not smooth sailing with PrCS6 either.  They're working on an update.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Advocate ,
Jun 03, 2012

Copy link to clipboard

Copied

My main issue thus far has been the lagged timeline/program monitor during playback or scrubbing.  I made a 2.5 minute clip of the issues I was seeing, but there's no audio with it.  I was going to do a voice-over with it, but I kept tripping over myself that I gave up.

Note at around 24 seconds or so: I hit the HOME key to reset the timeline, and the program monitor stays where it was.  I can even scrub a bit forward and it takes the monitor a tick or two to catch up.  Hit the HOME key again, and the monitor stays where it was.

Interestingly: when I grabbed the Mac CPU monitor and dragged it over top of the Premiere Pro window, the program monitor reset itself.  Playback and scrubbing seem to go OK for a bit until I jump ahead in the timeline (1:18 in the Youtube video).  I hit the PLAY key and it rights itself and starts playing properly.  Scrubbing seems to work well.

1:46 in the video: I hit the HOME key again, and the program monitor once again stays put.  Hitting the PLAY button resets it, but the video doesn't actually play in the monitor for a second or two, then is very choppy catching up.

Rig:

Modified Mac Pro with 2 X5690 Xeons

48G of RAM, 16 of which are in a RAM drive for scratch space

SSD for OS and apps only

1TB mirrored volume (7200RPM drives) for media

GTX570 card with nVidia's (not Apple's) latest drivers

jas

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
New Here ,
Jun 03, 2012

Copy link to clipboard

Copied

There seems to be no reason that causes the problem for me what so ever. There is nothing specific that I click on or do, moving the mouse after a little break has been the latest culprit. I have been having the problem for about a month now and it is so bad now that I cannot even open my projects for more than about 15 seconds or so without getting the "serious error". I am on CS5.5 though..so its not just a CS6 problem.

iMac 10.7.4

2.5 GHz Intel Core i5

4 GB 1333 MHz DDR3

AMD Radeon HD 6750M 512 MB

Let me know if there is any other info I could include to help.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Enthusiast ,
Jun 04, 2012

Copy link to clipboard

Copied

So, it looks like 10.7.4 is a common thread, since we are running different versions of Pr, different machines, different video cards, etc.  I would like to hear from someone (there must be many) that is running Pr with 10.7.4 without issues. 

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Advisor ,
Jun 04, 2012

Copy link to clipboard

Copied

Yes, common threads.  10.7.4 and lots of RAM.  If it turns out you get "no problems here" replies, and they're predominantly from people with less RAM, I'd suggest you pull half your RAM, and then see what happens. 

Maybe the way RAM is managed in Lion is suffering as Apple moves more towards a consumer-device OS, and away from RAM-bodacious towers, and letting that implementation fall through the cracks.  I don't know.  Just throwing that out there.

Here's another thing I learned recently:  I was having mysterious Pr CS5.5 problems.  I did all the regular maintenance and troubleshooting, re-installing... the works.  Finally, I tracked my issue down to a drive sled option I had bought from MaxUpgrades to put 6 drives in my MacPro.  I yanked the extra drives, using only the 4 stock SATA bays, and it's been smooth sailing ever since.  You can get serious errors from a bad cable; an unseated PCI card, etc.  That's how I know you have to eliminate your hardware, before you can start blaming errors on software.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Participant ,
Jun 04, 2012

Copy link to clipboard

Copied

I haven't seen any "no problem here" posts from Mac users.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
New Here ,
Jun 04, 2012

Copy link to clipboard

Copied

Just a thought, I first encountered the problem while using 10.7.2. updated to 10.7.4 last week trying to fix the problem. Not sure if that update is changed enough to make a difference..

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Explorer ,
Jul 03, 2012

Copy link to clipboard

Copied

I just finished 3 long form projects with...

PP CS 6.0.1

Invidia Quadro 4000

CUDA driver 4.2.10

MacPro 5,1

Lion 10.7.4

I edit 5 days a week 8 hours a day and push the system as fast is can go. I'm not a newbie and have built 6 editing suites for production companies. I CANNOT make this thing crash (with one exception). I imported a FCP project via XML, which went smoothly except for the fact that one audio file had a filter that for some reason would crash Premiere if I tried to copy and paste that clip to a new program. Not a big deal at all- in fact, quite understandable.

That said I do not use dynamic linking (yet) and use pretty basic graphics.

I use Canon 5d files, P2, and ProRes.

What really blew my mind and tottaly did not expect was that I could import and drop Apple Motion files right in the timeline. Crazy!

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Enthusiast ,
Jul 03, 2012

Copy link to clipboard

Copied

Run & Gunner wrote:

I just finished 3 long form projects with...

PP CS 6.0.1

Invidia Quadro 4000

CUDA driver 4.2.10

MacPro 5,1

Lion 10.7.4

I edit 5 days a week 8 hours a day and push the system as fast is can go. I'm not a newbie and have built 6 editing suites for production companies. I CANNOT make this thing crash (with one exception).

Can I have your machine, please?

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Explorer ,
Jul 03, 2012

Copy link to clipboard

Copied

I wish I had your experience with CS6..... 

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
New Here ,
Jul 04, 2012

Copy link to clipboard

Copied

I restored my system with Time machine and followed these steps and it seems to work fine until now: http://helpx.adobe.com/creative-suite/kb/cs5-cleaner-tool-installation-problems.html

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Enthusiast ,
Jul 05, 2012

Copy link to clipboard

Copied

Brand new system last week (MacBookPro), with NOTHING installed except Production Premium CS6.

4 Kernel panics in the last 20 mins.   I'm REALLY getting tired of this.

Canon MXF (XF100) single viddeo track, dual mono audio (collapsed), litterally 15 seconds long.  Ripple trim the start, ripple trim the end - panic - 4 times.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Community Beginner ,
Jun 04, 2012

Copy link to clipboard

Copied

My problem is when scrubbing through the timeline or watching my project back in premier it will jump and stutter and is so bad I cant edit anything. I'm also doing allot of dynamic links to After Effects that don't update for a very long time after I have made a change. When I take of the GPU Acceleration it seems to scrub through and preview the project fine but obviously a lot slower without the acceleration. I found I noticed the problem first after I updated my Mac Software.

MacBook Pro 15" Late 2011

2.2 GHz Intel Core i7

8 GB 1333 MHz DDR3

AMD Radeon HD 6750M 512 MB

Mac OS X Lion 10.7.4


Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Advisor ,
Jun 04, 2012

Copy link to clipboard

Copied

OK, I just updated a 10.7.4 partition, loaded up the new AJA Adobe Driver and Kona Control Panel.  I have a couple jobs this week and I think I'll give the whole schmear a shakedown.  I'll let you know what I encounter.

MacPro3,1 32G RAM, 10.7.4, CS6 PP (all updates), ATTO R680 RAID5, mostly working with ProRes, XDCam EX and HD footage.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Enthusiast ,
Jun 04, 2012

Copy link to clipboard

Copied

I'm also getting this problem on a Mac Pro with Lion, but so far not with Snow Leopard. 

What I AM seeing is that H264 exports never complete, although the file seems complete, the temp file is still there and the export sits at 100% with 00:00:00:00 left.  *really frustrating* !

The same sequence exports perfectly to DVD (on the Mac) andto H264 on Windows.  Arggh!

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Enthusiast ,
Jun 04, 2012

Copy link to clipboard

Copied

Does it make a difference if you are running MPE with hardware on/off?  Are you on 10.7.4?

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Advisor ,
Jun 05, 2012

Copy link to clipboard

Copied

Jim Curtis wrote:

OK, I just updated a 10.7.4 partition, loaded up the new AJA Adobe Driver and Kona Control Panel.  I have a couple jobs this week and I think I'll give the whole schmear a shakedown.  I'll let you know what I encounter.

MacPro3,1 32G RAM, 10.7.4, CS6 PP (all updates), ATTO R680 RAID5, mostly working with ProRes, XDCam EX and HD footage.

I worked on a spot yesterday with no issues.  Something just occured to me.  I did not update the Nvidia Quadro 4000 for Mac driver from the 10.6.8 version on my Lion test partition. 

Why don't one or all of you install that temporarily, and see if you get relief?

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Advocate ,
Jun 05, 2012

Copy link to clipboard

Copied

Jim Curtis wrote:

I worked on a spot yesterday with no issues.  Something just occured to me.  I did not update the Nvidia Quadro 4000 for Mac driver from the 10.6.8 version on my Lion test partition. 

Why don't one or all of you install that temporarily, and see if you get relief?

The driver for 10.6.8 isn't compatible with Lion; Apple included its own version of an updated driver with Lion.

nVidia also has newer drivers available for download directly from their site, for 10.6.8, 10.7.3, and 10.7.4.  The ones they ship are newer than what Apple includes with Lion.

jas

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Enthusiast ,
Jun 05, 2012

Copy link to clipboard

Copied

I will try to roll back to the last version of the nVidia driver that I was running with 10.7.2 and the GTX 285 if I can find it on my time machine. I'll report my test.

Edit:  Anyone have an idea on how to roll back the nVidia drivers?  I don't know what to remove from the extensions folder, and when I try to install an older version from nVidia, it says that I already have drivers installed and quits.  I don't want to roll back my whole system...

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Advisor ,
Jun 05, 2012

Copy link to clipboard

Copied

The driver for 10.6.8 isn't compatible with Lion; Apple included its own version of an updated driver with Lion.

nVidia also has newer drivers available for download directly from their site, for 10.6.8, 10.7.3, and 10.7.4.  The ones they ship are newer than what Apple includes with Lion.

All I can tell you is that I upgraded from a 10.6.8 partition to Lion, used Migration Assistant to move all my data over to the Lion partition, and didn't run the installer for the 10.7.4 nVidia driver.  I had heard that the GPU drivers are in the Lion OS.  I just didn't run another driver installer, such as I did for AJA, for example.

One way to uninstall an old driver is to use EasyFind to search your Lion disk for "nVidia", and just trash everything EXCEPT NVIDIA RECOVERY and NVIDIA DRIVER RESTORE, which you might need to boot afterwards.

Remember that Libraries are invisible in Lion, so a search utility is good for finding contents.  Be sure it's set to search in invisible folders.

There's an app called "NVIDIA DRIVER RESTORE" that I believe is used to remove the nvidia driver and replace it with the stock OS driver.

DO THIS AT YOUR OWN RISK, and it'd be best to consult the nVIDIA site, as I'm only working from memory here.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Enthusiast ,
Jun 05, 2012

Copy link to clipboard

Copied

I rolled back the driver to an earlier version with the "nVidia Driver Restore" (Thanks for the tip, Jim) but the problems remain.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Advisor ,
Jun 06, 2012

Copy link to clipboard

Copied

If it helps, here's what version of driver Ae says I'm running in Lion:  "2.1 NVIDIA - 7.18.18"

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Participant ,
Jun 07, 2012

Copy link to clipboard

Copied

Jim,

I reported my Twitch glitch to VCP a while ago.  They said it wasn't designed for Premiere Pro, even in a Dynamic Link.  It won't fit my worhflow if this is true so I hope you're right about a pending update.  It's a pretty cool plugin when it works.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Advisor ,
Jun 07, 2012

Copy link to clipboard

Copied

I never tried Twitch in Pr, only Ae.  I've never even noticed if it shows up in the Pr Effects tab.

It is a pretty cool plug in.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Participant ,
Jun 07, 2012

Copy link to clipboard

Copied

Sorry Jim, I was unclear. VCP said Twitch doesn't work in Premiere Pro. I told them that I don't use it there; I use it in AE comps that are dynamically-linked to a PP timeline and that AE comps with Twitch are crashing my PP renders.

I got the sense at this point that they didn't see this as a problem with the plugin. It's PP that's crashing and not AE, after all, and they don't support the plugin for PP.  I guess this leaves me to render in AE and place final (or, more likely, draft) output into the edit timeline. In other words, to pretend Dynamic Link doesn't exist.

Given my recent problems, I'm warming to the idea.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Enthusiast ,
Jun 12, 2012

Copy link to clipboard

Copied

I'd like to add my voice to this thread.

I'm running an 8 core Mac Pro (3,1) 16GB ram with a GTX285.  It's been running (almost) perfectly with Snow Leopard but for other reasons I'm needing to upgrade to Lion.   I have lion installed on a second boot drive and everything else is up and running, but I'm getting this serious error problem with Premiere Pro.

I've disabled Cuda and the problem seems to be better, though I've still had a couple of hangs.

Is there some magic combination of Lion + Nvidia drivers (285 + CUDA) that is known to be stable with CS6?  

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Enthusiast ,
Jun 12, 2012

Copy link to clipboard

Copied

Is there some magic combination of Lion + Nvidia drivers (285 + CUDA) that is known to be stable with CS6?  

Unfortunately, nothing that has been found here, yet.  I have the 285 too and I also started to see this error after upgrading to Lion and the nVidia drivers and CS6.  I tried downgrading the nVidia drivers and rolling back to CS6.0, but both did not help.  The only thing I haven't tried is rolling back the CUDA driver - starting to seem a little suspect, maybe.  Like you, I seem to have less problems with CUDA disabled.  Still trying to work on a solution.  For now, lots of saving with every few edits.

If you get a chance, can you PM me one of your crash logs? 

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Explorer ,
Jun 12, 2012

Copy link to clipboard

Copied

I'm seeing the same crashes on OSX 10.7.4, Pr 6.0.1 Cuda driver 4.1.29, GPU driver 7.18.18 270.05.25f01

I did a manual search on Nvidia's website and found an updated OSX10.7.4 driver released on May 10th

http://www.nvidia.com/object/macosx-270.00.00f06-driver.html

Also, Nvidia released a new CUDA driver today CUDA 4.2.10

http://www.nvidia.com/object/cuda-mac-driver.html

I didn't see any driver numbers listed above, only "latest Nvidia and CUDA drivers"

@needles27, can you confirm that these are the drivers your running?

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Enthusiast ,
Jun 12, 2012

Copy link to clipboard

Copied

I was running 270.00.00f06 when I had the problems initially, but then downgraded to 7.18.18 270.05.25f01 as a test with no improvement.  However, I am running Cuda 4.2.7 - thanks for the heads-up on the latest CUDA driver.  I am downloading now and will test with my fingers crossed.  Maybe this will take care of it...  Let us know if it does anything for you.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Participant ,
Jun 12, 2012

Copy link to clipboard

Copied

I installed it today and it fixed a persistent OpenGL error I was getting in my After Effects comp.  Will test it soon in Premiere Pro, but based on its performance in AE today I'd be surprised if it turned out to be a downgrade.

(I'm running Mac 5,1 with nVidia Quadro 4K by the way.)

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
New Here ,
Jun 12, 2012

Copy link to clipboard

Copied

I'll admit that I'm not totally versed and don't understand a lot of the hardware involved, but am I missing something? I don't have a CUDA enabled GPU and I'm on CS5.5 but I'm still having the same problems. Am I having the same problem as the rest of you or is it maybe something different?

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Contributor ,
Jun 12, 2012

Copy link to clipboard

Copied

Currently I'm only running CS6 Prod Pre. on a 17" MacBook Pro, 16 gig ram, (model A1297) on Lion (latest) w/OWC RAID via eSATA express 34 card. I'm only testing right now for a longer mobile editing job in a few weeks overseas. But i've ingested about an hour of AVCHD footage (Panasonic AVCCAM 1080 30p) I've had no issues except for audio not working on clips in Prelude before ingest. After ingest and also transfering over to PP CS6 with no issues with audio or crashing, timeline seems to scrub fine for AVCHD (forward smooth, but not backward). I am use the hardware mercury playback on the ATI graphic card, but have no dynamic link files. There are some color correction filters applied, but generally a simple edit.

This is a completely fresh install of Lion, CS6, etc as it is a new laptop. Generally with a new OS I like to do a complete erase and install of the OS and then install the other software. Over the years I've had less issues this way.

We have a MacPro in our primary edit suite, but we have not upgraded it yet.

Sorry I can't provide any additional help, but I hope this all gets worked out soon. All the best!

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Explorer ,
Jun 13, 2012

Copy link to clipboard

Copied

@genefama, I am very interested in your findings with the driver update, I have not installed the latest driver yet, as the driver page did not say support for 4000 for Mac, it only states 4000.

Screen Shot 2012-06-13 at 8.40.35 AM.png

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Participant ,
Jun 13, 2012

Copy link to clipboard

Copied

@RBemendo, If you open System Preferences and click the CUDA icon it tells you that there's an update available. I just accepted it because I don't like sticking with old software when there's an update available, especially when the old version is buggy. It would really irk me to have to reverse-update.

Plus, ya gotta figure Mercury Playback Engine (wotta mouthful!) is a big selling factor for the CUDA technology since it's what nVidia leads with on their website. nVidia CUDA updates must focus on working with Adobe software, particularly PP.

But like I say, Premiere Pro CS6 keeps knocking my liked comps offline, so I've been ignoring it and working in After Effects. I can try the new CUDA in PP today if you like, or run a particular routine. In my case, CUDA doesn't seem to have anything to do with PP crashing. All my problems seem like bugs in Adobe Dynamic Link (though I gotta say, so far the nVidia card hasn't been worth the $700.  I haven't noticed much speed improvement over my old Radeon card).

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Explorer ,
Jun 13, 2012

Copy link to clipboard

Copied

@genefama, I see that in my CUDA System Preferences as well, just interesting to see they don't list it on the Nvidia drivers download page.  I've cleaned my project of all dynamic links and i'm still crashing.  I guess i'll have to update drivers and hope for the best and report back.  Don't want to go too far off topic, but using the "fast draft setting" in AE with Nvidia 4000 has been a huge improvemnt for me.  As for dynamic linking files going offline and causing crashes, the only thing I can comment on is that if I had large/long render dynamic links, I'd only use them as placeholders on one track and then disable viewing for that track.  I found the more I clicked around while Premiere was generating previews from AE caused a lot of lock ups and crashes.  I haven't tried a large project, but using the "cache work area in background", has  had performance increases on small projects if you haven't tried that.  Since there is no true culprit for the "serious error" crash, perhaps you can just comment on your crashing status when your in Premiere with the latest CUDA drivers.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Contributor ,
Jun 13, 2012

Copy link to clipboard

Copied

Although we have not updated to CS6 on our MacPro (only the laptop), I know when we first ordered the nVidia 4000 I did a lot of checking to make sure I installed it correctly. In the research I discovered lots of people (Mac and PC) that had issues when they updated the drivers. I say drivers, because I was at first surprised to see that the 4000 had two. The CUDA and the card driver itself. The general info I gathered is that just because new drivers were available did not guarantee compatibility with Premiere, etc. Thankfully we never had any issues, but I'm guessing we would if this is related to the problems listed in this thread and we updated to CS6 on tha machine.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Enthusiast ,
Jun 13, 2012

Copy link to clipboard

Copied

@Glitchdod - that may or may not be true, butit's happening with the GTX285 as well., whereas with 5.5 things didn't seem to be a problem.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Contributor ,
Jun 13, 2012

Copy link to clipboard

Copied

Sorry to hear that. This seems like a real nasty issue. I wish I was at a spot to try upgrading the MacPro, but no time now for that. Plus as many of you guys are saying, maybe staying at 5.5 is best. For location work we really needed Prelude, so that's why we updated the laptop earlier than I would usually have done.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Participant ,
Jun 13, 2012

Copy link to clipboard

Copied

RBernando,

I figured that's what you meant about the nVidia website.  I guess I wouldn't read too much into it. So far the update has been more stable in my system than the previous version.

Thanks so much for the tips! They seem like great advice.  In fact, Adobe is looking at my case and mentioned that clicking around during renders can cause DL to crash. I've had problems setting it to render and going to bed for the night too, though.  I'm hoping they debug it, whatever the cause.

In the meantime, I'll try your tips. I'll also report back if the new CUDA crashes PP or causes any other mischief.

g

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Community Beginner ,
Jun 20, 2012

Copy link to clipboard

Copied

Having some "Serious Error" crashes of my own...

After using PP 5.5 for a year without any problems, then 6.0 / 6.0.1 from release until now with no problems, I am experiencing frequent "Serious Error" crashes.

I'm using a mid-2010 Macbook Pro, 2.53 Ghz Intel Core i5, Mac OS X Lion 10.7.4 (updraded from Snow Leopard when PP 6.0.1 released), 8GB RAM, NVIDIA GeForce GT 330M 256 MB with CUDA 4.2.10 installed and what I believe is the latest GPU driver installed (7.18.18 270.05.25f01)...

The crashes initially were occuring during a very specific scenario and only that scenario, but now I've had a few at more random times. The first series of crashes came during playback in a sequence with multiple audio and video tracks with different types of media (AVCHD, .WAV, .MP3). The sequence would playback fine, except for when I would make an edit to a clip, then modify the Volume of a single audio track within the second clip. Right when the playback head would pass over the edit point onto the clip with modified volume, PP would give me the "Serious Error" message, then crash.

I am unable to make heads or tails of the Crash Logs, but they seem to consistently mention the Audio Mixer / Renderer.

And today I have experienced 2 crashes not related to the above scenario, not during playback, but while I was working in a similar sequence with similar media.

I have been in contact with Adobe support, which has made me go through an extensive set of troubleshooting steps, and yet the problem persists. I have been able to recreate the above described playback crash under a diverse set of conditions... in a new project, in a different user account, in the root user account, with my media on both internal and external drives, after uninstalling and reinstalling PP, before and after updating CUDA, after removing 3rd party plugins...

Not sure what to do now...

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Advisor ,
Jun 20, 2012

Copy link to clipboard

Copied

I just had my first Serious Error.  It happened after I duplicated a Sequence.

Not sure what to do now...

I think what we do now is wait for Adobe to acknowledge they have a problem, and get to work coming up with a fix, pronto.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Enthusiast ,
Jun 20, 2012

Copy link to clipboard

Copied

Jim Curtis wrote:

I just had my first Serious Error.  It happened after I duplicated a Sequence.

Sorry to hear it Jim.  Welcome to our terrible club.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Explorer ,
Jun 21, 2012

Copy link to clipboard

Copied

@Jim Curtis, Sorry to hear as well, you were the only person I knew that was running a MacPro with CS6 not getting this error one time or another.  Now we play the waiting game. 

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Advisor ,
Jun 21, 2012

Copy link to clipboard

Copied

I was hoping not to join this club. 

I was working in Pr for about four hours yesterday.  I only got the error once, after about two hours.  Pr auto-saved the project before it terminated.  I reopened my own previously saved version, and immediately did a Save As, and incremented the file name.  Then I worked without a crash for a couple more hours.  I even duplicated a couple of more sequences, but that didn't cause the error, as it had the first time.

There seems to be no pattern for some to what causes the Serious Error, and yet, there is a pattern for others.

Curiouser and curiouser.