Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

After Effects: Unable to allocate 0.000MB of memory.

Engaged ,
Nov 28, 2018 Nov 28, 2018

I you are seeing this every time you close a project I believe it is an issue between AE 2019 and BlackMagic Desktop Video Drivers 10.11.2 and later. Running 10.11.1 will fix the problem, as will sticking with AE 2018. BM have been notified and hopefully will be providing a fix. I would be interested to know if anyone else has seen this as we've had it on two Win 10 systems and on Mac also.

2.1K
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Contributor ,
Nov 28, 2018 Nov 28, 2018

I installed Desktop Video 10.11.4 yesterday and just started having this After Effects error today.

I am on a Mac v10.13.6

2.7 GHz 12-Core Intel Xeon E5

64 GB 1866 MHz DDR3

AMD FirePro D700 6144 MB

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Contributor ,
Nov 28, 2018 Nov 28, 2018

It does it when I close a project or quite AE.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Contributor ,
Nov 28, 2018 Nov 28, 2018

If I deselect "Blackmagic Playback" in the After Effects preferences, the problem goes away...so does my HD client monitor.

But at least I don't have to deal with the errors and lockups.

Hope this helps.

BM.png

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Apr 04, 2019 Apr 04, 2019

Wow, finally. This has been bugging me since I updated AE about a month ago. But I really like to use my Sumo19 with AE. Since a lot of people use Blackmagic devices, it would be nice to hear something from Adobe about this. It has always worked before, why did it stop working now?

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Apr 04, 2019 Apr 04, 2019
LATEST

I didn't read the whole thread before I posted this. Sorry, seems to be a Blackmagic-issue. And since I cannot delete this post at the time...

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Dec 05, 2018 Dec 05, 2018

I have the exact problem with both AE CC 2018 and 2019 after upgrading to Desktop Video 10.11.4 (with Decklink 4K Extreme output).

Rolling back to 10.11.1 resolved the issue.

Appears to be AE-specific, I did not have the issue with Premiere or Resolve.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Dec 05, 2018 Dec 05, 2018

PS - I am running MacOS Sierra 10.12 which is NOT supported by Desktop Video 10.11.4. Could have also been a contributing factor...

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Dec 19, 2018 Dec 19, 2018

Hello

I have the same problem in windows environment... Tried 10.11.2, 10.11.3  and now riunning 10.11.4.

When I close after effects, it wrecks havoc on the entire system for 30s.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Engaged ,
Dec 19, 2018 Dec 19, 2018

10.11.1 will fix it for you. Please email Blackmagic support as they are still in denial about it. I just get the usual 'We're not seeing it here' line.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Contributor ,
Dec 20, 2018 Dec 20, 2018

This was my response from Blackmagic:

"There could be a couple things at play. One would be that the UltraStudio Express is a legacy item that we no longer test. The other would be rolling back to 10.11.1 and seeing if that works for you."

I haven't tried going back to 10.11.1 yet. Hopefully I will have time to do so soon.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Engaged ,
Dec 20, 2018 Dec 20, 2018

Nothing to do with your Express. We use a combination of Internal Intensity 4k and the older external Intensity Pro thunderbolt for the mac. This is a software, not hardware issue.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Contributor ,
Dec 20, 2018 Dec 20, 2018

I just uninstalled 10.11.4 and reinstalled 10.11.1 and everything is great now! 

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Mar 18, 2019 Mar 18, 2019

Blackmagic releases desktop v. 11 on march 7th. Alas, the problem persists on my side.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Apr 04, 2019 Apr 04, 2019

Same here. Updating to Blackmagic Desktop Video v11 does not seem to solve the problem. I will also try to roll back to 10.11.1

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines