Select by Minimum Vertices Count Add-On
Gabriel Moro
by Mark Stead
Add-on for Blender 5.1 by Mark Stead. Files: .exr.
5.0· 15 Gumroad ratings
Free / pay what you want
Get it on GumroadSold by Mark Stead. Check current pricing, license and Blender compatibility on Gumroad before purchasing.
Blender compositing node group for temporal denoising of animations. This is used to reduce the flickering or shimmering between frames of an animation. This node group requires multi-layer EXR files as input containing these layers: Vector (required) Denoising Data (recommended) Environment (when applicable) The node group will intelligently combine multiple frames of animation and reduce temporal noise across the frames. This will allow the the spatial denoiser (OpenImageDenoise) to achieve a higher quality result. Version History V1.3, 9th February 2026, tested on Blender 5.1 (requires Blender 5.1+) Fix for edge case if any of the Threshold configuration values were set to 0.0 exactly. The intended behaviour is that when a Threshold is set to 0.0 it requires that the images are identical for that Hue, Saturation or Value channel, otherwise the alternate image will be ignored. Conversely if the threshold is set to 1.0 then maximum latitude is given to blend images essentially disabling the comparison of that colour channel. The behaviour of the node group changed when a Threshold was set to 0.0. At that point it then behaved like the threshold was set to 1.0. This was triggered by a change in the Map Range logic in Blender 4.4+. It is not considered a bug though - I was relying on undocumented behaviour when the source range collapses to zero. V1.2, 5th December 2025, tested on Blender 5.0 Alert: A Blender 5.0.x compositing bug has been identified which breaks the temporal denoiser. The only work around is to use Blender 5.1 Alpha. Fix for the removal of the Texture node in the Blender 5.0 Compositor, which was used to inject Texture Coordinates data. Now there is a dedicated Image Coordinate node available instead. On further investigation there were changes to the functionality of the Coordinates node in Blender 4.4 and 4.5 (to do with the Texture node group only supporting a Line Style and not a Brush). I'm not confident that the V1.1 node group was functioning properly on these versions. You should work entirely on V1.2 with Blender 5.0 or use V1.1 with Blender 4.3 and earlier. Finally the image output is slightly different between V1.1 on Blender 4.3 and V1.2 on Blender 5.0. You only really notice if you perform an image difference and crank up the intensity. This is probably related to Blender 5.0 being a major upgrade. V1.1, 1st September 2024, tested on Blender 4.2 (compatible with previous versions) Fix for when the source images have transparency (even if the alpha is 1.0). In V1.0 it was using the alpha channel from the previous/next image even when that image was cropped due to being offscreen. Now it always uses the alpha channel from the current image, by simply reordering the inputs to the Mix Colour node. V1.0, 6th May 2023, for Blender 3.5+ Initial release Additional Info Check out my YouTube video for more details, including a temporal denoising comparison between OptiX and my node group. Create a Blender project for compositing, and append the Temporal Denoising node group (this download). Load your EXR image sequence in the compositor, and duplicate twice. Set the Offset value so that the current, previous and next frames can be accessed. Connect the Combined and Vector layers to the Temporal Denoising node group. Use the Hue/Saturation/Value Threshold values to restrict blending of dissimilar areas (shadow/non-shadow or simply where the lighting changes significantly). A threshold value of 1.0 disables that threshold - forcing it to blend regardless of the corresponding Hue/Saturation/Value in the images being compared. Often the Value Threshold must be set quite low (e.g. 0.05) to avoid shadow problems. (Which is counter productive for reducing temporal/spatial noise.) The Max Weight setting controls the mix balance between current frame and the next/previous frames. The default value of 0.3 indicates that the next/previous frames can have up-to 30% contribution (each), and the current frame will have at-least 40%. You could use 33.3% for an equal weighting, or say 25%/50%/25% to reduce any ghosting artefacts. You have the option of performing spatial denoising (Denoise node) before or after temporal denoising. It is designed to be used in conjunction with spatial denoising, because using temporal denoising only will not denoise as thoroughly. See this post for more details on the compositing configuration. https://blog.stead.id.au/2026/02/combining-temporal-denoising-and.html Best results will be achieved if you are able to render Shadows separately. It may be possible to do this using the Shadow Catcher in simple scenes. The Temporal Denoising (Debug) node group has tools for visualising motion vectors. At this point the node group is designed for denoising across three frames, but it could be extended to work across more frames. Limitations Status: Resolved The motion vectors calculated by Blender are incorrect when the camera focal length is animated. The problem was raised in issue #69731 and is flagged as a known limitation of the code. This means that if you animate your camera zoom, then the calculations for temporal denoising will be wrong and lead to significant ghosting. If focal length animation only applies to a small portion of your animation, you may be able to rely on spatial denoising only for this section possibly with additional render samples, and only use temporal denoising for other parts of your animation. When I get time, I will be looking at the Blender code and seeing what can be done. I've committed a fix to the Blender codebase which was merged to the Blender 4.3 release branch on October 15th 2024.
Gabriel Moro
Ahmed Ali
Theo Pantazi