Show only Search instead for. Did you mean:. This effect requires GPU acceleration. Follow Report. Community guidelines. Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more. Ann Bens. Adobe Community Professional , Mar 27, Mar 27, Are you using Immersive effects on non immersive footage? Community Beginner , Mar 27, Mar 27, VR chromatic abberation and lens distortion so yeahEdit:Okay i moved the adjustment layer with effects outside of the nest, it;s working now, thanks.
Jump to latest reply. Correct answer by Ann Bens. In Response To Ann Bens. Restart your PC for the new driver to take effect. You can drag this effect to the top of the list, or change the general order of all the effects to see if it makes a difference. While you might regularly update Premiere Pro and all the default effects, you may forget to update the third-party plugins and effects as well, which could cause compatibility issues and trigger random errors.
You can try updating those, if you use any, and test the issue. Hopefully this article helps! If you have any questions or suggestions, please feel free to leave a comment down below.
As a technical writer at Driver Easy, Katie writes solutions for daily tech issues and pro tips on games. You can try shifting something to an adjustment layer or nesting, to help break it up.
Maybe you want to render and replace to bake some of the effects out so you're not trying to do all of that processesing at once - or going back to my first statement, even playing with the order the effects take place. If you have a GPU installed, and can use any option other than "software only" in the Project settings dialog for "Mercury Accleration" The message you are getting comes up also from comments from engineers here when there is insufficient vRAM available for operation at hand.
If you have 10 effects applied to a clip, several of which use the GPU, you may simply be overloading too many GPU-intensive effects for processing at once. So that is why the above comment suggested nesting.
That breaks the processing into chunks as far as PrPro and the hardware are concerned, processing the stuff within the 'nest', then processing separately the stuff outside the nest. And something I see fairly often here, is people that will apply say video noise reduction, Warp stabilizer, and instances of Lumetri to a clip. And then, they speed-ramped it all. So for that kind of work, I suggest as do many: apply the noise reduction typically Neat or the Warp stabilizer. Then do the next step or two, then nest the clip, then the last one.
Even if the effect in question can be rendered by GPU it won't be in this case. More about it here:. Hence the message. Adobe Support Community. Turn on suggestions. Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.