Skip to main content
Inspiring
July 7, 2013
Answered

Premiere Pro (CC) has encountered an error. (Mac)

  • July 7, 2013
  • 4 replies
  • 27232 views

Darn, this is bad.  I'm having flashbacks to Pr CS6.0.0.  I keep getting this error, which leads to a crash:

Premiere Pro has encountered an error.

[/siree64/releases/2013.02/PremierePro/

Messanine/Make/Mac/../../Src/Utilities.cpp-780]

Pr CC has been working pretty well on older CS6 projects and new projects started in CC. 

For the record, I'm a professional Premiere Pro power user; not a novice.

This recurring problem happens when I just click on audio or video certain clips in a timeline.  I exported this project from FCP7 via XML and into Pr CC.  All the sync clips are double system; video from a Canon transcoded to ProRes; audio files are .WAV from a Zoom recorder.

{Sidebar:  I have an ongoing project in CC I started in CS6 with Canon H264 video, and Zoom audio.  I'm not having the same problems.}

I exported this problem project to XML from Pr CC, opened it in Pr CS6, and I don't get the crashes when clicking on clips. 

This is a new issue with PrCC, and apparently projects imported via XML.

I did all the usual maintanence: Trashed prefs, previews and Media Cache.  Ran Disk Warrior.  Problem persists.

Workaround is, once I locate a clip that causes the crash, use In and Out around the clip to lift it, then replace manually.  Slow going.  LOTS of crashing.  Every few minutes.  Once the media is replaced, the crashing stops.  So, this rules out corrupt media.  Besides, I ran Digital Rebellion's Corrupt Clip Finder, and all media on this project passes as not corrupted.  I save about every minute now, so as not to lose too much work.

Silver lining: Pr CC launches about ten times faster than Pr CS6, so getting back to work after a crash is faster.

If anybody has a clue on how to stop this, please chime in.

    This topic has been closed for replies.
    Correct answer Jesse Zibble

    Thanks for the explanation, Charles.

    I did open this project into 7.0.1, which I started in 7.0, but I haven't tried re-importing the XML, since I've already done a fair amount of work on the project since bringing it into 7.0. 

    I did try just importing the XML into a clean install of Pr 7.0 (The installer doesn't install the current version.), and no crashes!!!  Weird.  But, all my clips came in unlinked, too.

    And I updated Pr to 7.0.1, and got the same thing: no crashes, but no linked clips either.  It's possible I did a Select-All and Command-L and linked the clips after I imported the XML the first time, but I'm not sure about that.  Now, I'm really confused.

    Anyway, thanks for staying with me on this, Charles.  I hope this has been of some help.

    Here's a link to the XML in question:

    https://jpc.exavault.com/share/view/1lfq-g5ngeq69-h1db4ilu


    Thanks for the sample file.  With it I was able to reproduce the failure and we are working on a fix.  The failure is happening during the audio level keyframe translation.

    As a not very pretty work around: If you delete the audio level keyframes the import will succeed.

    -Jess

    4 replies

    Participant
    October 14, 2013

    I'm seeing there have been a few staff replies. Any link to a solution?

    Mark Mapes
    Participating Frequently
    October 14, 2013

    We have not released an update since Jesse and Dave chimed in above. A significant update is close to being released. This blog discusses most of the new features (but not bug fixes like the one at issue here): http://blogs.adobe.com/premierepro/2013/09/adobe-premiere-pro-cc-october-2013-release.html

    Participant
    September 5, 2017

    [/PPro11.1.2/releases/2017.03/shared/adobe/MediaCore/MediaFoundation/Src/Keyframe/BezierCore.cpp-61]

    ARGH

    [/PPro11.1.2/releases/2017.03/shared/adobe/MediaCore/MediaFoundation/Src/Keyframe/BezierCore.cpp-61]

    Any recent fixes for this issue?

    Charles VW
    Inspiring
    July 11, 2013

    Jim Curtis wrote:

    Darn, this is bad.  I'm having flashbacks to Pr CS6.0.0.  I keep getting this error, which leads to a crash:

    Premiere Pro has encountered an error.

    [/siree64/releases/2013.02/PremierePro/

    Messanine/Make/Mac/../../Src/Utilities.cpp-780]

    I checked the code, that function is trying to get the framerate (specifically the audio sample rate) from an Audio Clip that doesn't actually exist.

    Since you said this is from an FCP XML, it means that somewhere in the translation of the FCP XML to our own Project XML, something is going wrong and there aren't enough seatbelts to detect the error and so your project is in a bad state.  Sometimes resaving the project can fix itself (I've seen that in some scenarios).  Reading your workaround with the lift workflow, you may want to offline all clips and then perhaps relink the media.

    Participating Frequently
    July 8, 2013

    Having the same problem. I take it you're running on a Mac; I'm running on a PC.  Working with PPro CS6 files that have been converted to CC. Happens when I click on previousely disabled audio clips linked to a video clip that isn't disabled.  I can select them (but not do anything with them) by alt-clicking.  But if I simply click on them ---  the blahblahblaUtilities.cpp-780 error. 

    Adobe -- I hope you're monitoring this.  This needs to be fixed PRONTO!

    Participating Frequently
    July 8, 2013

    Further clarification.  The clips that are problematic in my situation are audio clips from one clip linked to video from a different clip.  IE: I had a clip on the timeline; video and audio. (This was done in CS6 where it worked fine): In CS6, I had delinked the video from its accompanying audio, and replaced the video with a color-corrected version, and linked the audio to the replacement video clip. In CS6 this worked fine.

    Once the project was imported to CC, the problem reared its ugly head.  Clicking on any of the relinked clips, either the video portion or the audio portion, triggers the code mentioned above, and shuts down PP.

    Help!

    Inspiring
    July 8, 2013

    On a positive note, PlannedR, if more than one person is having this issue, it suggests that operator error or corrupt media may be implicated slightly less.  I take it, you weren't having this happen on the same project in CS6?

    I'll add to my list of things that make Pr crash (in this FCP7>PrCC Sequence):

    Adding an audio effect to a clip

    Adding a transition (which triggers a similar error message):

    Premiere Pro has encountered an error.

    [/siree64/releases/2013.02/shared/adobe/

    MediaCore/Backend/Make/Mac/../../Src/Sequence/

    Action/SecuenceAddTransitionAction.cpp-57]

    BTW, I've tried Removing Effects>Volume (previous automation), which I suspected was the offending state.  That worked fine on a few clips.  I was encouraged.  But, then I encountered some clips that even crashed Pr with no effects at all. 

    You've given me an idea to Unlink my clips, and see if that helps.  I'll let you know.

    Inspiring
    July 8, 2013

    If anybody speaks Crash Report, here are the lines up to the end of the Adobe citations.

    Thread 0 Crashed:: Dispatch queue: com.apple.main-thread

    0   libsystem_kernel.dylib                  0x00007fff87dfdce2 __pthread_kill + 10

    1   libsystem_c.dylib                       0x00007fff93fcb7d2 pthread_kill + 95

    2   libsystem_c.dylib                       0x00007fff93fbcb4a __abort + 159

    3   libsystem_c.dylib                       0x00007fff93fbcaab abort + 192

    4   com.adobe.Frontend.framework            0x000000010006728a FE::ApplicationErrorManager::ThrowError(dvacore::config::ErrorLevel, char const*, unsigned int, int, bool, dvacore::config::ReplacementValue const&, dvacore::config::ReplacementValue const&, dvacore::config::ReplacementValue const&, dvacore::config::ReplacementValue const&) const + 202

    5   com.adobe.dvacore.framework             0x00000001002a1962 dvacore::config::ThrowError(dvacore::config::ErrorLevel, char const*, unsigned int, int, bool, dvacore::config::ReplacementValue const&, dvacore::config::ReplacementValue const&, dvacore::config::ReplacementValue const&, dvacore::config::ReplacementValue const&) + 226

    6   com.adobe.Mezzanine.framework           0x0000000105e30a9d MZ::Utilities::GetAudioClipFrameRate(ASL::InterfaceRef<BE::IAudioClip, BE::IAudioClip>) + 189

    7   com.adobe.Mezzanine.framework           0x0000000105a85290 MZ::CreateAudioInfoString(ASL::InterfaceRef<BE::IMasterClip, BE::IMasterClip>) + 304

    8   com.adobe.HandlerInfo.framework          0x000000010a8ba5b7 HandlerInfo::AudioContextLineRender::AsString() const + 39

    9   com.adobe.HandlerInfo.framework          0x000000010a8b9a28 HandlerInfo::ContextLineRender<HandlerInfo::AudioContextLineRender>::DrawLineItem(UIF::DC&, unsigned int, unsigned int&, int, bool) + 72

    10  com.adobe.HandlerInfo.framework          0x000000010a8bb1a9 HandlerInfo::AVClipInfoContext::PaintSelf(UIF::DC&, int) + 105

    11  com.adobe.HandlerInfo.framework          0x000000010a8b374c HandlerInfo::InfoView::PaintSelf(UIF::DC&) + 748

    12  com.adobe.UIFramework.framework          0x0000000104671499 UIF::TabViewImpl::UI_Draw(dvaui::drawbot::Drawbot*) const + 489

    13  com.adobe.dvaui.framework               0x0000000103df42c6 void dvaui::drawbot::InvokeDrawbotFromRegionT<dvaui::ui::OS_View, std::const_mem_fun1_ref_t<void, dvaui::ui::OS_View, dvaui::drawbot::Drawbot*>, NSView*>(dvaui::ui::OS_View const&, std::const_mem_fun1_ref_t<void, dvaui::ui::OS_View, dvaui::drawbot::Drawbot*> const&, dvaui::drawbot::SupplierInterface const&, NSView*, __HIShape const*, dvaui::drawbot::SurfaceInterface*, bool) + 198

    14  com.adobe.dvaui.framework               0x0000000103df0a71 void dvaui::drawbot::InvokeDrawbot<dvaui::ui::OS_View, std::const_mem_fun1_ref_t<void, dvaui::ui::OS_View, dvaui::drawbot::Drawbot*>, NSView*>(dvaui::ui::OS_View const&, std::const_mem_fun1_ref_t<void, dvaui::ui::OS_View, dvaui::drawbot::Drawbot*> const&, dvaui::drawbot::SupplierInterface const&, NSView*, __HIShape const*, dvaui::drawbot::SurfaceInterface*, std::vector<dvacore::geom::RectT<int>, std::allocator<dvacore::geom::RectT<int> > >*, bool) + 577

    15  com.adobe.dvaui.framework               0x0000000103de07d2 dvaui::ui::OS_View::UI_HandlePlatformDrawEvent(dvaui::drawbot::SurfaceInterface*) + 402

    16  com.adobe.dvacore.framework             0x00000001002a1a24 int dvacore::config::ErrorManager::ExecuteFunction<void>(boost::function0<void>*, void*) + 68

    17  com.adobe.Frontend.framework            0x000000010006713c FE::ApplicationErrorManager::ExecuteFunctionWithTopLevelExceptionHandler(boost::function0<int>) + 76

    18  com.adobe.dvacore.framework             0x00000001002a1abc void dvacore::config::ErrorManager::ExecuteFunctionWithTopLevelExceptionHandler<void>(boost::function0<void>, bool*) + 140

    19  com.adobe.dvacore.framework             0x00000001002a362d void dvacore::config::ExecuteTopLevelFunction<void>(boost::function0<void>, bool*) + 125

    20  com.adobe.dvaui.framework               0x0000000103deaba6 -[DVAMacContainerView drawRect:] + 118

    21  com.apple.AppKit                        0x00007fff8dd903bb -[NSView _drawRect:clip:] + 3995