Changes between Version 20 and Version 21 of DenoiseExamples

Timestamp:

Jun 9, 2024, 5:51:25 PM (2 years ago)

Author:

uncoder

Comment:

[minor] typos and formatting. Clarification regarding split-screen comparison.

DenoiseExamples

@@ -42 +42 @@
 Prior to applying a denoise filter, a user is encouraged to separate and preview the individual planes and identify whether the source of the noise is in any particular plane.
 
-For example, when an analog source is digitized, there may be a disproportionate amount of noise in the chroma plane.  The following will produce a 4x4 mosaic containing `{original, luma, Cb, Cr}`, similar to the tools such as [https://www.neatvideo.com/support/tutorials/nv5/building-noise-profile Neat Video noise-preview].  Frames are converted to yuv444p (or yuv444p10le for 10-bit) in order to remove chroma-subsampling of a yuv422p or yuv420p source, where chroma-planes are encoded at a lower resolution.
+For example, when an analog source is digitized, there may be a disproportionate amount of noise in the chroma plane.
+
+  The following command will produce a 4x4 mosaic containing `{original, luma, Cb, Cr}` planes, similar to plane preview-scopes in tools such as [https://www.neatvideo.com/support/tutorials/nv5/building-noise-profile Neat Video noise-preview].  Frames are converted to yuv444p (or yuv444p10le for 10-bit) in order to remove chroma-subsampling of a yuv422p or yuv420p source, where chroma-planes are encoded at a lower resolution.
 
 {{{#!shell
@@ -51 +53 @@
 }}}
 
-Some denoice filters allow the user to select which planes are processed.  Planes are typically decimal notation, which may be confusing to a new user.  This notation is not unique to `avuy` formats, it is also used for `abgr` formats.
+Some denoise filters allow the user to select which planes are processed.  Planes are typically decimal notation, which may be confusing to a new user.  This notation is not unique to `avuy` formats, it is also used for `abgr` formats.
 
 {{{
@@ -64 +66 @@
 === Visualizing and comparing filters #Visualizing
 
-The visual effect of a denoise filter is subjective.  A user is encouraged to compare denoise filters.  The following command will compare `null` (no-operation) filter on the left of the player window with the `hqdn3d` filter (with default properties) on the right of the center-line.
+The visual effect of a denoise filter is subjective.  A user is encouraged to compare the visual effects of denoise filters.
+
+  The following command will provide a split-screen comparison between `null` (no-operation) filter on the left of the player window with the `hqdn3d` filter (with default options) on the right of the vertical center-line.  The same methodology can be used to compare the visual effects of two different denoise filters, or two different options of the same filter.
 
 {{{#!shell
@@ -76 +80 @@
 }}}
 
-It is possible to extend the above command to cycle through the `{ combined, luma, Cb, Cr }` planes using FFplay's ''"cycle video filters or show modes"'' using the `w` key.
+  It is possible to extend the above command to cycle through the `{ combined, luma, Cb, Cr }` planes using FFplay's ''"cycle video filters or show modes"'' using the `w` key.
 
 {{{#!shell
@@ -94 +98 @@
 === Benchmarking the relative performance of denoise filters #Benchmarking
 
-The performance of denoise filters varies depending on a number of factors, including algorithm, patch size, number of planes being processed, hardware etc.  A user can measure and compare the relative performance of a denoise filter and the selected options using the [https://ffmpeg.org/ffmpeg-filters.html#latency_002c-alatency `latency`] benchmarking filter.
-
-For example, here is a comparison of the relative performance of the `hqdn3d` and the `nlmeans` filters across 1000 video frames.  These comparisons and values are not recommendations, but are to demonstrate how algorithm and options selection can have a major impact on performance.
+The performance of denoise filters varies depending on a number of factors, including algorithm, patch size, number of planes being processed, hardware etc.  A user can measure and compare the relative performance of a denoise filter and the selected options using the [https://ffmpeg.org/ffmpeg-filters.html#latency_002c-alatency latency] benchmarking filter.
+
+  For example, here is a comparison of the relative performance of the `hqdn3d` and the `nlmeans` filters across 1000 video frames.  These comparisons and values are not recommendations, but are to demonstrate how algorithm and options selection can have a major impact on performance.
 
 {{{#!console