Premiere Pro CC 7.2.1 Crashing and Corrupting on Mac

This started shortly after updating from 7.1, to 7.2, to 7.2.1 almost back to back.  I cleaned out everything and re-installed, updated all CUDA drivers, and crashed through the forum without finding a specific cure for my problem.  I use Digital Rebellion Crash Analyzer to tell me what is happening and this is what it said for the past 3 crashes.
1st Time.
User Interface Crash
     Relevant Line = 1 com.adobe.UIFramework.framework    0x00000001048184ef UIF::TimeBarControlImpl::Enable(bool) + 79
2nd Time.
     Relevant Line = 0 com.adobe.HandlerTimeline.framework    0x000000010bdd60f6 HandlerTimeline::TrackViewArea::SetVisibleBaseTime(dvamediatypes::TickTime const&, double const&, bool) + 54
3rd Time.
     Relevant Line = 1 com.adobe.UIFramework.framework    0x00000001048184ef UIF::TimeBarControlImpl::Enable(bool) + 79
I'm hoping someone with a Mac / Premiere background will be able to link these 3 crashes to one cause, but they would only solve half of my problem.
I believe Auto Save was corrupting my project Save files for the past 5 days.   I had Autosave set to 20 minute intervals before and after Saving and closing my project I was unable to open it again.  Even after cleaning out the media cache and resetting Premiere (re-installing) back to defaults the projects themselves would not open without freezing during loading of media.  I was forced to create a new project and reimport the previous one to advance in my editing process.  After disabling auto-save, I can now save a project and re-open it safely (most of the time), but it doesn't help when the program itself crashes.
Any and all help would be appreciated.
Thanks,
Corn
Computer Specs: 2012 MacBook Pro (non-retina). Processor  2.7 GHz Intel Core i7 . Memory  16 GB 1600 MHz DDR3 . Graphics  NVIDIA GeForce GT 650M 1024 MB . Software  OS X 10.8.5 (12F45). CUDA Driver Version 5.5.28 (Updated 10 hours ago).

I'm not sure what the TimeBarControl is (not a developer...) but my best guess is that it's the widget that the scrub bar in the Timeline and the Monitors is built on. As for what could be causing the crash, I'd only be guessing. A few things I'd try to isolate:
Whether the crash is limited to certain sequences, or possibly just one.
Whether it's tied to certain content: a single clip,  a multicam or nested sequence, ...
Given the TimeBarControl  and SetVisibleTimebase refs, whether it's associated either with the way you have things set up for one or more of the scrub bars (zoom level, timecode display mode, Show Audio Time Units...) or with the actual timebase of the content or the sequence (unusual frame rate, use of Interpret Footage to specify the frame rate of content).

Similar Messages

  • 4k Pro Res crop/resize causing crash and corrupt recovery save

    Hello,
    I am working on an edit of F55 XAVC 4k footage that has been turned into pro res 422 files for an offline edit.
    The edit calls for a lot of split screen work, and when I resize or use the crop effect, put another layer underneath, and then try to move either layer forward or backward in the timeline, premiere always crashes. I could deal with this, but unfortunately premiere saves the project upon crashing, and when I open it again, it launches into the recovery file, which has the bug still present, which immediately causes premiere to crash.
    Is there a way to turn off this recovery or auto save on crash feature? I just wish to open the file from the last point I manually saved it, but seem unable to do so.
    Also, I have auto save set to save every three minutes but it does not save. Not sure why!
    Any help appreciated.
    Burning time in Boston,
    FIlouza

    Filouza wrote:
    2. Switch project from mercury to cuda render in project settings, under the file menu.
    Thanks Filouza,
    Do you mean switch Project Settings in Renderer > Mercury Playback Engine from Open CL to CUDA?
    Thanks,
    Kevin

  • Osx 10.8.5 premiere pro cc 7.2.2 crash crash crash crash crash

    Hey discussion gang -- been running into mega crash problem with PP CC 7.2.2
    Albeit I'm running Premiere Pro on a Late 2011 Macbook Pro 16GB RAM, surely there shouldn't be so many crashes.  I'm working on a short documentary, which has 5 days of footage, all of it h264 quicktime movs shot on Canon60D, approximately 8 hours each day, with 2-channel wav audio files from a separate recorder.
    My project file is huge, around 425MB, as I've got sync sequences from each day with all the footage synced to my separate audio source, and I've been duplicating my edit sequences every day, to preserve old edits.
    Perhaps this is the source of my crashing issue.  Though I've since gone through my project and deleted a bunch of old edits, which I don't need to preserve. Today, I've used the blade tool, resulted in crash with spinning ball of doom, force quit; I've tried to copy 5 clips with 6 lines of audio, resulted in crash with "serious error"; I've used the track select tool, resulted in crash with spinning ball of doom, force quit. Today, my Premiere 7.2.2 has crashed about 12 times, each time requiring a 4-5 minute restart.  I know my project file is large, but I used to have much larger project files in FCP7 and this same lappy would seldom crash.
    I've recently installed Memory Booster, which is a program to clean up unused RAM.  This tool installs a readout of your free RAM in your menu bar and I've noticed that Premiere Pro is a memory hog.  I can sit here and edit for about 30 minutes and watch my free RAM drop from 14.5GB to 100MB.  Is this what's causing my crashes?  I've got no other programs running. 
    I'm at a loss.  I've been avoiding upgrading to Mavericks, as I've heard of other issues stemming from installing that OS.  But perhaps PPCC 7.2.2 is optimized for Mavericks? 
    I've noticed Lightworks released their public beta today; I'm feeling compelled to switch editing systems again, twice in a year.
    Many thanks for any help / info.

    Hi yoshinatsu,
    A few things to try for your crash on launch issue:
    Change Preferences to Write: When you upgrade a Mac OS (as opposed to installing the new version fresh), Mac OS can set permissions of folders and files incorrectly. To fix this in the case of Premiere Pro, go to the preferences folder and set the entire preferences folder ( /Library/Preferences/Adobe/Premiere Pro/7.0 ) and all of its contents to be writable, not read-only. Though you did a clean install, please check this anyway.
    Trash preferences
    Make sure the System Preferences > Language & Text is set to English
    Have an AMD GPU? Certain applications, like DaVinci Resolve install CUDA drivers, even if you have AMD GPUs. This can cause issues with Premiere Pro. See this blog post.
    Sign out from the Creative Cloud application and then Sign in
    If you have a NVIDIA GPU, update CUDA drivers in System Preferences > CUDA
    These are things that have solved similar issues for other customers. If none of these things work, send me a PM and I'll escalate your issue.
    Thanks,
    Kevin

  • Premiere Pro cc 2014 8.2 crashing

    I’ve been working on a documentary with several types of footage/stills.  Crashes have become more frequent as I get further into the project.  Lately it’s been freezing up to the point where I have to force quit and I’ve also gotten the “Sorry, a serious error has occurred” where it has to restore the file.  It's also happening with a new project file which has only one type of footage in it.
    My machine’s getting old and I plan on replacing it soon but it still works fine with FCP7, Avid, After Effects, etc. Here are the specs:
    2.8 GHz Intel Core 2 Duo
    4 GB 1067 MHz DDR3
    NVIDIA GeForce 9400M 256 MB
    Footage is on an external Glyph drive 2TB
    MacBook Pro mid-2009
    OSX 10.9.5
    Here’s what I’ve tried:
    -I made sure my Adobe folder preferences are set to read/write.
    -I’ve tried recreating the preference file (ctr+alt+shift) several times while starting the program. This seemed to help the first time I tried it but then it started crashing again and eventually gave me the “Sorry, a serious error has occurred” message again.
    -I’ve cleaned the media cache
    -The only plugin I have installed is FinalPlug (a compressor) but I haven’t been using it and don’t see that anyone’s listed it as being problematic with PP CC, so I haven’t uninstalled it.
    Should I update the video driver? Can anyone advise me on how to do that?
    Thanks!

    Hi, I have something similar to this happening to me. Does a crash report box also pop up for you? I get one, but it's for Apple, not Adobe. I  didn't have my problem until getting a new Mac with Yosemite installed, so it shouldn't be your machine's age.
    Part of my error message looks like this:
    Crashed Thread:   
    0  Dispatch queue: com.apple.main-thread
    Exception Type:   
    EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes:  
    KERN_INVALID_ADDRESS at 0x0000000000000000
    VM Regions Near 0:
    -->
    __TEXT            
    0000000100000000-0000000100003000 [   12K] r-x/rwx SM=COW  /Applications/Adobe Premiere Pro CC 2014/Adobe Premiere Pro CC 2014.app/Contents/MacOS/Adobe Premiere Pro CC 2014
    Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
    0   com.adobe.AudioSupport.framework    0x0000000103d7f8d0 ML::Device::GetNumberOfPhysicalChannels(unsigned int, bool) + 80

  • Premiere Pro CC 2014.2 often crashes (Windows)

    Hi...i'm on windows 8.1 and using premiere pro cc 2014.2.... there have been bugs and really need help as this problem has affected my workflow and i even can't get a solution of this.....
    1. There are times my files will be offline and have to reconnect them one by one....and sometimes i have to restart the software or computer to reconnect them back....there are also times when i reconnect them and get a "files are corrupted" error but they can be opened in redcine x...
    2. I also get error when trying to reconnect audio files stating a "header error....
    3. If i mark in and out and try to copy paste from one sequence to another, the computer will not respond and freeze....
    I'm using a asus g750jm, i7 2.4ghz, with 24gb of ram.....
    The sequence that i use to edit these red raw files are just 1024x540....
    Need serious help here...thank you...

    Hi Nazim,
    You´re not alone! It looks like the whole world of Mac users crashes when inside Premiere Pro CC 2014.
    I´ve tried back peddling to early version (8.0) same problem.
    So this is for Kevin (who probably will tell me to stay with the Mac-probelm-users-thread):
    Here is my latest crash report (out of hundred):
    Process:               Adobe Premiere Pro CC 2014 [717]
    Path:                  /Applications/Adobe Premiere Pro CC 2014/Adobe Premiere Pro CC 2014.app/Contents/MacOS/Adobe Premiere Pro CC 2014
    Identifier:            com.adobe.AdobePremierePro
    Version:               8.0.0 (8.0.0)
    Code Type:             X86-64 (Native)
    Parent Process:        ??? [1]
    Responsible:           Adobe Premiere Pro CC 2014 [717]
    User ID:               501
    Date/Time:             2015-04-03 14:55:56.729 +0900
    OS Version:            Mac OS X 10.10.2 (14C1514)
    Report Version:        11
    Anonymous UUID:        3C4BE865-15A1-83C0-2A8F-247384EECB0D
    Time Awake Since Boot: 19000 seconds
    Crashed Thread:        0  Dispatch queue: com.apple.main-thread
    Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes:       KERN_INVALID_ADDRESS at 0x00000000000000c0
    VM Regions Near 0xc0:
    -->
        __TEXT                 0000000100000000-0000000100003000 [   12K] r-x/rwx SM=COW  /Applications/Adobe Premiere Pro CC 2014/Adobe Premiere Pro CC 2014.app/Contents/MacOS/Adobe Premiere Pro CC 2014
    Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
    0   com.apple.CoreText             0x00007fff8c98db95 TLine::~TLine() + 243
    1   com.apple.CoreFoundation       0x00007fff9105ca9e CFRelease + 526
    2   com.apple.HIToolbox           0x00007fff8d5a0944 TCoreTextLineInfo::~TCoreTextLineInfo() + 34
    3   com.apple.HIToolbox           0x00007fff8d5a0913 TLayoutInfo::Clear() + 51
    4   com.apple.HIToolbox           0x00007fff8d5a078f TCoreTextEngine::Invalidate() + 49
    5   com.apple.HIToolbox           0x00007fff8d59d0a8 TCoreTextEngine::Init(void const*, THIThemeTextInfo const*) + 92
    6   com.apple.HIToolbox           0x00007fff8d59cf00 TThemeTextCache::Create(void const*, THIThemeTextInfo const*) + 460
    7   com.apple.HIToolbox           0x00007fff8d59c8bf DataEngine::GetTextDimensions(void const*, double, HIThemeTextInfo*, double*, double*, double*) + 259
    8   com.apple.HIToolbox           0x00007fff8d59c785 HIThemeGetTextDimensions + 185
    9   com.apple.HIToolbox           0x00007fff8d5e124e HIStandardMenuView::MeasureItemTextWidth(__CFString const*, TextLayout*, __CTFont const*) + 122
    10  com.apple.HIToolbox           0x00007fff8d5e0a3f HIStandardMenuView::GetItemWidth(float, TextLayout*, unsigned char*) + 719
    11  com.apple.HIToolbox           0x00007fff8d5dde02 HIStandardMenuView::GetOptimalSizeSelf(CGSize*, float*) + 878
    12  com.apple.HIToolbox           0x00007fff8d5dda1c HIView::SendGetOptimalBounds(CGRect*, float*, CGSize*) + 416
    13  com.apple.HIToolbox           0x00007fff8d5dd84f HIView::GetOptimalSize(CGSize*, float*, CGSize*) + 45
    14  com.apple.HIToolbox           0x00007fff8d5dd755 HandleCalculateMenuSize(OpaqueEventRef*) + 154
    15  com.apple.HIToolbox           0x00007fff8d58213a MenuData::EventHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 358
    16  com.apple.HIToolbox           0x00007fff8d58098c DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1260
    17  com.apple.HIToolbox           0x00007fff8d57fdce SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 386
    18  com.apple.HIToolbox           0x00007fff8d57fc42 SendEventToEventTargetWithOptions + 43
    19  com.apple.HIToolbox           0x00007fff8d5dd4e4 _CalcMenuSizeOnDevice(MenuData*, unsigned short, unsigned int, CGRect const*, unsigned int) + 763
    20  com.apple.HIToolbox           0x00007fff8d5e1bad GetInitialMenuRect(MenuSelectData*, MenuData*, unsigned char, Point, unsigned short, Rect*, unsigned int*, CGPoint*) + 261
    21  com.apple.HIToolbox           0x00007fff8d5f6f32 GetCurrentMenuRect(MenuSelectData*, unsigned int*, CGPoint*) + 110
    22  com.apple.HIToolbox           0x00007fff8d605890 DrawTheMenu(MenuSelectData*, __CFArray**, unsigned char, unsigned char*) + 582
    23  com.apple.HIToolbox           0x00007fff8d60548c MenuChanged(MenuSelectData*, unsigned char, unsigned char) + 356
    24  com.apple.HIToolbox           0x00007fff8d5f1e36 TrackMenuCommon(MenuSelectData&, unsigned char*) + 1211
    25  com.apple.HIToolbox           0x00007fff8d604fb1 MenuSelectCore(MenuData*, Point, double, unsigned int, OpaqueMenuRef**, unsigned short*) + 510
    26  com.apple.HIToolbox           0x00007fff8d604c5e _HandleMenuSelection2 + 446
    27  com.apple.AppKit               0x00007fff9191b8be _NSHandleCarbonMenuEvent + 277
    28  com.apple.AppKit               0x00007fff917b72f0 _DPSNextEvent + 1843
    29  com.apple.AppKit               0x00007fff917b6730 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 194
    30  com.apple.AppKit               0x00007fff917aa593 -[NSApplication run] + 594
    31  com.adobe.Frontend.framework   0x00000001000c948d FE::MacApplication::RunSelf() + 45
    32  com.adobe.Frontend.framework   0x0000000100047cca FE::Application::Run(std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&) + 4058
    33  com.adobe.Frontend.framework   0x00000001000cad44 FE::AppMain(ASL::ObjectPtr<ASL::Module, ASL::AtomicValue> const&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&, int, void*) + 276
    34  com.adobe.Frontend.framework   0x00000001000d1f25 FE::Run(ASL::ObjectPtr<ASL::Module, ASL::AtomicValue> const&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&, int) + 581
    35  com.adobe.AdobePremierePro     0x00000001000018ac main + 508
    36  com.adobe.AdobePremierePro     0x00000001000016a4 start + 52

  • Premiere Pro CC 2014 & Media Encoder Crash when rendering

    Every time I try and render something out of Premiere Pro CC 2014 it will crash before it completes the render. I have no idea why. I am on a windows 8 machine running the latest version of Premiere Pro CC 2014.Any idea what is going on?
    Here is the log from Event Viewer:
    Faulting application name: Adobe Premiere Pro.exe, version: 8.0.1.21, time stamp: 0x53c7b17f
    Faulting module name: mc_enc_avc.dll, version: 9.8.11.6624, time stamp: 0x536af65d
    Exception code: 0xc0000005
    Fault offset: 0x00000000000e7f80
    Faulting process id: 0x650
    Faulting application start time: 0x01cfb99562fe469a
    Faulting application path: E:\Program Files\Adobe\Adobe Premiere Pro CC 2014\Adobe Premiere Pro.exe
    Faulting module path: E:\Program Files\Adobe\Adobe Premiere Pro CC 2014\mc_enc_avc.dll
    Report Id: f30f38a1-2589-11e4-bf2c-bc5ff467c039
    Faulting package full name:
    Faulting package-relative application ID:
    Here is the Report.wer that windows automatically generates: http://pastebin.com/hriEegkJ
    I have also tried rendering out of media encoder and I get a crash also (Report.wer: http://pastebin.com/Dpvk6bDb):
    Faulting application name: Adobe Media Encoder.exe, version: 8.0.1.48, time stamp: 0x53c99d97
    Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
    Exception code: 0xc0000005
    Fault offset: 0x000000002c2cce3d
    Faulting process id: 0xcf8
    Faulting application start time: 0x01cfb9906060796e
    Faulting application path: E:\Program Files\Adobe\Adobe Media Encoder CC 2014\Adobe Media Encoder.exe
    Faulting module path: unknown
    Report Id: 07096c20-2584-11e4-bf29-a0f3c1153ce7
    Faulting package full name:
    Faulting package-relative application ID:

    More hardware information might help someone give you an idea
    -Premiere Pro Video Editing Information FAQ http://forums.adobe.com/message/4200840
    or
    http://blogs.adobe.com/kevinmonahan/2014/01/13/computer-shuts-down-with-premiere-pro-or-af ter-effects/

  • Premiere Pro Timeline with 3 video channels and 4 audio channels, audio channels change to 8 channels when clip dragged onto timeline.

    Premiere Pro Timeline with 3 video channels and 4 audio channels, when clip dragged onto timeline audio channels change to 8 channels. Audio track mixer changes too. I edit undo to remove dragged clip and it reverts back to 4 channels of audio on timeline as does the audio mixer?  Any ideas as to why the audio channels and mixer changes?

    you can check the clip you are dragging to the timeline, if it has 8 tracks... can check by right clicking it in the project bin, choose modify, audio channels.
    The Video Road – Multichannel Audio in Premiere Pro

  • Is there anyway to have Premiere Pro recognize the "in" & "out" points and the sequence's "home" (first frame) as edit points so that the up & down arrow work as short cuts on these areas?

    Is there anyway to have Premiere Pro recognize the "in" & "out" points and the sequence's "home" (first frame) as edit points so that the up & down arrow work as short cuts on these areas?

    Hey guys, I wrote a big long speech trying to be more clear and was just getting more confusing. LOL
    Hopefully this image makes my question a bit easier to understand. In green you can see how the up and down arrow keys land while in Final Cut. In red how they land while in Premiere. I'd like them to land like Final Cut. Thanks!

  • I've been paying for Adobe Premiere pro for the past Thre onth and today, despite the fact that i have paid already for the upcoming month, i cannot access it because of an "intenet connexion problem". But I'm connected and I have the right ID. What shoul

    I've been paying for Adobe Premiere pro for the past three month and today, despite the fact that i have paid already for the upcoming month, i cannot access it because of an "intenet connexion problem". But I'm connected and I have the right ID. What should I do?

    Lanakivee
    Try this it worked for me Pat Willener gave it to me off the site :
    I have not read all you wrote, so I may have missed some points. As I understand it, you installed FP 10 on IE7, but it won't play any Flash content?
    Try this
    download the FP uninstaller from http://www.adobe.com/go/tn_14157
    close all browser windows, then run the uninstaller
    download the offline ActivX installer for Internet Explorer from http://fpdownload.macromedia.com/get/flashplayer/current/install_flash_player_ax.exe
    close all browser windows, then run the installer

  • Is it possible to have the lid open on a MacBook Pro connected to a Cinema Display and have the Mac display blank with the Cinema in highest definition?

    Is it possible to have the lid open on a MacBook Pro connected to a Cinema Display and have the Mac display blank with the Cinema in highest definition?

    Hi,
    Create a play list that you wish to burn. Select playlist, the file from main menu which gives to an option to burn the playlist. A pop up box appears allowing you to select burn speed and disc format.
    Jim

  • Sony NXCAM and Premiere Pro CS 5.5.2 crash (Win7)

    Hello,
    We recently got a Sony NXCAM. We are shooting in SD only (until next year!), so it's not a problem with any particular HD format. Until we got this camera, we've been using Panasonic P2s exclusively. Our Chief has had good luck with these Sonys (admittedly editing in AVCHD mode and exporting to DVD mostly), so he decided to give one a try for news.
    When we first started using the Panasonic P2s, we had a bugger of a time with the video clips coming into premeiere in one stereo clip and us needing it split to mono (because of how we often capture in the field where the on cam mic is for nat sound, while the attached mic is for the actual interview audio - it's recorded to the same clip simply as one side or another). This was also during the days of Premeiere crashing every time you tried to adjust stereo audio gain (has that actually been solved?). Anyway, that's all been solved and the systems have been stable and working fine for the last two-three years aside from the occasional issue with full disk drives (reporters NEVER DELETE ANYTHING, ARG, smash! ).
    Up to this month: We have one reporter who has been using this Sony and every time she edits she is experiencing crashes when she adjusts audio (gain, I believe), which of course reminds me of the problem we had with the Panasonics and their MXF wrapped MPEG2 clips. That said, we have the same project settings bringing in the Sony's MPEG2 video with all tracks in mono, and I have a feeling that is what needs to change, I'm just not sure how. It has to be something in how the clips are configured, but I can't figure out what the difference is and more importantly what I need to do to fix it. I am including a screen shot of the GSPOT info on the file. We're using up to date drivers, and Adobe is updated to the lastest version and the system has been working fine for the last two years, except for this one issue of late. We are not using the Sony software to convert the clips simply because we don't have a need to shoot extra long clips, and they join just fine on the timeline if we do, or have so far at least. That and its native format for SD is MPEG2, precisely what we need. Anyway, I'd love some help on this if anyone has any ideas.

    As a counterpoint to Harm's perspective, I'll say that I've used Quicktime Pro since early version 6, and I haven't ever had to uninstall or remove it to get Premiere Pro to work, or to work with the QT codecs.  Quicktime has never been a problem for me, and it's been a lifesaver on more than one occasion.
    Adobe has some custom QT importers for Premiere Pro that are 64-bit, and you don't need QT installed to take advantage of them.  But if you have clients that can only provide you with MOV files, or that demand MOV files for delivery, then you will need to have Quicktime installed.  Further, some applications like After Effects, (maybe)SonicFire Pro, and Cinema 4D require Quicktime to be installed to take advantage of all their features and plugins, so you can get boxed into the Quicktime corner that way as well.
    No need to fear Quicktime.  Just be aware that it can potentially be a source of problems and conflicts with Premiere Pro.  So far, that hasn't been the case for me.
    Jeff

  • Premiere Pro CC(V.8.0) sluggish and crashes during Playback

    Issue:
    Premiere Pro CC(V.8.0) extremely sluggish and crashes during Playback. My video won't play at all unless I render (which is no problem). I render all my clips and attempt to play it back. It usually will allow me to watch it the first time around. After that, the program freezes up or becomes extremely sluggish. I have even had a blank green screen pop up on my playback monitor. Sometimes the program will generate the message "A Serious Error has occurred" and will shut down. Other times, the program just locks up. I am not running any other programs except email.
    Here is what I've tried:
    Cleared all my cache files
    Set my Mercury Playback set to "Software only"
    Restarted the program and computer after doing the above.
    Made sure I had no RGB Curves as an effect (as I did see that was an issue from other threads)
    Deleted all unused footage
    Deleted all render files and re-rendered everything.
    I am editing footage that requires Ultra Key. I am using a Three-Way Color Corrector. My video isn't even 1 minute long, so I would think it would be easy to render and playback.
    Here is what I am working on (I know I need an upgrade - was hoping to after I finished this client's project):
    Macbook Pro 2008
    Processor  2.4 GHz Intel Core 2 Duo
    Memory  4 GB 667 MHz DDR2 SDRAM
    Graphics  NVIDIA GeForce 8600M GT 256 MB
    Software  OS X 10.9.3
    HELP! This is seriously slowing my workflow and my project is due tomorrow. Any advice would be appreciated.

    I am Windows but I have some saved Mac links that may help
    -next link says After Effects, but check YOUR permissions !!!
    -http://blogs.adobe.com/aftereffects/2014/06/permissions-mac-os-start-adobe-applications.ht ml
    -Mac 10.9.3 workaround https://forums.adobe.com/thread/1489922
    -more Mac 10.9.3 https://forums.adobe.com/thread/1491469
    -and https://forums.adobe.com/thread/1507936
    -Enable Mac Root User https://forums.adobe.com/thread/1156604
    -more Root User http://forums.adobe.com/thread/879931
    -and more root user http://forums.adobe.com/thread/940869?tstart=0

  • Premiere Pro CC (v7.2.1) crashing every time I try to export

    I've been trying to export a sequence on Premiere Pro CC (version 7.2.1) in editing mode: Canon XF MPEG2 720p, but I'm getting a message that says "Sorry, a serious error has occurred that requires Adobe Premiere Pro to shut down. We will attempt to save your current project.
    I'm running a one-day-old iMac on OS X (version 10.9) with a 2.9 GHz Intel Core i5 processor and 16 GB of memory, so I wouldn't think the computer is the issue.
    I've tried restarting both Premiere and my computer 15-20 times with no success. I've also tried emailing the project to a different computer to export (as a .mov), but I received a prompt saying "The project appears to be damaged. It cannot be opened."
    The render bar is yellow, and I've tried to find a way to turn it green without any luck. I've tried downloading the patch on the Adobe site, and I've searched the forums for similar problems, but I haven't found a way to make it work yet.
    Any help would be greatly appreciated.
    Thanks,
    Britton

    If it helps, here is my problem report:
    Process:    
    Adobe Premiere Pro CC [836]
    Path:       
    /Applications/Adobe Premiere Pro CC/Adobe Premiere Pro CC.app/Contents/MacOS/Adobe Premiere Pro CC
    Identifier: 
    com.adobe.AdobePremierePro
    Version:    
    7.2.1 (7.2.1)
    Code Type:  
    X86-64 (Native)
    Parent Process:  launchd [259]
    Responsible:
    Adobe Premiere Pro CC [836]
    User ID:    
    502
    Date/Time:  
    2014-02-10 12:17:04.221 -0500
    OS Version: 
    Mac OS X 10.9 (13A603)
    Report Version:  11
    Anonymous UUID:  0F8558D9-FF49-EDFC-83B6-F7134821A052
    Sleep/Wake UUID: 8AB1437A-EF0C-4E4F-8B0B-12FAB0197554
    Crashed Thread:  0  Dispatch queue: com.apple.main-thread
    Exception Type:  EXC_CRASH (SIGABRT)
    Exception Codes: 0x0000000000000000, 0x0000000000000000
    Application Specific Information:
    terminating with unexpected exception of type dvacore::filesupport::dir_create_exception: $$$/dvacore/filesupport/DirCreate=The directory '@0' could not be created. Please check the parent directory protection or permission rights.
    abort() called
    Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
    0   libsystem_kernel.dylib   
    0x00007fff9748d866 __pthread_kill + 10
    1   libsystem_pthread.dylib  
    0x00007fff8c58035c pthread_kill + 92
    2   libsystem_c.dylib        
    0x00007fff93ea7c5a __abort + 145
    3   libsystem_c.dylib        
    0x00007fff93ea7bc9 abort + 140
    4   libc++abi.dylib          
    0x00007fff96c41141 abort_message + 257
    5   libc++abi.dylib          
    0x00007fff96c66aa4 default_terminate_handler() + 240
    6   libobjc.A.dylib          
    0x00007fff94842322 _objc_terminate() + 124
    7   libc++abi.dylib          
    0x00007fff96c643e1 std::__terminate(void (*)()) + 8
    8   libc++abi.dylib          
    0x00007fff96c64456 std::terminate() + 54
    9   libc++abi.dylib          
    0x00007fff96c66ad3 default_unexpected_handler() + 23
    10  libc++abi.dylib          
    0x00007fff96c643a5 std::__unexpected(void (*)()) + 6
    11  libc++abi.dylib          
    0x00007fff96c64d52 __cxa_call_unexpected + 129
    12  com.adobe.SettingsUI.framework
    0x00000001087e6c32 AME::AMESettingsDlgImp::AddPreviewSource(ASL::InterfaceRef<BE::IProject, BE::IProject>, ASL::InterfaceRef<BE::ISequence, BE::ISequence>, dvamediatypes::TimeDisplay, dvamediatypes::TickTime const&, dvamediatypes::TickTime const&, dvamediatypes::TickTime const&, dvamediatypes::TickTime const&) + 978
    ==========================
    Edited by moderator to trim the crash report down to the essentials. Since these forums do not support attaching file (due to legal and security issues), we recommend uploading files using Acrobat.com’s Sendnow (https://sendnow.acrobat.com) or similar services (YouSendit.com, etc.)

  • Adobe Premiere Pro CC / Media Encoder CC Crashing On Export

    Hi,
    I have a 1 hour project consisting of
    - iPhone 5 Video clips recorded at 1080p/30fps using app FilmicPro
    - Various Image files, imported as PSD's
    - WAV Sound files
    My Sequence Settings are:
    Export Settings are:
    As you can tell by the file name, i already installed ALL updates.
    I just installed a new graphics card (GTX 770) a few days ago, but these crashes were happening before i installed the card, and now after I've installed it, so it's not related at all (before i was just using my CPU (Intel HD 4600). (At the moment I have CUDA enabled).
    Full Specs
    - Windows 8.1 Pro
    - Adobe Premiere Pro 7.2.2
    - Adobe Media Encoder 7.2.2
    - Intel i7 4770k
    - 8GB RAM
    - NVidia GTX 770
    The crashes always happen at the exact same place on both Premiere Export and Media Encoder, no idea what's causing it, I've played around with the settings and managed to export it a few times but not at the quality I want. If i render my entire sequence preview's first, and then export using preview files then it exports fine using MPEG Preview. Not exactly the format/quality I want though, if there is anything i have missed out then please ask, I do intend to check the boxes for Maximum Bit Depth and Maximum Render Quality
    P.S. I have already tried
    A) Clear Media Cache
    B) Reinstall Premiere/Media Encoder
    C) Change Location of Project Files
    Thanks,
    Jay

    Hi Jay Singh,
    Thanks for posting on Adobe forums.
    Please try to check the resolution on the PSDs in the Project. and Make sure that the resolution should not exceed more than 1920*1080. This is could be the issue on crash on export.
    Let us know if this will help.
    Happy Editing,
    Sandeep

  • Importing a Premiere Pro Sequence into After Effects Crashes After Effects

    Hello,
    I'm on a Quad Core Mac, 2.8GHZ with 6GB of Ram.
    I have a Premeire Pro project with varying MOV and MP4 files; from a DSLR and from a Sony EX-1 camera.  This project has lots of media, over 3 TBs, and each and every time I try to import it into After Effects-After Effects crashes and does not respond.
    Please help.
    Thanks

    Don't try and do a whole movie in AE. After Effects is for making shots or short sequences. Break up the projects. Organize. 3TB of source materials into AE's Project folder means linking, analyzing, interpreting, and generating previews for enough material to shoot a feature film. Bring in the shots you're working on, not the entire movie. If you need to do an entire movie, break that up to Scenes and make each scene a separate project.
    Terabytes of data would also choke Final Cut Pro, Premiere Pro, Avid, or any other NLE if it was dumped in all at once. The only reason that a NLE can handle that much data is that there were some caches created when the footage was imported.

Maybe you are looking for

  • Problem calling function in attached movie

    In my main timeline I'm attaching a movieclip from the library & then trying to call a function defined in frame one of the attached movieclip - however it does not run ? Can anyone see what is wrong with this code... var mcRef:MovieClip = _root.targ

  • Are widgets secure?

    There's all this stuff about Cross-site scripting & that the Javascript in a widget can read a lot of details of your site. If you place content - such as your gallery on your secure dotmac page & drive it in a wide open website... Are you being comp

  • IPod suddenly starts playing after being inactive for some time

    After using my iPod I press the play/pause button and keep it pressed for some seconds to turn the iPod off. Some hours later -I don't know exactly how long since this usually occurs overnight- the iPod starts playing music!!! Am I missing something

  • Font errror when opening some FrameMaker files

    When opening some FrameMaker files in Windows 7, my clients are getting the following message: The FrameMaker Console provides these details: The "Arial Black Bolded" Font is not available.   "Arial Black Heavy" will be used in this session. The "Ari

  • Find my mac and non-admin account

    Hello all, so, on my macbook pro I have 2 user accounts. One is the administrator account, that I don't normally use to work. The other is a non-admin regular account which is what I log into every day for my work. Today I upgraded to Lion 10.7.2 and