Srishti from tech support was showing me how to change the setting from Open CL to Software rendering.
In Adobe Premiere go to
File -> Project Settings -> General -> Video Rendering Playback
Set this to Software only.
Then it'll ask to delete all the Preview files, say yes.
Now everything works, only it is much slower...
But hey, at least it works!
1 person found this helpful
There are problems rendering Lumetri using OpenCL. Switching to software mode or changing to nVidia are the current solutions.
1 person found this helpful
Sorry for the troubles. I have a few questions.
- Was there a specific Lumetri effect that caused the problem or multiple effects? Which one(s)?
- Did you apply the Lumetri effect to the clip or on a adjustment layer?
- Did flickering only occur on the clip with the Lumetri effect and in a specific place or was is random?
- Which drivers did you use?
Thanks! You information will hopefully help this issue get resolved.
@Jim Sinon: Oh what a bummer.... I hope Adobe/Lumetri will support AMD cards, soon... Thanks for letting me know!
Thanks for the response.
I use two Lumetri effects:
- Warm Midtones
- Dream 1
Both applied directly to the clip of raw footage which is in the sequence that gets exported. There is actually one sequence, where I fixed some of the footage putting it into another sequence first, then the sequence into the final sequence that gets exported.
All my clips have both Lumetri effects applied to them. The flickering took place randomly, but it would definitely get worse the more I attempted to render (the first 2 to 3 no problems, on the 3rd or 4th maybe a few flicker seconds in the middle, any more would be 100% flickering - if any flickering or only like a green solid...)
Now Shrishti from tech support insisted the problem was within the sequence. And that kind of made sense, because once we successfully rendered one sequence, there would be no more trouble rendering it a second time, even if the program was already in flicker mode. And also for some reason while we were playing around with it when one sequence failed, even after restarting Media Encoder, it would fail again afterwards.
However last night after it failed I would just try again, doing 2 at a time and it would be successful.
Now I say it failed, but of course no errors no nothing... Just as in the result didn't look the way it was supposed to.
Also I want to mention that especially when I kept it running after it failed (meaning you leave it runnning, producing only garbage) the fans of my computer kept running louder and louder. Not sure if it was the GPU or CPU. Rigth now it keeps rendering in Software mode and the fans are barely louder than under normal usage.
I use the AMD catalyst driver which I downloaded from here:
While Shrishti was trying a couple of different settings at one time the screen went dark, as it came back on there was a message coming from the windows tray, saying the display driver had crashed, but recovered. One time I also received a bluescreen message, which I will try to attach to this post.
well i guess it doesnt have too much information on there other than... what is that? a memory address?
This happened I believe after the first attempt with the updated driver (I updated from 13.3 to 13.4 )