Skip to main content
thereARNOlimits
thereARNOlimits
Participant
May 9, 2018
Question

Input Contract Violation when copying layers

  • May 9, 2018
  • 1 reply
  • 2791 views

Hey there,

quite the annoying little thing happening out of a sudden

an Input Contract Violation error

10594a8e73d4860366aa6a143d1d114a.png

followed by

a4a622a2c236a2a399d4dd873028dbda.png

Things that lead to this behaviour:

copying a layer, in any composition in the project.

Steps I already did:

  • purged cache
  • restared
  • reinstalled AE
  • tried on different machine - same error

Happening on OSX 10.12.06 with the newest version of AE installed (15.1.1), happened out of a sudden in one project, other projects are not affected.

Of course that happened on a project that is time sensitive, I mean, sure, could not be the other way round.

Anyone got an idea?

Thanks for you help.

This topic has been closed for replies.

1 reply

Jose Panadero
Community Expert
Jose PanaderoCommunity Expert
Community Expert
May 9, 2018

What you can check is:

- Use the Disk Utility, located in Applications > Utilities to repair permission problems.

- Enter into After Effects Preferences > Media and Disk Cache > Clean Database & Cache.

- Maybe your codec is not supported in version 15.1.1. Remember that Adobe has dropped support for previous Quicktime codecs. Have you tried with version 15.0.1?

- I remember that sometimes, when the video files have audio tracks that are empty (silence). This happened to me a long time ago and the solution was to remove the empty audio tracks in the video file.

thereARNOlimits
thereARNOlimitsAuthor
Participant
May 10, 2018

Thanks for your input.

- The Disk utility is a good idea, haven't thought of that

- cache, as stated hast been cleared

- the layers that I tried to copy were textlayers, and no exotic codes were used in the comp

- silence audio tracks are a problem - I see, good to know, I shall keep an eye out for that

thanks for your ideas, miraculously after working yesterday with the project, calling it a night and starting it again today, the problem is gone...

NO idea why. Like NO. IDEA

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