Why does Adobe Premiere Pro CC 2014 quit upon playback of a sequence?

I have a new iMac 27" 3.5 GHz Intel Core i7 with 32 GB 1600 MHz DDR3, running 10.8.5. I have a project using AVCHD files running at 59.94 fps, 1920x1080. The media is on a OWC Mercury Elite- AL Pro Qx2; it is at least 3 years old and it is connected to the iMac via a LaCie eSATA hub (with the eSATA cord). Also I have the Mercury Playback Engine GPR Acceleration (CUDA) enabled.
I can edit in a project for a while fine but then the playback starts getting weird and hanging up. The cursor jumps in the timeline and the picture freezes on a frame. Sometimes, the playback monitor screen turns a solid green. Sometimes I will then receive an error message saying "Sorry, a serious error has occurred that requires Adobe Premiere Pro to shut down. We will attempt to save your current project." I usually have to force quit at this point. I try opening a new project and bringing in the sequences again. It will work for some time, and then the same problem again.
Is there a problem with Premiere Pro or do I need a faster, newer media drive?
Thanks.

Hi Andizzlem,
Andizzlem wrote:
I keep running into this issue. I really don't understand what is happening.
I have a brand new Mac Pro (Late 2013) with a 3GHz 8-core Intel Xeon E5 with 64GB of DDR3 and an AMD FirePro D700.
I run my machine with the latests version of OS X Yosemite.
I keep every Adobe program up to date.
I've been working straight off my internal 1TB SSD.
Any ideas or information would be great.
Thank you!
Are you running the following update? OS X Yosemite 10.10.1 Update
Is the SSD you are running your system on one you installed, or is it factory installed from Apple?
Are you testing with a brand new project file or one you updated from a previous version?
What happens to you precisely when this issue occurs? Are you working for 5-10 minutes, then the program freezes? Or do you get a warning dialog box?
Have you checked permissions for your Adobe folders (see my blog): Premiere Pro CC, CC 2014, or 2014.1 freezing on startup or crashing while working (Mac OS X 10.9, and later)
Have you tried trashing preferences (press Shift + Option while starting Premiere Pro)?
Thanks,
Kevin

Similar Messages

  • Why does Adobe Premiere Pro CC 2014 cannot detect and install BlackMagicDesign's UltraStudio 4k?!

    I have the new MAC Pro and I installed Adobe Premiere Pro CC 2014 few days ago.
    I have the UltraStudio 4K by BlackMagicDesign connected through ThunderBolt.
    BUT...
    Premiere Pro CC cannot add it to the device control.

    Did you install the UltraStudio Device driver before Adobe Premiere Pro CC 2014 or after it ?
    Martin

  • Why does adobe Premiere Pro CC Crash every time I export a movie file?

    Why does adobe Premiere Pro CC Crash every time I export a movie file?

    Please hand type your posts directly into the browser window.  Copy/Paste leaves unwanted code throughout.
    span style="color: #ffffff; font-family: Arial, Helvetica, sans-serif; font-size: 12px; background-color: #000000;"

  • Why does Adobe Premiere Pro modify original footage/asset files (e.g. mov)? (CS6)

    Background:
    A colleague had given me a large 33Gb .mov for use in a project, I put this file on a backup drive.
    I made an identical copy of this 33Gb .mov file and placed it in a folder that I'd use to work on a Premiere Pro Project.
    I ran Adobe Premiere Pro CS6 and dragged in the 33Gb .mov file into the Sequence (imported it)
    Premiere Pro CS6 started conforming the file.
    After it had finished, I noticed that it's Modified Date was just now i.e different to the Modified Date on the original copy of the file on the backup drive (see step 1)
    I ran a BeyondCompare check between the .mov file on the backup drive (see step 1) and the one that the Premiere Pro project was using (step 2, 3) and Beyond Compare reported they were different.
    I had initially thought it was unrelated file corruption of some kind, but I have checked this several times and got the same outcome, so it's definitely Premiere Pro deliberately modifying the file.
    So I am puzzled: these are supposed to be the same file.
    Why would there be a need for Adobe Premiere Pro to modify the footage?
    What does it do to the file?
    Would it not be better to create a separate file if necessary?
    I can accept this if that's how it works and it's good to know that it was Premiere Pro deliberately modifying the files and not corruption (so my hardware ought to be healthy). But it makes more sense to me if Premiere Pro made separate modified copies for its own use. Modifying the file as it does hinders my process for checking the integrity of backups; if the original asset footage files were the same as earlier copies then it would be easy to know that the backups are OK.
    Thoughts?

    Definitive Answer (I believe): It's all about this setting, "Write XMP ID To Files On Import" - which confirms that Adobe Premiere Pro is deliberately modifying the .mov file: http://helpx.adobe.com/premiere-pro/using/preferences.html#WSE3BD4A43-7022-4fe6-97F5-95313 935347B
    These posts give some background as to why having this setting enabled would be beneficial: one benefit being to be able to skip conforming files by matching the conformed file with the original using the embedded XMP tag :-
    http://helpx.adobe.com/premiere-pro/using/preferences.html#WSE3BD4A43-7022-4fe6-97F5-95313 935347B
    http://www.dvinfo.net/forum/adobe-creative-suite/498627-why-premiere-modifying-video-files .html
    https://forums.creativecow.net/thread/205/876064
    (Found using Google search term "adobe premiere pro date modified")

  • Why does "Adobe After Effects CC 2014 Quit Unexpectedly" on launch?

    I'm currently on a 2012 MacPro OS X 10.9.5 with 2x2.66 GHz 6-Core Intel Xeon Processor, 24 GB DDR3.
    I uninstalled CS5 in order to download and install Adobe's Creative Cloud suite. I was able to get Photoshop up and running, but I cannot get After Effects to run. Every time I try to open it, I get the message:
    "Adobe After Effects CC 2014 quit unexpectedly." So, I uninstalled it, and tried re-downloading it and restarting my machine. Same result.
    So, please take a look at my Problem Report below and let me know if you can see any possible solution to this problem. Thanks for any possible help!

    Process:    
    After Effects [2032]
    Path:       
    /Applications/Adobe After Effects CC 2014/Adobe After Effects CC 2014.app/Contents/MacOS/After Effects
    Identifier: 
    com.adobe.AfterEffects
    Version:    
    13.1.1 (13.1.1)
    Code Type:  
    X86-64 (Native)
    Parent Process:  launchd [199]
    Responsible:
    After Effects [2032]
    User ID:    
    501
    Date/Time:  
    2014-10-16 09:23:59.823 -0500
    OS Version: 
    Mac OS X 10.9.5 (13F34)
    Report Version:  11
    Anonymous UUID:  AAAE1F0B-D145-61CB-DF58-86B63D66ED6A
    Crashed Thread:  0  Dispatch queue: com.apple.main-thread
    Exception Type:  EXC_CRASH (SIGABRT)
    Exception Codes: 0x0000000000000000, 0x0000000000000000
    Application Specific Information:
    terminating with uncaught exception of type dvacore::filesupport::dir_create_exception: dva_exception::what() error.
    abort() called
    Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
    0   libsystem_kernel.dylib  
    0x00007fff87256866 __pthread_kill + 10
    1   libsystem_pthread.dylib 
    0x00007fff867a235c pthread_kill + 92
    2   libsystem_c.dylib       
    0x00007fff8ccbcb1a abort + 125
    3   libc++abi.dylib         
    0x00007fff8cd84f31 abort_message + 257
    4   libc++abi.dylib         
    0x00007fff8cdaa93a default_terminate_handler() + 240
    5   libobjc.A.dylib         
    0x00007fff8a24a322 _objc_terminate() + 124
    6   libc++abi.dylib         
    0x00007fff8cda81d1 std::__terminate(void (*)()) + 8
    7   libc++abi.dylib         
    0x00007fff8cda7e7b __cxa_rethrow + 109
    8   com.adobe.dvacore.framework 
    0x0000000103486ee7 dvacore::debug::DebugDatabase::Instance() + 247
    9   com.adobe.AfterEffectsLib.framework    0x000000010027724f egg::dvainit::InitDVAClient(bool) + 655
    10  com.adobe.AfterEffects  
    0x0000000100002f51 main + 1393
    11  com.adobe.AfterEffects  
    0x00000001000029d4 start + 52

  • Why does Trial Premiere Pro CC 2014 crash as soon as the Workspace Appears?

    I've just started my trial of premiere pro but everytime I open the program I'm allowed to choose new project and input the name and then it shows me the workspace for a brief second and then instantly crashes. My computer specs are listed below but I do not think that is the cause of the crash. Any help would be greatly appreciated.
    Intel Core i5-3337U [email protected]
    12GB RAM
    64 Bit operating system Windows 8.1
    x64 based processor
    Acer Laptop

    Windows finally showed me an error message and this is what I got.
    Problem signature:
      Problem Event Name: APPCRASH
      Application Name: Adobe Premiere Pro.exe
      Application Version: 8.0.0.169
      Application Timestamp: 536f4f89
      Fault Module Name: dvaui.dll
      Fault Module Version: 8.0.0.169
      Fault Module Timestamp: 536f2bbf
      Exception Code: c0000005
      Exception Offset: 00000000001a9b41
      OS Version: 6.3.9600.2.0.0.768.101
      Locale ID: 4105
      Additional Information 1: a77e
      Additional Information 2: a77eab15afda63f33d8f166af9292dc6
      Additional Information 3: ebed
      Additional Information 4: ebed0779dfaaeca2a0b6da253d50fb65

  • Adobe Premiere Pro CC 2014 quit unexpectedly.

    I keep running into this issue. I really don't understand what is happening. 
    I have a brand new Mac Pro (Late 2013) with a 3GHz 8-core Intel Xeon E5 with 64GB of DDR3 and an AMD FirePro D700.
    I run my machine with the latests version of OS X Yosemite.
    I keep every Adobe program up to date.
    I've been working straight off my internal 1TB SSD.
    Any ideas or information would be great.
    Thank you!

    Hi Andizzlem,
    Andizzlem wrote:
    I keep running into this issue. I really don't understand what is happening.
    I have a brand new Mac Pro (Late 2013) with a 3GHz 8-core Intel Xeon E5 with 64GB of DDR3 and an AMD FirePro D700.
    I run my machine with the latests version of OS X Yosemite.
    I keep every Adobe program up to date.
    I've been working straight off my internal 1TB SSD.
    Any ideas or information would be great.
    Thank you!
    Are you running the following update? OS X Yosemite 10.10.1 Update
    Is the SSD you are running your system on one you installed, or is it factory installed from Apple?
    Are you testing with a brand new project file or one you updated from a previous version?
    What happens to you precisely when this issue occurs? Are you working for 5-10 minutes, then the program freezes? Or do you get a warning dialog box?
    Have you checked permissions for your Adobe folders (see my blog): Premiere Pro CC, CC 2014, or 2014.1 freezing on startup or crashing while working (Mac OS X 10.9, and later)
    Have you tried trashing preferences (press Shift + Option while starting Premiere Pro)?
    Thanks,
    Kevin

  • Why does adobe premiere pro cs6 capture HVD TO .mp3 format?

    Please help me

    More information needed for someone to help... please click below and provide the requested information
    -Premiere Pro Video Editing Information FAQ http://forums.adobe.com/message/4200840
    Exactly WHAT are you capturing, and HOW are you doing so?

  • Adobe Premiere Pro CC 2014 crashes upon launch

    Everytime I open premiere it says "Adobe premiere cc 2014 has stopped working." Also "A problem caused the program to stop working correctly."
    Ive searched far and wide through threads..
    Ive updated my graphics drivers.
    Ive updated chip stuff.
    Ive done windows update and all that.
    STILL NOTHING!! PLEASE HELP
    Computer Specs:
    Windows 7 Home Premium
    Intel core i7
    CPU 3.50GHz
    64-bit OS
    GEFORCE 760 Graphics

    Exactly what version are you on? There are now three releases of CC2014.
    Have you tried clearing your preferences? Clearing the cache files?
    What third-party plugins are installed, if any? How about codecs?
    Does it crash while the splash screen is up or after the welcome screen or after the project loads?
    Is Windows 7 Service Pack 1 applied. (I know you said that you updated Windows, but it's worth being very specific here.)
    A log file might help identify the cause of the crash. Please right-click 'My Computer', select "Manage," look under 'Event Viewer->Windows Logs->Application' to see if there's an event there from Premiere Pro. If so, copy the contents of that log and paste them here.

  • Why does Adobe Premiere Pro offer more effects for the windows platform than Mac?

    Every time I find a cool new effect that I would like to use it seems it is only offered on the windows platform.  I am a mac user and wondering why this is.

    A lot of that is inertia, though. 3 or 4 years ago, I would have laughed in your face if you'd told me that we were going to move to a PC-based workflow. Then everybody stopped using FCP, Apple refused to update their Pro towers for, like, 3 years, and released a completely redesigned MacPro that has caused us more headaches than it's worth. PPro makes it super easy to bounce projects back and forth between our Macs and PCs. Mainstream computer hardware has become powerful enough that you don't need a professional workstation to edit video and do basic motion graphics. This is totally anecdotal, I realize, but our PCs are every bit as stable (or unstable!) as our Macs, and we've yet to have a single virus on either Mac or PC (mostly because I don't let warez anywhere near our boxes...). At this point, I literally can't think of a single reason to stick with Mac as a platform; if I can put together a $2000 PC that'll perform more-or-less as well as the $3000 MacPro, why would I choose the more expensive option? I guess you could say "ProRes", but I've never really been a fan of ProRes. Besides, DNxHR will be out in a month or two; that'll be the final nail in the ol' ProRes coffin.
    I honestly don't mean this to come off as an insult, but I think that in 2014, anyone who tries to tell you that Macs are somehow superior to PCs just doesn't know what they're talking about. Aside from the price, the playing field is pretty level... I hope I don't come off as being an anti-Apple, pro-PC fanboi; I'm just a big fan of rational, informed decisions.

  • Adobe Premiere Pro CC 2014 Crashing very often! Please Help!

    Hello,
    I am currently editing my first feature on Adobe Premiere Pro CC 2014 and it is currently up to date.
    I am editing on a iMac 27in, late 2013 brand new computer.
    Processor: 3.5 GHz Intel Core i7
    Memory 32GB 1600 MHz DDR3
    Graphics: NVIDIA GeForce GTX 780M 4096MB
    System: OSX Yosemite V 10.10.1
    The project is located on a 8TB G Drive
    7200 RPM
    High Performance ThunderBolt drive.
    Details of the project:
    I am currently working on a fine cut of 5K Red Footage that is being cut in the RAW.
    I work at 1/2 quality settings and have no lag.
    The timeline includes limited stacked video files and various mp3 audio files.
    The Problem:
    Lately, the program will randomly quit or freeze up 4-5 times during an 5-6 hour edit session.
    Many times it is random, however, it seems to happen often if I accidentally click on the end of a clip on the timeline and it goes to switch into trimming mode. 
    Also, it will randomly go into the "pinwheel of death" out of nowhere followed by "Adobe CC is not responding."
    My project file is just about 15MB now.
    What is causing this reoccurring problem?
    How can I make it happen less?  I have scoured the forums and found similar articles but no helpful solutions.
    I have recently turned auto save on to save every 2 minutes because there have been more than one occasion where I lost A LOT of work because of this issue.
    I am about two weeks out from picture lock delivery and this issue is driving me crazy and loosing me a ton of time.
    Please help or let me know if any more additional information can help solve the issue.
    I have sent in well over 25 error reports already.
    Thanks,
    Thomas.

    I think I may have found the solution...
    I completely removed the Premiere Pro folder under User > Documents > Adobe and so far it seems to have solved the problem.
    I of course backed up my projects and than deleted this folder. So far it seems it worked.
    I'll know for sure in a day or two, but after constantly crashing, Premiere hasn't crashed for the last 4-5 hours of work.
    Goran

  • How to work on the same project on two machines at the same time and also exchange progress seamlessly using Adobe Premiere Pro CC 2014?

    We are working on a film project on Adobe Premiere Pro CC 2014. Two editors are working on the same film project (same pproj file ) on two machines. As a result the bin structure and the file structure is exactly the same. We even bought two licenses for the respective machines to make matters simple (at least we thought it would).
    Now when we share a sequence between the two machines, every time we have to import and re-link media. Also each sequence import comes with its own set of files, which are actually already present in the project. Basically the new sequences are looking to re-link the media to the original/ source files only and are completely ignoring the file structure present in the project.
    In all editing softwares, timeline/ sequence sharing is a very common practise when working on multiple machines. Why is it so tedious in CC 2014? Every time we share a sequence between the two machines the media gets doubled and tripled in the project. As a result the project file size is increasing perpetually. Already Premiere CC 2014 is extremely laggy and slow, and this stupid bug is making it more difficult for us to finish our work on time.
    Has anybody ever faced this issue? How do we solve it? We are willing to try out any workflow that you can suggest.

    Concurrently working on the same project it requires a specific implementation in all editing programs like Avid's Unity/ ISIS shared storage. That's what you are simply not considering. none of your issues would be any problem if your projects resided on a commonly accessed server or something like that. Check respective hardware solutions.
    Mylenium

  • Adobe Premiere Pro CC 2014 Will Not Open But other App like Lightroom will..

    Hello,
    Can someone please help with with this problem!?
    I have just purchased Adobe Creative Student Cloud (the full set) and my Adobe Premiere Pro CC 2014 won't open when clicked on... however other App like Lightroom, indesign etc will... Can some explain why this is and help me load it up so i can start editing!
    Thank you,
    George

    if you failed to reset the preferences, do it manually - Adobe Premiere Pro Help | Preferences
    also, make sure your graphics card drivers are up-to-date.

  • Adobe premiere pro cc 2014.2 has stopped working error 1000

    I'm about to throw this desktop across the room. Please someone help me. When I was using this last week, it would close all of a sudden after a while. Now, it does it so quickly I can only save once. Can anyone help? It's going down hill and I've got deadlines.
    Thanks in advance,
    Leslie

    Adobe Premiere Pro CC 2014.2 is the version I am on.
    I am up to date on all updates.
    Windows 7 64 bit Enterprise
    It stops working with anything I do.
    This is the error message I get in the application log:
    Log Name:      Application
    Source:        Application Error
    Date:          4/27/2015 4:13:02 PM
    Event ID:      1000
    Task Category: (100)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      USDOE0042087DT.BECHTELJACOBS.ORG
    Description:
    Faulting application name: Adobe Premiere Pro.exe, version: 8.2.0.65, time stamp: 0x5486db4a
    Faulting module name: devenum.dll, version: 6.6.7600.16385, time stamp: 0x4a5bded7
    Exception code: 0xc0000005
    Fault offset: 0x00000000000016a0
    Faulting process id: 0x13a8
    Faulting application start time: 0x01d0812687cc6c6e
    Faulting application path: C:\Program Files\Adobe\Adobe Premiere Pro CC 2014\Adobe Premiere Pro.exe
    Faulting module path: C:\Windows\system32\devenum.dll
    Report Id: cde2b72f-ed19-11e4-be69-005056c00008
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Application Error" />
        <EventID Qualifiers="0">1000</EventID>
        <Level>2</Level>
        <Task>100</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2015-04-27T20:13:02.000000000Z" />
        <EventRecordID>696921</EventRecordID>
        <Channel>Application</Channel>
        <Computer>USDOE0042087DT.BECHTELJACOBS.ORG</Computer>
        <Security />
      </System>
      <EventData>
        <Data>Adobe Premiere Pro.exe</Data>
        <Data>8.2.0.65</Data>
        <Data>5486db4a</Data>
        <Data>devenum.dll</Data>
        <Data>6.6.7600.16385</Data>
        <Data>4a5bded7</Data>
        <Data>c0000005</Data>
        <Data>00000000000016a0</Data>
        <Data>13a8</Data>
        <Data>01d0812687cc6c6e</Data>
        <Data>C:\Program Files\Adobe\Adobe Premiere Pro CC 2014\Adobe Premiere Pro.exe</Data>
        <Data>C:\Windows\system32\devenum.dll</Data>
        <Data>cde2b72f-ed19-11e4-be69-005056c00008</Data>
      </EventData>
    </Event>

  • Adobe premiere pro cc 2014 - constantly crashing

    Naturally, my project is under deadline..
    My system is running OS X 10.9.4 (13E28)
    late-2012 MacBook Pro Retina
    2.6 GHz Intel Core i7
    16GB 1600 MHz DDR3
    Intel HD Graphics 4000
    NVIDIA GeForce GT 650M
    768Gb Flash Hard Drive
    My project consists of DSLR footage (h.264 compressed files) and Zoom H4N Audio (.WAV files)
    Even after spending most of Thursday and Friday on the phone with Adobe support; deleted all files from media cache, re-imported project, waited for premiere to re-conformed footage, etc..
    ...I still find my project loading sluggishly.. like it takes 15 minutes until video clips in the sequence will fully loads & appear in the project window... it becomes momentarily operable before quickly becoming inoperable as the video and audio no longer playback or respond to the cursor.
    At that point  (when playback no longer works) I can still save the project.
    It seems as though the software loses the dynamic link between the footage as it completely goes black.
    Then when I try to exit Premiere CC 2014.. the program locks up and crashes with no report.
    The crash reports I have are from a few days ago when they first began and before they stooped generating reports.
    Majority of the errors were:
    Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes: EXC_I386_GPFLT
    It also crashed a few times with the following errors:
    Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes: KERN_PROTECTION_FAILURE at 0x00007fff5fbfdef0
    Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000018
    Any help would be greatly appreciated!

    First I must say.. ADOBE PREMIERE PRO CC 2014 is glitchy as hell (and in my three weeks editing a documentary or rather two weeks bc I lost an entire week due to this issue) I have come to learn and identify some workaround solutions..
    Here is what I originally wrote after speaking to five different Adobe engineers...
    It is only an issue with PrCC2014 and the temporary solution before the upcoming update is to...
    1) Go into Preferences... Audio... and UNCHECK the box next to "Maintain pitch while shuttling."
    [this is a new feature in PrCC2014 that is processor intensive, causes audio dropouts, and is a major player in why the playback suffers]
    2) Go into your sequences settings for each sequence you have for DSLR footage and change the Editing Mode preset to "CUSTOM"
    3) Next scroll down to Video Previews and change the preview file format to "QuickTime" and the codec to "Animation."
    4) Uncheck the box  next to "Composite  in Linear Color (requires GPU acceleration or max render quality).
    [this is another new feature that is also processor intensive & is also a key suspect to the problem]
    THE KEY TO FIXING (temporarily) THE BEHAVIOR
    When your computer begins to show signs of the glitchy - sluggish playback behavior..
    Stop.. go back into your SEQUENCE SETTINGS and change it to a different EDITING MODE (only temporarily) and click OK.
    You could change yours from ProRes to CUSTOM (as indicated in step #3)
    Next a prompt will pop up asking you...
    Click okay then immediately go back to SEQUENCE SETTINGS and change it back to your original setting, in your case, ProRes.
    Somehow, by DELETING those PREVIEW FILES it essentially resets the issue... until the dreaded glitchy behavior returns.
    I have had luck with this trick and hopefully you will too..
    Cheers!

Maybe you are looking for