Skip to main content
CJB_001
Inspiring
September 28, 2017
Answered

ERROR (17 ::45) unable to decompose matrix

  • September 28, 2017
  • 1 reply
  • 11897 views

Hi

I've run into this error suddenly out of nowhere, when I click ok the error message comes up again, it's infinitely there so I can't access my file to change settings and I don't have an auto-save for a previous version. Please advise.

I'm on Windows 10, After Effects is up to date.

    This topic has been closed for replies.
    Correct answer CJB_001

    I fixed the situation by importing it into another project.

    Prior to that I could not check the effects, as I mentioned already. The message would not let me access my file, I click ok and the message pops up again in less than half a second, had to force shutdown to open Ae again and could not get in my file prior to the fix.

    1 reply

    Mylenium
    Legend
    September 29, 2017

    Without knowing what you actualyl do, what goes on in your comp and so on nobody can tell you anything. From damaged footage to specific effects going bonkers to the endless AE disk cache bugs this could be anything. To salvage your project start by enabling capslock to completely suppress rendering and then disable al lthose potentiall offending things - check your effects, flush the caches etc..

    Mylenium

    CJB_001
    CJB_001AuthorCorrect answer
    Inspiring
    September 29, 2017

    I fixed the situation by importing it into another project.

    Prior to that I could not check the effects, as I mentioned already. The message would not let me access my file, I click ok and the message pops up again in less than half a second, had to force shutdown to open Ae again and could not get in my file prior to the fix.

    Michelangelo De Cia
    Known Participant
    January 25, 2021

    I had the same problem, using Mocha AE... After creating the tracking data and applying it to a null, when linking an object to that null I would get that error. After restarting AE everything went fine, this problem might have something to do with the scale X and scale Y values from Mocha, I noticed those values were huge...