Premiere Pro crash: An input contract violation has occurred

[williamr95336582]

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??

[williamr95336582]

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.

[ethanframe]

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.

[vjinxile]

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

[R Neil Haugen]

These are user-to-user forums, not official "support" tools. Some of the Product Support staff do spend some time here, but the majority of "us helpers" are simply other users willing to help from our experience.

So, I can't tell from your comments if this is on specific projects, or if you've tried a new project and it happens there also.

Next, what sort of media are you using, and how is it stored? Internal drives, external, and if external, what's the connection ... USB, Thunderbolt, what?

Also, what sort of effects are you using, and has the media been through any third-party apps or plugins?

Those would give us an idea where to start.

Neil

[ethanframe]

Hey -

I uninstalled and then reinstalled and everything worked again.

Let me know how that works for you.

[vjinxile]

Hi Ethan and Neil,

thanks for your replies>

@Ethan: yes i did do the same desinstall and reinstall, problem not solved

Hi Neil,
yes i ve tried new project, with importing only .mxf video &audio files shot from a sony Z series of video cameras, the files are stored on the documents in a project folder from my computert he problems started when i began a new project loading files from internal hard drive and usb 3 external HD drives western digital hard drives, files .mxf .jpg and audio files

i read the forums and it seems that is a recurrent problem over the adobe application, i had thos message also as it crashes> input contract violation has occured

the media are not been through other third party plug in, or apps

this message>

Tanqueray/releases/2016.10/premierePro/HSL/Scr/sequencePlayer.ccp/551/

on forums i ve seen people with similar set up having same problems on teh 27th feb 2017

i also tried to change sync settings also from the adobe cc account website, i juste erased all my sync preferences..

i dont know if related but i was searching type fonts on the adobe typepage and synche new fonts

[vjinxile]

I also filled in the page where there is the official troubleshooting online form, but instead of sending mz info the page crashed on the firefox browser, several times, so i really appreciate you taking the time to send me a reply, i will now reload another project and see if it is also crashing

[vjinxile]

Hi everyone, i went back to work on a current project, saved on external hard drives connected with usb 3 and it seems to work fine, i did encounter crashes and slow/ness on that project, where all the files are located on one folder .mxf .mp4 and audio files . wav, .psd so back to my orgininal problem it seems to occur when starting a new project, whether the files are sourced on the computer itself or on external hard drives usb 3, i hope if it is a bug from the application that the support team will hurry to fix it, with my suscription, i am not a clien important enough to get tech support from the offcial adobe staff, nor can i obtain a number to call, which i did, when i worked for a company, on the inside of the company, i understand that adobe had priorities, but i am upset, at the way, we small customer *only individual licenses for 2x computer are treated...i hope this can be fixed in the future. and the bug i reported is still open and not resolved., Thank you very much for reading this, kind regards, Lise

[R Neil Haugen]

You should be able to get the "Live chat" support method, and if you do, please ask as soon as you get someone responding for the "Video Queue". Product Support manager Kevin Monahan (an experienced editor and teacher of editing himself) always suggests that anyone with PrPro use the Video Queue to get through to support staff with at least some experience rather than the normal generalists.

The type of drive and connection can at times help ... say a Samsung T3 through a USB3 connection has been shown by expert Bill Gehrke to work very well for sustained read/write as needed by PrPro. Many early generation SSD drives and most spinning drives via USB3 do have a slow enough connection that although ... usable ... it's not optimal.

Neil

[vjinxile]

THanks Neil, thanks for the advice, i will, and thanks for the tip for the hard drive. I will post the answer when i have the problem resolved. Kind regards to you Neil and all of the people putting time in running those forums, you re an inspiration and life-saver, thank you sincerly.

[vjinxile]

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 michael van metre

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

[vjinxile]

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

[vjinxile]

Same issue of crashing when on software only renderer

[R Neil Haugen]

Realistically, Apple hasn't upgraded the mobo on their Big Mac in several years. Three complete New Product Rollouts from Cupertino, with absolutely nothing for the desktop computer end. Apple is into devices ... content ... now. Their CEO has stated publicly he has no idea why someone would buy a desktop these days. And they show no interest in creating computers that work with other people's stuff. (They make FCPx, if you run Apple, you're supposed to use that, and not whine about somebody else's programs.)

Hence, even in perhaps the most Macophile post-processing group, colorists ... the talk is on about how to move away from the Mac to PC/Linux in order to get a computer that can actually handle the load they need it to carry.

In aisle-way discussions at NAB the last couple years, software & hardware vendors have been talking of the change in attitude from the wondrous days of yore ... when they got pre-release builds to test with their software/hardware in plenty of time to make changes of their own, and the Apple staff were interested in hearing about things they needed to tweak in the OS before rollout. Now ... they still get a 'test' release, but much closer to the actual launch without time to make any serious testing of say your complete software or the 50 hardware bits you make, and ... if you call and say this bit needs modification, the attitude is ... dude, why you whining at me? Go fix your own cr*p.

A sadly very different experience.

So ... expecting Apple to modify their computers to work with anything else is probably like wishing you could walk to the moon. Thrilling to think of ... but ain't happening. Even as a long-time PC user who has trouble figuring out how to use a Mac, I find this sad, as I so prefer competition, multiple possibilities, many different approaches to anything.

Neil

[vjinxile]

Hi Neil, thank you for your infos and comments, i ve been following the NAB from far as  i don-t live on the same continent. Through Kevin Monahan, who escalated the case, the tech support contacted me yesterday and we could resolve the issues. Well of course.., i still have the AMD graphic card in my machine, but until i get the option to change it or Apple released some upgrade on their graphic cards, for now i will keep my project surgically operated on the advices i recieved to best work with the hardware i currently have. Regarding your comments and having briefly workd with premiere pro on a Mac Pro, last year , which did crash the machine by the way (it was a large project) and note being able to finance a mac pro and an updated screen for colorimetrie, i took my chances on an Imac. I would also consider a shift into linux, in the future. For now i will make work the best of what hardware i have. Kind regards and thank you again for you help, Lise

[R Neil Haugen]

Always happy to be of help. Every one of us has different processes, needs, and resources ... but we all need to get work out.

Neil

[Mitch Drummond]

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

[AnthonyEpes]

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

[Saxy2826395144hl]

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