Which is why learning how to work Neat's parameters is so important. I've been around similar issues with Resolve.Īnd Neat can have similar effects as far as 'smoothing' something to the point macroblocking occurs.
This forum is primarily user to user.īut this is most certainly not a Premiere-only issue. Feel free to post that bit with full details and images on their Premiere Pro UserVoice site, as that is where the devs log all posts into their system. it blends them into more similar pixels than they were before.Įven at "0", I would imagine there is still some blurring math being processed. Blurring intentionally removes the details, meaning. Details are the differences in pixels at neighboring sites. Why? What does blurring do? It removes detail data. How to get some blurring but not get any macroblocking. Participate in their forums and discussions.Ĭamera blur is often a problem child in those discussions. I teach pro colorists how to work in Premiere when they have to, and of course, follow very closely their work in Resolve. H.264 and HEVC use different patterns and algorithms or whatever the specific process is called, so it is expected the results will not be duplicates albeit at different data rates.Ĭamera blur is a major cause of image degradation in long-GOP encodes, both in Premiere and in Resolve. Lastly, I have observed this problem on a variety of HEVC footage (422 10-bit, 420 10-bit, and 420 8-bit) and two different workstations (specs below).Īnybody else noticing this or have some insight into what's going on? The first image just has Lumetri applied, while the second also has Camera Blur but with the percent blur set to 0 (saturation has been boosted in both to help show the issue). I’ve also included a couple of still frames for reference – notice the blocky color artifacts on the second image, especially in the purple areas to the left and right sides of the frame.
And while it’s a bummer that Neat Video for Premiere isn’t really usable with HEVC footage, I found that if I dynamic link to Ae and use Neat Video there, the issue isn’t present. Out of these, Neat Video’s noise reduction plugin is the most relevant to my workflow – but I wanted to show that this bug applies to both native and 3rd party effects.
It essentially looks the same as if using MPE Software Only.Įffects such as Warp Stabilizer don’t cause this, as I don’t think they are in the same processing pipeline, but I have found that the following do: From what I can tell, if an effect is not natively GPU accelerated, the image will be degraded by color noise/artifacting and perhaps a color shift. I’ve noticed what appears to be a bug in how Premiere renders H.265/HEVC footage after applying certain effects.
0 kommentar(er)
