toughpug wrote: Adobe, this is a call from many, many editors who need assitance please. A solution is would be much appreciated. A solution to what? The Serious Error warning? Random crashing with MPE enabled? This thread has multiple issues related to Mac OS. I compiled the issues some days ago, so we are aware of everything people are wanting fixes for. As I have said, we know about the many issues on this thread, and are working hard on fixes. Unfortunately, some of these are difficult fixes and/or are hard to reproduce. In the mean time, please file a bug report: http://www.adobe.com/go/wish Unless you file a bug report, there is not much more I can do for your specific issue. Thanks. ... View more

Hi Cr3ating, Sorry you are having trouble. We are working hard on issues related to the "Serious Error" warning on Mac OS.  Our staff is aware of the issues, rest assured. As Ben said, it's best not to post crash logs to the forum. If you must, limit it to the first 50 lines, or so, as that is the part usually looked at by engineers. It is really an inconvenience for other users trying to troubleshoot a problem. To submit a bug report or feature request, do so here: http://www.adobe.com/go/wish Thanks a lot. ... View more

Thanks for your report KGCW, I'll look into it. It would be great if you could submit a bug report: http://www.adobe.com/go/wish ... View more

Guys, I told you that the team knows about the issue. Nothing we can do about it unless you submit a feature request: http://www.adobe.com/go/wish Yesterday, I cut a simple multicam sequence and pressed the 0 key before the Space bar to pause playback. Seriously, it didn't take me long to get used to that. By all means, please try it. It's definitely the way to pause playback without introducing a cut. Until the interface is changed, we are going to have to live with it working this way. I'm going to look into why it won't work on certain combinations of Premiere Pro and Mac computers. ... View more

Bill, Sorry, I can't file a new bug as the team already knows about the issue. At least you now know they are aware of the problem. Have you tried the workaround? Tap the 0 key and then hit the Space Bar. I think this works OK for what you wish to do. ... View more

DMH79 wrote: That seems like a very honest and revealing statement about the disconnect of this product and its users if there is no middle men to relay the issues. I'm the middle man. I relay the top issues to the team. I write bugs that have repeatable behavior. The engineers writing code do not usually have time to check out the forums, that's why I'm here. Sometimes we get the quality engineers to participate, but the content lead (me) and tech support folks are the ones on the forums most. DMH79 wrote: So just being nice about it doesn't seem to get anything accomplished. Granted, I'm glad you all are nice (thank you for that), but man, I hope you figure out a way to bridge that "gap" between those that address the users and those that fix the issues. The idea of it being added to some sort of abstract wish list is a joke. Before I got into the software biz, I was an editor just like you. Back then, I found it hard to understand why fixes couldn't be made more quickly by companies like Apple or Avid. For example, some things about FCP never "got fixed" through seven full versions, and will forever remain broken, despite me being very vocal about those problems in forums like this. I found that an enhancement like the one you're requesting, might break several other things, or might require a full rewrite of the code for that interface. There are also priorities based on user feedback. We, as editors, can't know about these difficulties, but should be aware of them. Creating software is complex and time consuming. To change an interface feature, like the multicamera monitor, might take more than a few versions to satisfy editors. The "wishlist" is not a joke. In fact, we read and consider every single feature request. Please don't think we don't care because a certain feature has not been changed according to your needs. DMH79 wrote: Well, I hope that changes quickly. One day you'll google search "Premiere Pro Multicam" and this post will pop up first and I'm guessing it would be a bad way to introduce people to the program if it doesn't have a big green SOLVED on the top. Trust me, like I said before, I'll be the first one to come in here and put it up there. In the mean time, tap the 0 key before you hit the Space bar to pause playback. That should work for you while you wait for changes to the software. ... View more

KGCW wrote: zuccon123 wrote: I hate this issue too. It needs a fix soon. In any case there's a workaround. Before to stop the playback press the key 0 (zero) of the keyboard and then you can stop the play without the cut in the timeline. Ivan It used to work for me too but moving to OSX Lion or PP 6.0.2 (can't tell exactly wich one is responsible) have killed this workaround, now stop record create an edit when pressed too. Really? That's no good. It's working on my Mac running Snow Leopard. I'll try to find out what's going on. ... View more

DMH79 wrote: Regarding the "numbers" reference...I know full well that making the wish request is the best way to get things done. I've done that. So have others as you see in the first thread on this topic. But, I also know that these topics are one of the first things that are referenced when people search online about different programs. Using a title that catches attention of other people will encourage more people to respond and send forth their "feature requests" as you mentioned. I also know that the first thing Adobe doesn't want when people google "Premiere Pro Multicam" is to see a post at the top that it's broken. If I saw this thread two months ago when I started I might have gone to FCPX first and never come back. So hopefully that motivates the change to happen sooner than later. So sorry that this is such a dealbreaker for you and others on this thread. I wish I could snap my fingers and make the fix for you, but I can't. However, I'll do my best for you regarding pointing more attention to this issue. If there are others on the thread that have not filed a bug, please do so right now: http://www.adobe.com/go/wish Thanks. ... View more

Premiere Pro CS6 (and CS5, and CS5.5) has serious issues/problems with the multicam feature that is broken as of right now (version 6.0.2) in Premiere CS6 and makes editing multicam a VERY frustrating experience and much less efficient compared to other NLE's. If its a design, then its flawed as yes, you can get around it and fix what you've done, but why should you have to keep wasting valuble time "fixing" things like this anyway? Just doesn't make sense. This is exactly the way I edited multicam in FCP and Avid, I live switched the multicam edit and then went back with the roll tool. It's not broken, it just doesn't work the way you want it to. File a feature request to request a change in behavior: http://www.adobe.com/go/wish DMH79 wrote: This issue has been known by Adobe for over two years but they push it aside, call it a design quirk, and ultimately avoid fixing the issue as noted in this thread: http://forums.adobe.com/thread/738084?start=0&tstart=0 We never called it a quirk. One of our moderators did. We made lots of updates to multicamera editing in CS6, unfortunately, not the ones you wanted. Keep making feature requests if you wish to see it operate differently. DMH79 wrote: 1) Start a thread with as many keywords as possible so that this issue gets "the numbers" both in this forum and in Google searches. Hopefully soon when you google "Premiere Pro multicam" this will be the first topic on the first page. My hope is that I can put a nice "SOLVED" or "FIXED" label on this thread one day soon (and I will for sure!). If that's the case, its a testament to the squeeky wheel theory combined with a little web analytics. 2) Make this a new thread rather than continue in the old thread because it's time to ask a new question: how long will it take for Adobe to fix an issue when its design is essentially broken causing all users to have to do a "fix" every time? Right now it's going on two years! This isn't a feature request...its a broken function within Premiere. A design...flaw. I do know Adobe listens and that they care about certain things, but how fast do they act? That's my real question. Please, do respond...we apparently need the numbers. The "numbers" refer to feature requests, not amount of threads, keywords, Google searches, or whatever. We count feature requests from this form only: http://www.adobe.com/go/wish No need to create new threads, or take other actions. Thanks. ... View more

Sorry about that. Please create a bug report, so we can work on a fix: http://www.adobe.com/go/wish ... View more

ExactImage wrote: Kevin, Thanks for the feedback. I do undertand the time it takes fix software - and the importance of getting repeatable steps - I was a software engineer for 20 years, and certianly liked the feedback I got from beta testers.  I trust you know that there are a few additional people here willing to beta test your fixes prior to releasing it out in to the wild again Sure. As a former software guy, thanks for understanding our position. I know how frustrating waiting for a fix is. Our beta program is only open prior to ship, so we'll have a new one opening soon for our next version. Don't worry, our engineers are going to test the heck out of this one. ... View more

genefama wrote: bossy, Not true, some progress was made.  We were accused of being whiners and conspiracy theorists!  ;-O Never said anything about whiners, but those conspiracy theorists...tsk tsk! ... View more

genefama wrote: Adobe admitted they were ignoring us and would keep doing so until we re-listed every complaint that we had already spent weeks listing in exhaustive detail--as if we were starting from scratch. Now you say quit complaining. Me, I just want to not have to re-link and re-render the same media everyday. We aren't ignoring you. We are on the forums every day trying to help. Not sure what you're talking about there. I was the one who re-compiled the list of complaints (many of them not related to the OP's problem of "Serious Error", by the way) because the thread became so unruly, our staff was having a hard time following it. If you are having trouble with relinking and rendering media, please create a separate post so we can work on that problem on its own. Thanks! ... View more

bossy22 wrote: I am really speechless, that a) This hasn't been discovered during development. I mean, do they test the stuff they program?? This is happening to so  many people and there aren't that many configs on the mac platform. Not like windows and thats rock solid. b) That they haven't figured anythingout yet.. The thread started in June, right?? unbelieveable... bossy22, a) Yes, we do test the program extensively. We had a beta program running for months before ship and bugs like this didn't appear. Yes, we had Mac users in the program. We also have internal QE, and other departments doing testing. When the app gets out in the wild, though, people have different installed software, configurations, and parts, so things can go awry. b) As I remarked to ExactImage, software bug fixes are extremely hard to fix without repeatable steps. Fixing deeply rooted problems can't always be fixed quickly. As an editor, it is hard to understand why it takes a long time to make software bug fixes. Trust me, I've been there. It's definitely not an easy task. Thanks! ... View more

Seastage wrote: Just submitted my REPEATABLE crash to Adobe.  Can someone else try to emulate this crash on their mac?  If so please submit your results to Adobe as well (bug submission form:  http://www.adobe.com/go/wish) Thanks so much for your submission. ... View more

ExactImage wrote: C'mon Adobe, let's have a fix, or at least some indication that you are working on it and it 'will' be fixed in a 6.0.x update and not a 6.5.x release.  If it's not fixed in a 6.0.x update you will lose me (and I suspect many others) as a customer.  Period.  End of story. So, what's the score? ExactImage, I've told you before that we know about many of these issues and are working on them right now. If a bug is repeatable, we can try for a fix, but if it is not repeatable, it is much more difficult. When it comes to making software fixes, it takes time. This is really frustrating for users who need fixes right away. As an editor, I used to feel exactly the same way. Hang in there. ... View more

We are continuing to attack the bugs brought up on this thread. I was just speaking with engineering this morning, they want to make sure we have bugs filed for every issue. Please make sure you file a bug report, if you have repeatable steps, even better. Random crashes are harder to pin down, but still file a bug if it happens to you. File it here: http://www.adobe.com/go/wish ... View more

Make sure you've updated Premiere Pro CS6. Links to other updates are on this blog. You can also go to Help > Updates to get version 6.0.1 ... View more

Jim Curtis wrote: Kevin Monahan wrote: 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. Kevin, thank you for your continued presence on this forum and this thread.  It is reassuring to hear that you and Adobe are aware of the issues and working on them.   I think we all look forward to the day when you or we collectively can pinpoint a culprit or a solution, and we can mark this topic "solved." BTW, 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. Sure, Jim. I'm working with engineering right now to make sure we have bugs filed for these issues. I'll let the group know which ones do not have a repeatable case. The day we can solve a lion's share of these issues will be a good one. BTW, I'll add your tip about deleting prefs and media cache files to the compilation post. ... View more

needles27 wrote: 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. I'll add your findings to the compilation. If you haven't filed a bug report yet about Mountain Lion, can you please do that? Thanks. ... View more

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. ... View more

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. ... View more

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 ... View more

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. ... View more

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. ... View more

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! ... View more