Skip to main content
W
williamr95336582
Participant
February 27, 2017
Question

Premiere Pro crash: An input contract violation has occurred

  • February 27, 2017
  • 4 replies
  • 12418 views

Hi everyone! I am trying to finish my thesis but I keep encountering an error that shuts down my project while editing, moving or deleting elements from my timeline. Any help would be greatly appreciated! Thus far, I have tried cleaning the cache and restarting.

(Mac/ Adobe Premiere Pro CC 2015.3)

"Adobe Has Encountered an Error

GoodBuddy/releases/2016.03/shared/adobe/MediaCore/Backend/Src/Sequence/Action/TrackInfoChangedAction.cpp-88"

in addition, I get a dialogue box that says "An input contract violation has occurred"

Does anyone have some advice to save my project??

This topic has been closed for replies.

4 replies

S
Saxy2826395144hl
Participant
July 5, 2023

1. Please close app, go to 'Run' ( Windows Key + R) , then type %appdata% , in Folders, go to Adobe > Common > Delete the folders named Media cache & Media cache files

2. Open Premiere Pro restoring default settings and plug-in cache. To do this, hold down Shift-Alt (Windows) or Shift-Option (Mac OS) while the application is starting. Release the Shift-Alt keys or Shift-Op

    Mitch Drummond
    Mitch Drummond
    Known Participant
    July 27, 2018

    I have found that this can be caused by a damaged project file. To fix this created a new project then using the media browser import the old project into the new project. This fixed the issue I was having

      A
      AnthonyEpes
      Participant
      October 21, 2018

      Tanks man.  this worked for me.  You saved me!!!!

      ethanframe
      ethanframe
      Participant
      March 1, 2017

      Dude, this same thing is happening to me.  I just purchased Adobe Premiere Pro CC 2017 less than a week ago, finished my first video on Sunday and everything went smoothly.  Now attempting to start on my second and I am getting the same exact error.  I drag my first clip to the timeline and all is well, then whenever I attempt to bring a second clip and join the two, the program craps out and reports the "Input contract violation."  This is always on a brand new project. I can't even get started.  I've tried in both the "Assembly" and "Editing" views as well.

      Mine reads: "Premiere Pro has encountered an error. [/Tanqueray/releases/2016.10/shared/adobe/MediaCore/Backend/Src/Component/ComponentFactory.cpp-109]

      (I'm running a MacBook Pro, Mid 2014 with macOS Sierra 10.12.3)

      @Adobe any help would be mightily appreciated.

        V
        vjinxile
        Participating Frequently
        March 3, 2017

        I have the same problem, pls help this is really serious, i have tried all the steps clean media cache etc what do i say to my clients..and if i loose those projects &jobs how do i pay rent, ADOBE SUPPORT pls help

        V
        vjinxile
        Participating Frequently
        March 4, 2017

        i found this post on looking on some forums> wondering if that is the issue, if it is, why is this not put forward, i wld have got another computer, Mac Pro was just over my budget, Also i have been editing on Premiere pro ok until now, well with crashes and some issues but it has been getting worse until now i cant start a new project as it continually crashes when wanting to make a new sequence

        From Forum on creative Cow> answer of a long thread>

        Re: will the iMac 5K Retina's AMD Radeon graphics card be a problem for Premiere Pro CC and AE???

        by

        on Jul 8, 2016 at 7:48:58 pm

        I have the same computer, late 2015 iMac 5K Retina, 32 GB Ram, AMD Radeon R9 M395X GPU.

        After extensive research and trouble shooting my conclusion is the Radeon R9 is not compatible with Premiere Pro CC. Adobe has confirmed that they have not tested the card and will not give a time frame as to when. Very disappointing to purchase a "high end" iMac to work in 4K only to have it not work decently at all. I'm looking into swapping out the GPU for one that is compatible with CC and will still run on the iMac, but this is doubtful.

        I have been in contact with both Apple and AMD in addition to Adobe. Currently there is no work around. Apple needs to stop selling this configuration as the end all NLE work station when it is not compatible with Premiere, and Adobe needs to get busy and test this GPU and make it work. This has been a known issue for well over a year and a half. Solutions are:
        1- wait it out
        2-go with a PC
        3-try a swap out of the GPU-doubtful
        4-edit with FCP X

        RTo Adobe Support Team out there what is your opinion on that, and users too?

        below sceenshots of some of the issues, which i ve written about


        So Now i ve retried starting a brand new project saved on my computer folder documents and without importing any sources i tried creating a new sequ from menu above, and application crashed with same Tanqueray msg..on render engine Open CL *not Metal*

        it is real bad, guys and gals out there, also read the bugs release given a few months ago, i know you all work very hard to deliver these applications to us, but pls do take these issues and complaints seriously and try to fix the problem sooner, cheers Lise

        W
        williamr95336582Author
        Participant
        February 27, 2017

        So I copied the section of my timeline (about 25 minutes in length) that was crashing when I worked with it and pasted it into another part of the timeline. Whenever  I worked within the faulty timeline- things would crash without any rhyme or reason - other than that it would seem to happen when I moved or deleted more than a minute of information on the timeline.

        After copying the faulty timeline I deleted the original potion slowly - a few seconds of information at a time - saving often - until only the copy of my work remained. It seems that I am now able to work - but I am still concerned as I don't know what caused this problem, and I don't really know how to fix it.

        Terms & ConditionsAccessibility statement
        Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices