Skip navigation

The Mac CS6 "Serious Error" thread

Jun 3, 2012 9:12 AM

  Latest reply: deepansh1989, Oct 18, 2013 9:03 AM
Branched to a new discussion.
Replies 1 ... 5 6 7 8 9 ... 14 Previous Next
  • Currently Being Moderated
    Jul 18, 2012 7:46 AM   in reply to Strillogy

    Just another note......After having audio muting issues, as discussed in this forum, I uninstalled CS6 a while ago on my Macbook Pro. Audio issues seemed to have subsided. I recently reinstalled CS6 just for the heck of it and started recieving audio muting problems again, but no serious crashes. I uninstalled CS6 and for a while now have been still having audio issues. So, I read Jim Curtis note about this:  

     

    You're probably risking more problems by installing nVidia drivers.  This is a guess on my part, because I didn't install any nVidia drivers, and I'm not plagued by Serious Errors as some of you are.

     

    Then I deleted my nVidea Cuda Preference Pane in System Preferences, reinstalled CS5.5 and have been running audio problem free for some time. I know this thread is getting very long and frustrating, I too want to use PrP CS6 in a professional manner, but do not have the confidence yet to have clients sitting behind me while I explain why there are so many issues with a new piece of software, as my deadlines creep up. None of us can be hadcuffed by the tools we use on a daily basis. PrP CS6 is like driving my first car .....fingers crossed and hope I make it to my next destination, every time I hop behind the steering wheel.

     


     
    |
    Mark as:
  • Currently Being Moderated
    Jul 18, 2012 7:51 AM   in reply to EditorPete

    My guess is that the next update we see will be for Mountain Lion compatibility and no mention of these issues.

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 18, 2012 8:04 AM   in reply to EditorPete

    EditorPete wrote:

     

    I know this thread is getting very long and frustrating, I too want to use PrP CS6 in a professional manner, but do not have the confidence yet to have clients sitting behind me while I explain why there are so many issues with a new piece of software, as my deadlines creep up. None of us can be hadcuffed by the tools we use on a daily basis. PrP CS6 is like driving my first car .....fingers crossed and hope I make it to my next destination, every time I hop behind the steering wheel.

     

    I have ZERO confidence in Pr with clients in the room.  Not just for the Serious Error probability, but also for the fact that audio is out of sync or completely gone 3/4 of the time I hit the spacebar.  Pr's saving graces, when I'm working alone (which is most of the time), is that the CUDA accelleration and Dynamic Link with Ae compensate for Pr's general bugginess.

     

    I have a job coming up on location soon, with a hard and unforgiving deadline.  No way will I put my trust in Pr.  I'll be using FCP7.

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 19, 2012 6:48 AM   in reply to ExactImage

    ExactImage wrote:

     

    Jim Curtis wrote:

     

    My audio stopped working yesterday.  First time for me.  Deleting the audio devices preferences in my User Library brought it back.

    Jim, can you be more specific about the files you deleted? All I have in Library-->Audio are some more empty folders.  No files.

     

     

    Sorry for the delay in responding.  Very busy. 

     

    The files to delete are:

     

    com.apple.audio.DeviceSettings.plist

    com.apple.audio.SystemSettings.plist

     

    In root>Library>Preferences>Audio.  They might also exist in User>Library>Preferences>Audio.

     

    You can also try deleting "com.apple.audio.AudioMIDISetup.plist" and "com.apple.audio.AggregateDevices.plist"  You can use EasyFind to locate any of these files.  If you delete AudioMIDISetup, you will lose any MIDI device maps you've created, so if that applies to you, be aware of that.

     

     

     

    I have a new theory for Serious Error.  I've gotten several in the past couple of days.  After getting them, I delete my Previews and Adobe Caches, and that seems to stop them (for a while).  Thinking back on how one person was getting them after starting a new project, this may not work for everybody.  YMMV. 

     

    BTW, I read a post on another forum that Adobe is aware of this issue, and is working on a fix.  I inferred from the post that "a fix" may require an OS update.  Interesting.

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 19, 2012 6:59 AM   in reply to Jim Curtis

    Thanks Jim.   I did find the files in the main library and deleted them to get my audio back..... but couldn't find them originaly in the user prefs - which is what had me confused.   thanks for the tip though - it saved me several hours already.

     

    I've been running for several days now WITHOUT an error, simply be turning CUDA off.   Then today, I wantedto do some testing and turned CUDA back on.  BANG.   Repeatable every time scrubbing the CTI over these clips with CUDA on, but works perfectly (no errors) without CUDA.  Just to make sure I went back and forth 6 times.

     

    Guess who had CUDA disabled for everything except exporting now!

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 19, 2012 9:56 AM   in reply to needles27

    Just installed CS6 on a 2009 Mac Pro running Snow Leopard.

     

    Out of the box, the help system is entirely non-functional.  When I click on the help button in the splash screen, or through a menu item, nothing happens.

     

    When attempting to import footage from my Panasonic P2 camera using the Media Browser, the entire program hangs and becomes unresponsive.  When I force quit, I get the "serious error" dialog box.

     

    I downloaded the latest Premiere updater but it didn't help.

     

    It's going to be a serious problem for me as an editor if Premiere won't import video off my camera.

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 19, 2012 10:31 AM   in reply to needles27

    It is a long thread.  I tried getting the footage off my camera using Prelude, but it copies the whole arcane folder structure directly from the P2 card -- which I could do just fine in the Finder if I wanted to, but I need something that will also extract my video from the mxf wrapper so I can also use the footage in other software.

     

    As an aside, when I tried Photoshop CS6 that came with Premiere (had been using CS3, which I only purchased because Snow Leopard broke PS 7, which I was pretty happy with...) I found that the Quicktime Export function in Photoshop CS6 has been crippled: previously I could export video in any format Quicktime supported.  Now I can only use JPEG 2000 or Animation, which will add another step for me to actually use the video, and which adds an extra encode, which will add artifacts.

     

    Because my help system is totally nonfunctional, I spent some time digging around on Adobe's site to find the manual in PDF format.  When I went to the section about exporting Quicktime from Photoshop, the content was out of date!  It only discussed CS5 -- which still had the functionality that is now missing!

     

    I therefore see no reason to switch to CS6 since several changes to the interface are also pretty annoying (I don't like the new lasso cursor, there are some changes to the zoom tool, etc.).  I expect to continue using Photoshop CS3.

     

    I think I've been straight up robbed by Adobe.  I just bought all this useless software.

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 19, 2012 11:09 AM   in reply to needles27

    I hate to post a new issue every day, but it seems that since the latest update with Premiere cs6 I'm experiencing more problems than ever.  I just had a new issue arise on my iMac (the very latest one).  I was playing back the timeline and suddenly the video stopped playing, but the audio kept going. My mouse worked, but I couldn't click on anything within premiere or anywhere else on the computer. 

     

    I had no way to force quit..so after 5 minutes I was about to shut down with the power button, but the screen shut off suddenly and the computer wouldn't come back on.  20 minutes later the iMac booted and reported a serious error--and guess what the culprit was? Good old premiere cs6.  I'm glad I have the cloud month to month option, because I think I'm going to have to move back to FCX or Avid.

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 19, 2012 2:36 PM   in reply to Strillogy

    I didn't had problems until I tried to playback a montage with 3 video layers. At each attempt, black screen comes and I need to hard reboot.

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 20, 2012 4:35 AM   in reply to needles27

    I'm on a macbook pro 2.2 ghz i7 4 gig RAM with lion osx 10.7.4. And yes, I use hardware acceleration. Maybe it's the problem, for mercury playback engine is nvidia technology and my video card is ATI.

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 20, 2012 5:42 AM   in reply to Crapule Création

    And this morning, my macbook lost sound! My sound indicator is on mute and I can't unmute it at all. So, no sound anywhere exept in Premiere!!! I had this problme when I first installed CS6, I made a system restore using Time machine and uninstalled cs5.5 with Adobe's cleaner. Then, I installed all CS6 softwares and I had no problems until 2 days ago in Premiere. Really annoying... and I guess I can't listen to streaming videos like last time...

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 20, 2012 5:51 AM   in reply to Crapule Création

    Try deleting the audio preference files in :

     

    Machintosh HD -->  Library --> Preferences --> Audio

     

    Then reboot.

     

     

    Actually, copy those files somewhere else, then delete them and reboot. The system will recreate them.  It would be nice to see what the difference is between the old ones and the new ones so we can see whatis going wrong. It hasn't happened to me for a few days so I don't have the corrupt files to look at!

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 20, 2012 8:53 AM   in reply to ExactImage

    My audio is now permanenty muted on the YouTube volume icon in Safari. The Premiere Pro preview pane never refreshes.  I've sat in front of clients trying to show them stuff and embrarrassed myself.  I'm going back to Final Cut Pro.

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 20, 2012 9:43 AM   in reply to genefama

    Yeah, it's pretty ridiculous how buggy Pr CS6 is.  There's one guy on another Ae forum who claims that Pr is rock solid on his system, which is very similar to mine.  No complaints whatsoever. 

     

    I sure wish we could find out what's causing these errors.  I got about six of them yesterday, and about four today, before lunch.  I recovered from all of them and got my jobs out, but there was a lot of rebooting, trashing of caches and prefs, and finally a re-install of the application. 

     

    I'm saving after just about every two or three edits, just to ensure I don't lose any work.

     

    As soon as I get the Serious Error dialog now, I Force Quit, instead of clicking OK.  I get back up and running faster if I don't let the app go through a  pointless attempt at saving a possibly corrupted project.

     

    Adobe, please put this at the top of your list.

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 20, 2012 11:47 AM   in reply to Jim Curtis

    I was able to resolve my problems with Premiere crashing on import by booting my machine up off the Mac OS install disc, repairing permissions, then re-installing Premiere.  The help system is still completely non-functional however.  I found a copy of the manual as a PDF on Adobe' website.

     

    I'm having difficulty now with Premiere not correctly setting the anamorphic flag when I export DVCPRO HD 720p footage: it comes out square instead of 16:9.

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 20, 2012 4:13 PM   in reply to DavRW2012

    Wow, been following this crazy thread.  Since my first audio error, somehow fixed that, but then serious errors and crashes and force quits, I've completely abandoned Pr CS5.5 and gone back to FCP7.  Thinking about Avid now, but need to make some money to get that.  Can't allow clients to see this embarrassment, so I can't risk it with Pr CS5.5 OR CS6.  This is craziness. 

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 20, 2012 6:30 PM   in reply to footagehead123

    I'm currently on location editing with a team using a 17" MacBook Pro. We have CS6 loaded, but decided not to touch Premiere in CS6. We are using 5.5 with no problems and have really not had any problems on our main MacPro back at the office in 5.5. Staying completely away from Premiere 6 till Adobe gets their act together.

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 21, 2012 8:21 AM   in reply to needles27

    Which is what confuses me about this whole debacle.  I'm running CS5.5, however on a Mac Pro 2,1 (last of the 32bit only towers), and I'm getting serious errors, albeit not as often as some of you, but enough to be a PITA so I've "switched" back.  The majority of you are having issues on CS6.  I haven't even gone there yet. 

    I found this white paper from Adobe this morning detailing hardware/software configs for optimal use of Production Suite CS6.  I haven't had a chance to look in it yet... but maybe there's something useful?

    http://provideocoalition.com/index.php/cmg_blogs/story/adobe_hardware_ performance_white_paper/

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 21, 2012 8:37 AM   in reply to footagehead123

    footagehead123 wrote:

     

    I've completely abandoned Pr CS5.5 and gone back to FCP7.  Thinking about Avid now, but need to make some money to get that.  Can't allow clients to see this embarrassment, so I can't risk it with Pr CS5.5 OR CS6.  This is craziness. 

    I personally didn't/haven't experienced any issues with CS5.5 before or after intsalling CS6. I have reverted back to 5.5 for paying clients until Adobe figures out how to make CS6 stable. Going back to FCP7 for me is an option, but I think CS5.5 works way better for me and my style of editing/compositing. What issues are you having with 5.5 that you can't work with clients on?

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 22, 2012 11:45 AM   in reply to needles27

    I have a group on Facebook called "DSLR Cinematography Indonesia" (http://www.facebook.com/groups/200269766688583/) which consist of 2500+ and growing group members nationwide and many of them are asking how are my experience with the brand new Premiere Pro CS6 for Mac, because I was so enthusiastic about it before.. They are learning students and aspiring young film makers.

     

    What should I say to them now?

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 22, 2012 11:56 AM   in reply to AudyErel

    How about telling them the truth?

     

     

    AudyErel wrote:

     

    What should I say to them now?

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 22, 2012 4:07 PM   in reply to EditorPete

    @ EditorPete It seems I'm a special case as most people on this thread are having issues with CS6.  My problems such as the serious error and force quits/crashes are random.  I am not getting it as bad as others, more like once every day or other day.  Honestly, I haven't had a serious error for a couple weeks now because I'm back to FCP7

    It's not debilitating for sure, but it is certainly a pain and concerning, and after one embarrassing moment with a client I've decided to just skip it for now. 

    This could be stemming from my system in general too, I realize, but I don't have time to troubleshoot software/hardware compatibilities right now.  I do plan on giving Pr a solid shot, but when I find some downtime and a small project.  In the meantime, I'm keeping an eye on this thread.  Keep trucking y'all!

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 22, 2012 6:20 PM   in reply to footagehead123

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

     

    jas

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 22, 2012 7:02 PM   in reply to Jason Van Patten

    I am actually shocked that someone from Adobe would post that! It is evident there is a problem with PPro. I have NOT been able to use CS6 because of the immediate crash I get. Adobe hasn't addressed me or my issues. Trust me Kevin, it's not a user or machine issue. Can you tell me how just scrubbing a video is a user issue?

     

    I really hope they get on top of this and soon.

     

    Just my 2 cents.

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 22, 2012 8:06 PM   in reply to needles27

    These comments make me worry that they won't  address our issues at all.

     

    I had a few crashes today where I lost my progress on the project even though I'd been saving every 2-3 edits/adjustments I made.  It's getting incredibly annoying and I feel like I'm wasting more time worrying about what will happen rather than focusing on just editing.

     

    Two of the crashes today happened right after I finished saving... but after I rebooted and opened the latest save state, the project had reverted back to a previous state.  I'm not sure how this happened because I saw the save progress bar finish and close..so I assumed that meant it was saved. Guess not.

     

    This is becoming a never ending battle and I still have yet to hear anything back from the support team.

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 22, 2012 8:16 PM   in reply to Jason Van Patten

    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!

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 22, 2012 9:08 PM   in reply to needles27

    I hesitate to make this post, but I think it is time someone stepped up.  I'm sure some of you may be incensed, but I hope others may get a grip on reason.  I've been observing the comments and problems posted here and I hope someone other than myself has noticed the remarkably few people who have problems with CS6.

     

    I have been editing for 40 or so years, started editing HD on a Mac in 2000 and switched from FCP 7, to Adobe in January, and have edited a half dozen 1 hr programs in PPr.  Sure there have been a few issues, but not nearly as many as I had with FCP7 before making the move.  For the most part I find the Production Suite a great tool and a well needed and refreshing move into professional editing.

     

    I edit in my studio on a 12core Mac and Kona 3 card and on location, on a relatively new MacBook Pro.  I'm in Alaska at the moment and just finished editing a one hour fishing lodge promo with "0", count em..."0" crashes.  On my studio machine so far other than learning curve problems of my own doing have sufferred far fewer crashes than with any version of FCP.  I only edit HD and have cut well over 200 hours of HD programming in the last few years using a variety of formats mixing HDV, Canon DSLR, DVCPROHD 1080/60i, 30p, 24p, and a ton of GoPro footage in for the most part 1080/30P.  Oh yes and Nanoflash formats as well.  Not only did final cut take forever to convert all these formats it crashed frequently..

     

    About the only time I've encountered issues in CS6 is when I used about 50 stills that we're huge sizes in the same show.  Even then I was able to export the offending stills sequences and reintroduce them to my project.

     

    My message here is for you-all to consider how few there are with serious problems and  forget all this vitriolic whining and spend that time problem solving your issues.  Continual slamming of an excellent production suite wastes your time that could be much better spent in the edit suite.  Or you could just quietly make a switch to wherever. 

     

    Jim Watt, Bennett-Watt HD Productions, Inc.

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 22, 2012 9:18 PM   in reply to jwffvm

    Well Jim, I suspect that if you were having the problem, you might have a few words to say as well. But you're not so good for you. But others are having problems and it is an issue that needs to be addressed. How are we supposed to stop are "whining and spend time problem solving" when it's not something we can't fix. We are not the software engineers. I have a very nice computer that works great with everything else. In fact, I had never even seen that kind of error on a Mac until this problem.

     

    So Jim, we are all extrememly happy that you are crusing right along with your operations but please try to understand that if your system had to be rebooted everytime you starting working in PPro, you'd be a little frustrated as well.

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 22, 2012 9:23 PM   in reply to jwffvm

    Jim,

     

    I can appreciate where you are coming from, but I expect software like this to function properly.  I've been editing with FCP from 2004  until early last year.  I can count the amount of major crashes I had on one hand..and none of those were kernel panics. I also have 2 other sub contractors using the same software with similar hardware and they all have very similar stories so I  feel this is hardly an isolated incident.

     

    Maybe there are just a few bad combinations of hardware with CS6 that causes these issues, I'm not sure.  I do know that two of my newest computers crash constantly editing R3D, H264, and PRORES files. I can recreate it over and over again.  I'd be happy to set up a camera to record 20 minutes of editing to show how many times the computer locks up completely.

     

    I absolutely love the rest of the production suite (After Effects, Photoshop, Illustrator), but Premiere has been a complete nightmare for me. When I invest time and money in software and a workflow, I expect it to work.  Those of us with these major issues have every right to voice our concerns and ask for some support.

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 22, 2012 9:22 PM   in reply to jwffvm

    jwffvm wrote:

     

    I hesitate to make this post, but I think it is time someone stepped up.  I'm sure some of you may be incensed, but I hope others may get a grip on reason.  I've been observing the comments and problems posted here and I hope someone other than myself has noticed the remarkably few people who have problems with CS6.

     

    I have been editing for 40 or so years, started editing HD on a Mac in 2000 and switched from FCP 7, to Adobe in January, and have edited a half dozen 1 hr programs in PPr.  Sure there have been a few issues, but not nearly as many as I had with FCP7 before making the move.  For the most part I find the Production Suite a great tool and a well needed and refreshing move into professional editing.

     

    I edit in my studio on a 12core Mac and Kona 3 card and on location, on a relatively new MacBook Pro.  I'm in Alaska at the moment and just finished editing a one hour fishing lodge promo with "0", count em..."0" crashes.  On my studio machine so far other than learning curve problems of my own doing have sufferred far fewer crashes than with any version of FCP.  I only edit HD and have cut well over 200 hours of HD programming in the last few years using a variety of formats mixing HDV, Canon DSLR, DVCPROHD 1080/60i, 30p, 24p, and a ton of GoPro footage in for the most part 1080/30P.  Oh yes and Nanoflash formats as well.  Not only did final cut take forever to convert all these formats it crashed frequently..

     

    About the only time I've encountered issues in CS6 is when I used about 50 stills that we're huge sizes in the same show.  Even then I was able to export the offending stills sequences and reintroduce them to my project.

     

    My message here is for you-all to consider how few there are with serious problems and  forget all this vitriolic whining and spend that time problem solving your issues.  Continual slamming of an excellent production suite wastes your time that could be much better spent in the edit suite.  Or you could just quietly make a switch to wherever. 

     

    Jim Watt, Bennett-Watt HD Productions, Inc.

     

    Maybe you should take a closer look at the post count and views of this thread!  Obviously it's more then a "few" people with problems.  Since you are having such great luck maybe you should help others with information about your setup instead of slamming them!

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 22, 2012 10:19 PM   in reply to jwffvm

    Jim,

     

    Thanks for the post.  Early in the thread some of us asked whether there were any Mac users who were not having problems and might want to weigh in. After 20 pages, you're the first. I'm glad there's at least one. But so far, the only population with "remarkably fewer" numbers than users with problems seems to be users without problems.  I know happy campers don't rush to post here, but it's interesting how few Apple users post on the site in general. 

     

    It's possible, as you suggest, that we're a marginal group--not because we're whiners, mind you, but because we use Apple computers. A few of the problems we've discussed here have been acknowledged by Adobe, so we know we're not crackpots.  Maybe Apple and Adobe are growing apart.

     

    OSX gets stupider with every update. In the end I wouldn't be surprised if Adobe quit supporting Apple users. Apple bans Flash from its devices and sells competing products that don't fit into their product line. Then they dumb down their video editor and lose customers to Adobe. Then, bang, everything goes buggy between Adobe and OSX. Adobe, meanwhile, forms a strategic alliance with HP.

     

    This isn't a conspiracy theory because there isn't a conspiracy--just a conflict of interest. You know, the way a Mercedes dealer won't put BMW brochures in the showroom or a Fidelity broker won't make it easy to buy Vanguard funds?  It's just a fact of life in business.

     

    If I were Adobe I know I'd take a hard look at ditching CS for Apple--especially when so few people seem to run their stuff on Macs and so few of those that do seem to do so successfully.  But I'm glad you're in that group.

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 23, 2012 2:38 AM   in reply to jwffvm

    jwffvm wrote:

     

    My message here is for you-all to consider how few there are with serious problems and  forget all this vitriolic whining and spend that time problem solving your issues.  Continual slamming of an excellent production suite wastes your time that could be much better spent in the edit suite.  Or you could just quietly make a switch to wherever.

    Well Jim, firstly I'm glad for you that you don't see any of these problems.  I hope you never do.  But the problems are real, not some miss configuration of a system.  Brand new straight out of the box Macs with nothing loaded except CS6 shouldn't be miss-configured - but they still crash.

     

    Macs that are solid on every other program still crash.

     

    It's not just one Mac, its lots of them, Snow Leopard & Lion for sure.

     

    Thinking back, CS5 and CS5.5 used to crash on me when exiting.  Not sure how I should 'fix' a CMD+Q or quit via the menu.  Seems a straight forward operation to me

     

    Just becaue you don't have the problems yourself doesn't mean they aren't real, doesn't mean that lots of people aren't getting frustrated and having multiple crashes ALL day long.

     

    You edit different types of footage (codecs) to me. That could be one of the causes, or it could be a red herring.  But unless some one from Adobe speaks up, we'll never know.

     

    Just for reference, I rearranged my office so I can access both Mac and Windows systems at the same time.  While it doesn't happen as often, the Windows version IS crashing too, although to be fair it's mostly After Effects this time.  Go figure.

     

    I have found that I can minimize my crashes by keeping the audio twirled up unless I'm working on it, and turning CUDA support OFF until it comes time to export.   If I turn CUDA on then within minutes I'm likely to encounter a serious error.    This could mean the problem is not within Adobe's code, but in the CUDA drivers.  But again, unless some one speeks up from Adobe we may never know.

     

    I think what most of us want more than anything else is SOMETHING from ADOBE that tells us they acknowledge the problem and are working on it (with some degree of sincerety).  Right now we feel we're being ignored.

     

    I've tried FCP X is desperation but I can't make it work for me without slowing my down (for several reasons).  

     

    CS6 will be the very last Adobe product I buy unless we can get some acknowledgement of the problem, an idea that they are working on it and a fix BEFORE some bright spark thinks they can take more money off me for CS6.5, because that's ain't gonna happen!

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 23, 2012 9:14 AM   in reply to needles27

    needles27 wrote:

     

    It looks like the engineers decided to or were told to not engage in this discussion.  You can see that they weighed in at the beginning of the thread a few times, and Wil R responded to my crash reports at first, but for a few weeks now won't even respond to my messages anymore.  Another engineer working on another problem told me he has been paying attention to this thread, but when I engaged him on what we can do about it, went silent.  And now hearing that they are considering locking the thread shows that there is something fishy here.  If there wasn't some sort of Adobe internal issue here, why wouldn't an engineer make a brief comment such as "Looking into it." 

     

    I'm not talking conspiracy theory, just that the silence is deafening. 

     

    No. The silence is not because of what you are thinking (cut out the conspiracy theories folks). I've never been told from on high to not post anywhere in the forums. The reason for the lack of employee participation is because this thread has become completely unfocused. It meanders all over the place, contains multiple topics, with issues that might be pilot error, a bug, hardware incompatiblity, or other issue. It might be more valuable to collect the actual issues, lock this thread, and then break out each one of them in a separate thread.

     

    Shall we do so?

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 23, 2012 9:17 AM   in reply to Kevin Monahan

    Kevin Monahan wrote:

     

    No. The silence is not because of what you are thinking (cut out the conspiracy theories folks). I've never been told from on high to not post anywhere in the forums. The reason for the lack of employee participation is because this thread has become completely unfocused. It meanders all over the place, contains multiple topics, with issues that might be pilot error, a bug, hardware incompatiblity, or other issue. It might be more valuable to collect the actual issues, lock this thread, and then break out each one of them in a separate thread.

     

    Shall we do so?

     

    Will it actually help us get a resolutuon any faster, or perhaps let us know that a resolutuon is actually being worked on?

     

    What do you see as the issues you would separate out?

     

    Anything that gets us to a fix faster would be helpful in my opinion, but if the idea is to divide and conquer then that's another matter

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 23, 2012 9:23 AM   in reply to ExactImage

    ExactImage wrote:

     

    Kevin Monahan wrote:

     

    No. The silence is not because of what you are thinking (cut out the conspiracy theories folks). I've never been told from on high to not post anywhere in the forums. The reason for the lack of employee participation is because this thread has become completely unfocused. It meanders all over the place, contains multiple topics, with issues that might be pilot error, a bug, hardware incompatiblity, or other issue. It might be more valuable to collect the actual issues, lock this thread, and then break out each one of them in a separate thread.

     

    Shall we do so?

     

    Will it actually help us get a resolutuon any faster, or perhaps let us know that a resolutuon is actually being worked on?

     

    What do you see as the issues you would separate out?

     

    Anything that gets us to a fix faster would be helpful in my opinion, but if the idea is to divide and conquer then that's another matter

     

    Yes, we would get to a solution faster if we could break down the actual issues into a list. I haven't gone through the entire thread to compile a list of the actual issues, but that would be a good start.

     

    This thread is really hard to read, especially for the people that can actually help you, so let's work together to compile the issues right here.

     
    |
    Mark as:
1 ... 5 6 7 8 9 ... 14 Previous Next
Actions

More Like This

  • Retrieving data ...

Bookmarked By (6)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points