I will now answer my own question...
I found this on a whats new and changed page, But I must say rather than it being tucked away at the bottom of the page this information would have been more usefull at the top of the page in red letters. "BEFORE YOU UPDATE PLEASE NOTE, etc, etc..."
Is there any information on when the patch update is coming?
known issues that we are intending to fix in an update very soon
There are two bugs that we are intending to fix in an update within a couple of weeks:
- remaining RED (.r3d) performance issues: The After Effects 13.1 update includes fixes for performance and pixelation issues with RED (.r3d) files, but some performance issues still exist for a subset of RED files, including those from Epic cameras. We have a fix for these remaining cases in development and testing now.
- internal verification error when using effects with no properties, such as Knoll UnMult
Rather than delay the release of After Effects 13.1, which includes many fixes, we determined that we should include these two fixes in a patch update as soon as possible after After Effects 13.1 was released.
I am having same issue here. And like you, i missed it at the bottom of the page.
Now i need to deliver some work and i can't open my projects.
Did you find a way to open your project?
Is it possible to rollback (without having to reinstall plugins)?
Thank you in advance!
My way around it wasn't that elegant I'm afraid.
I opened up a new project and imported my old one into it, put on Caps Lock and then removed unmult from the relevant layers. It still came up with the error as I opened each one so I had to click the error closed with the return key whilst attempting to turn off the layer in the comp.
I also thought about removing the unmult plugin from the effects folder in Applications/Adobe After Effects CC 2014/Plug-ins/Effects to see if this just removed it throughout but I didn't try that, so you could give that a quick go.
Either way I had to key out the Black rather than the easier unmult method.
I hope the fix is out soon, I use it loads!
The other way would be once you've imported the project into a new fresh project you could save this out as CC12 and open in the previous version, as long as you've not used too many CC2014 specific effects ...
Hope this helps :-)
Thank you very much for your answer thebobwolf your solution works (i did try to import into a new project before i posted but i didn't think about the caps part so thumbs up for you)
I started doing it has you said and it was working. But at some point i had to give up.
I had so many multimattes with knoll in them and so deep compositing that i had to just give up on keying everything and reinstalled older version again.
i hope this gets fixed soon cause Knoll is just way too handy to pass on it.
Cheers and thanks again!
Thanks Szalam, downloaded and installed (at the right price too!) ;-)
We expect to have a fix out in 1-2 weeks.
Thanks Todd, appreciate you answering.
Luckily the VCP is a great substitute.
Loving the new interface BTW, The blue is great and I like the new anchor points too! ;-)
I have just published a free script to try to work around this UnMult issue until the underlying bug is fixed:
It's testing well here, but please let me know if it works for you or if you run into any issues.
script is not working for me at all still getting the errors
Oh I realized why- I'm not using UnMult im using Mask Avenger from aescripts which has a property-less "Mask Render" effect as part of its' stack
im using Mask Avenger from aescripts which has a property-less "Mask Render" effect as part of its' stack
I'm sorry, but I'm not sure how much I can help here. I can't think of an alternate way to replace BAO's Mask_Renderer functionality. Any ideas?
Red Giant has just released a version of Knoll UnMult that works around this problem. You can get a new version of Knoll UnMult from Red Giant Support and swap that for your existing plug-in.
We're still on track to fix the underlying bug on our side and get the fix out in about a week.
THANK YOU! I might just leave Unmult alone now that I have this one.
And I think the posts of other Adobe enthusiasts are right: THIS bug should have been listed as a warning at the VERY top of the page...I have a project that I need to open that I cannot open because of this bug. This isn't nice.
I'm going to remove the Unmult and hopefully all it tells me is an effect is missing then I can replace it with the video copilot plugin. -I really would have appreciated very plain, upfront warning about this bug.