5.7.0: measured pixel grid, pixel rebuild, colour edge rebuild, demodulator on the cleaned line
Video standard and composite filter: 5.5.1 changes
Deinterlacing and composite filter: 5.5.0 changes
Composite filter: the moving-texture check in 5.4.1
Extended history
Composite filter: gate back to the 5.2.1 window
Composite filter: gate asks the centre line on its own
Composite filter: gate on a carrier-exact window over three lines
5.2: measured crawl cycle, vertical motion search, standard watch, resolution match, General tab, Vulkan
The program is called qBlank Every page now says the name the program carries from 4.0 on. What still says CapView says it deliberately: the shared section names the camera is found through, the migrator, and the sentences that are about a version which really was called that. Updates gains the section the rename needed -- the migrator shipped under the old file name, the release asked for by repository number and asset label, the executable that renames itself on its first start, and settings recognised by their contents rather than by their file name. Home, Building and Configuration point at it.
Add the new comparison images to both filter pages Deinterlacing gets the close-up: a subject that barely moves stays sharp while the background behind it tears, which says what combing is better than the before/after in the README can. The composite filter page gets a picture for colour shimmer and one for bandwidth restore, and its existing caption now describes the replaced image.
Record that the cable question and the signal type are one list And that the two filters which survive on S-Video and component describe themselves as noise reduction there, rather than as a composite filter with pieces missing.
Write up the cable question, and what hangs on it
Measure the vertical demodulator, and rule it out Isolating the crawl over 26 frames of a parked scene -- the mean is the picture, each frame minus the mean is the artefact -- makes the comparison possible that no single-frame control could support. Both estimators are linear, so each can be run on the two separately: what it produces on the crawl-free mean is damage, what it takes off the isolated crawl is benefit. The whole gain of a vertical comb sits on the row +- 1 tap, which is the other field, because this pass runs before the deinterlacer. Put the fields out of step the way motion does and that tap goes from the best of four to worse than the filter it would replace. It helps only where the four-frame average already has the crawl. Also records the four single-frame controls that had to be thrown away, and the movement mask that quietly discards the pixels the crawl lives on.
Write up the three filters added in 3.3 The composite page gains a section each for following the movement, restoring bandwidth and applying the chroma blur only where needed, with the proof that motion compensation cannot remove dot crawl, the measured response that shows why the bandwidth lift is built from triangles and not boxes, and a table of what every standard resolves to. The artefact table gains a column naming the control that handles each one.
Bring the wiki up to 1.9
What the grey ring actually was, and the field that went missing
The long version: one page per feature, and what the code does