Highlighted

Failure related to GPU-enabled effects

Explorer ,
Oct 24, 2017

Copy link to clipboard

Copied

Hello,

after updating to CC 2018, I noticed one issue. During the preview of quite simple project, I keep getting this error:error.png

What I have in particular in the project:
Few compositions>Inside them there is one image (3000x2000), which scales up using Transform Effect to fill the comp size.

Comp size: 1280x720

System info:

system.png

Is there any chance to get rid of it, without going to Software Only mode?  OR, the GPU simply has not enough memory to handle the GPU acceleration?

Thank you up front!

Most Valuable Participant
Correct answer by Mylenium | Most Valuable Participant

Your GPU is simply too old/ inadequate for this stuff.

Mylenium

Views

12.6K

Likes

Translate

Translate

Report

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

Failure related to GPU-enabled effects

Explorer ,
Oct 24, 2017

Copy link to clipboard

Copied

Hello,

after updating to CC 2018, I noticed one issue. During the preview of quite simple project, I keep getting this error:error.png

What I have in particular in the project:
Few compositions>Inside them there is one image (3000x2000), which scales up using Transform Effect to fill the comp size.

Comp size: 1280x720

System info:

system.png

Is there any chance to get rid of it, without going to Software Only mode?  OR, the GPU simply has not enough memory to handle the GPU acceleration?

Thank you up front!

Most Valuable Participant
Correct answer by Mylenium | Most Valuable Participant

Your GPU is simply too old/ inadequate for this stuff.

Mylenium

Views

12.6K

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Oct 24, 2017 0
Most Valuable Participant ,
Oct 24, 2017

Copy link to clipboard

Copied

Your GPU is simply too old/ inadequate for this stuff.

Mylenium

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Oct 24, 2017 3
Explorer ,
Oct 24, 2017

Copy link to clipboard

Copied

Thanks for your reply. Basically, updating to a newer Macbook would solve the issues?

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Oct 24, 2017 0
Adobe Employee ,
Nov 07, 2017

Copy link to clipboard

Copied

Hi Tom,

A larger GPU can help with GPU accelerated effects, yes.

Thanks,
Kevin

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Nov 07, 2017 1
New Here ,
Nov 15, 2017

Copy link to clipboard

Copied

Hi Kevin,

I have the same problem, but with the Glow effect on a simple PNG-logo. I have to turn of 

I have a Dell XPS 15 9560 with 32 GB RAM, Nvidia GTX 1050 with 4 GB, 7th Gen Intel Core i7 7700, 1Tb SSD etc.

Is this a bug or is this simple effect a very heavy effect that this PC can't handle. Because I have done much heavier and more complicated stuff and it has been handling that before.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Nov 15, 2017 1
Explorer ,
Nov 15, 2017

Copy link to clipboard

Copied

That is exactly what my concern is about.

Whether it is a bug somewhere, or just an effect which GPU can't make it through successfully.

As I used the Transform effect with simple scale IN value change, it is far far away from complexities which occur in other projects, including the same CC distortion effects.

Looking at your rig build specs, I assume it can't be just a bottleneck of a system.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Nov 15, 2017 0
Adobe Community Professional ,
Nov 16, 2017

Copy link to clipboard

Copied

Instead of buying a new computer, try changing your project settings to render software only without the hardware acceleration. It should help.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Nov 16, 2017 3
Explorer ,
Nov 16, 2017

Copy link to clipboard

Copied

It helps and I already went towards this workaround, but it doesn't answer the question why actually it is happening

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Nov 16, 2017 0
Adobe Community Professional ,
Nov 16, 2017

Copy link to clipboard

Copied

It's due to the small amount of memory on your GPU. If you'd rather keep GPU acceleration on, you'll need a system with a more powerful GPU.

Now, in this case, it's likely the large layer you mentioned. I'm kind of confused why a layer that huge needs to be scaled up to fit a composition that is significantly smaller than it is...

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Nov 16, 2017 0
Explorer ,
Nov 16, 2017

Copy link to clipboard

Copied

In that image scaling situation, I need to have two different scaling controls, where layer transforms does action1, and Distort Transforms - action2 for the same transformation.

Ozzumagi has significantly better GPU, but it does not help with Glow effect either. Is it not enough as well? Thank you!

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Nov 16, 2017 0
New Here ,
Nov 17, 2017

Copy link to clipboard

Copied

I just talked to a friend in class, and he said that he had the same problem but with the "write on"effect. He have a really good PC with a good and new GPU with alot of GPU-memory, 4 GB.

I think that this is a bug that need to be fixed.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Nov 17, 2017 0
Adobe Community Professional ,
Nov 17, 2017

Copy link to clipboard

Copied

You have to upgrade the OS to 10.13.1 and install the NVIDIA web driver first and then update the CUDA driver. NVIDIA was very slow to update the drivers. I have a slightly older Mac and have not had any problems with upgrading the drivers. I published this a few weeks ago:. NVIDIA CUDA driver update for OSX 10.13.1

The correct answer is not that the GPU is too old, you just have the wrong drivers installed.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Nov 17, 2017 2
New Here ,
Dec 26, 2019

Copy link to clipboard

Copied

Thank you so much rick your literally a life saver, nothing harder than losing your render near deadline, 
I've updated my driver and my CUDA, restarted my PC and everything works now. 
I couldn't thank you enough.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Dec 26, 2019 0
Community Beginner ,
Nov 30, 2017

Copy link to clipboard

Copied

I think this is BS that is not that old of a card and people are having this issue with brand new cards. It seems to be a driver and update issue.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Nov 30, 2017 0
Community Beginner ,
May 15, 2018

Copy link to clipboard

Copied

This absolutely ISN'T down to old cards etc. I'm using Windows 10 Pro with 3 x 980ti cards and I've never had this issue before. I've been rendering this project at 4K for weeks and all of a sudden, the day before the final deadline, it now decides it's not going to render because of this weird error. Has anyone else had this issue before?

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
May 15, 2018 0
Community Beginner ,
May 15, 2018

Copy link to clipboard

Copied

Ok, so I worked out what caused the issue for me - the invert effect. How on earth is it possible that such a simple effect is using up almost 6gb of GPU memory? On top of that I duplicated the comp (it was being used for a luma matte) and applied the invert effect and its worked perfectly. It literally makes no sense.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
May 15, 2018 0
Adobe Community Professional ,
May 16, 2018

Copy link to clipboard

Copied

That sounds like a bug! Please file it!

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
May 16, 2018 2
New Here ,
Apr 04, 2019

Copy link to clipboard

Copied

since today I also got this error. I guess it is related to the update to 16.1 yesterday. Before I worked in the same project without any troubles for weeks.

I have a NVIDIA Titan x with 12GB GPU Ram so I can't believe this is the problem, also it is a rather simple Project with only some pictures and repetile/curves/fastboxblur etc on it, nothing too fancy.

Win10, 32gb Ram, everything updated....

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 04, 2019 0
New Here ,
Jul 11, 2019

Copy link to clipboard

Copied

hi i have the same problem except that i have a rtx2070, it was just working then i got the same exact message,

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jul 11, 2019 0
New Here ,
Jul 11, 2019

Copy link to clipboard

Copied

never mind because all of a sudden it just started working after a while

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jul 11, 2019 0
Community Beginner ,
Sep 26, 2019

Copy link to clipboard

Copied

Hi,

 

I had the same issue and I have a great GPU with 8GB of memory. I closed and reopened the project, went to File > Project Settings and changed the Mercury Software Only back to GPU and that fixed it. Hope this helps someone!

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Sep 26, 2019 0
Participant ,
Dec 30, 2019

Copy link to clipboard

Copied

Same issue here, out of the blue...
Just tried changing from CUDA to Software saving reopening  and now have a black frame...
Changed to CUDA, again plain black...

GTX1060 6GB and task manager shows just 1% GPU utilization.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Dec 30, 2019 0
Community Beginner ,
Jan 12, 2020

Copy link to clipboard

Copied

Just encountered the same problem. As workaround I switched from CUDA to OpenCL and the problem went away. If anyone has solutions would like to hear.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jan 12, 2020 1
Community Beginner ,
Aug 07, 2020

Copy link to clipboard

Copied

 

Hello, same issue here with a last gen low-mid range Nvidia GTX 1650 Super 4 GB in a pretty simple project at FHD resolution. Nothing crazy just shapes and effects, with all third-party effects disabled it won't render with GPU, only with software (CPU). 

In Windows's Task Manager in the Performance tab there's a GPU tab and I can see the 4 GB memory being eaten right away. Also that memory seems to not be flushed between two frames, so yeah it gets filled and that's the end. Not sure that more VRAM would save the day because it would be filled just a few frames later, I guess. 

 

Josh's idea about OpenCL would be a cool workaround if somehow CUDA fails, but in AE 2020 on PC I don't have OpenCL in the rendering options : there's Mercury software and Mercury GPU (CUDA). 

 

In my project I found the culprit for the GPU error : a bitmap transformed "upscaled" to a resolution of 3840x3840 pixels. My GPU with 4 GB VRAM won't render that because a lack of memory. Seriously how much VRAM do you need to render a square 4k frame : 8 GB, 12 GB, a GPU cluster? Disappointing and good to know for my next projects. 

We had lack of RAM, we now also have lack of VRAM. AE needs to be able to manage "out of cores memory", which is system RAM used for GPU tasks. At least we would be facing only one well known limitation : RAM. 

 

About my final AE render : before the GPU memory failed me it took 12 hours to render "without the finishing effects : glow, grain, RGB separation". Now on CPU "software" WITH these effects enabled it took 2 hours... There's not been much more in my project than a switch from GPU to CPU, between these 2 renders : these numbers are really not in favor of the GPU "acceleration" here.

Something must be seriously off and in any case benchmarking CPU vs GPU might always be a good idea, NOT thinking that GPU acceleration is always faster...   

 

Back to CPU "software" rendering for now. So much for these "GPU accelerated effects" in AE and plugins. 

 

Cheers. 

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Aug 07, 2020 0
Explorer ,
Aug 12, 2020

Copy link to clipboard

Copied

I totally agree, there needs to be an out-of-core-feature. I have just ran into the issue as well with a 1660 Super with 6GB and the most current driver (451.77), rendering a 4K x 4K image sequence. Unfortunately there are effects which only work in CUDA mode like the VR Converter, so switching to CPU only is not a solution for me...

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Aug 12, 2020 0