Screen and window capture, replay, system-wide shortcuts
- New page Screen-and-window: Desktop Duplication, Windows.Graphics.Capture,
the options, the exclusive-fullscreen notice
- Recording: replay in memory or on disk, slots given back by fence, frames
left out instead of repeated, recording resolution
- Shortcuts: every action can have a system-wide binding
- Encoder settings: all encoder chips
- Screenshots of the new tabs
Ctrl+Enter toggles borderless
F3 shows and hides the toolbar
Add The main window page
Window size, Shift keeping the shape, borderless and the red taskbar dot
while recording. Linked from Home and Shortcuts.
Shortcuts: the keys 5.0 added, and bindings stored by name
The defaults table was missing Ctrl+F10, F11, F12 and Shift+F12, and the
code excerpt still showed twelve actions and a virtual-key number. It is
split into rebindable and fixed now, with Ctrl+F and the double click in
the second half.
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.
3.6.0: the format that follows the signal, and measuring the range again
Document the pipeline delay in place of frame age
The overlay row was renamed and now measures to the present rather than to the
start of the draw. Latency gets the new definition, the measured figures for
both deinterlacing modes, and an explicit list of what sits outside the span --
including the point that on 480i the card's own field capture is the largest
term in the whole chain and the one nothing in here can see.
The settings window's 0.5 to 1.6 ms was measured under the old definition and
is marked as such rather than restated, since it has not been measured again.
The colour round waits for the decoder, not for a deadline
Document what 3.2 changed
The two passes through the candidate list with the measurements behind the
0.6 s, the result a hand-started search now shows and every way it can end,
the optional crop per picture size, and the profile that picks itself from
the detected standard with the four things that stop it.
Document what 3.1.1 changed
Four things, across five pages.
The standard search now says on screen why it is running and which step
of how many it is on, so "Automatic video standard" gets a section on
what the two lines mean, why the colour round counts steps rather than
standards, and where the reason comes from.
The same page gets the manual search on F7: the blind spot it exists for
-- colour that is wrong rather than missing, which no threshold here can
see -- why the request is a deadline rather than a flag, and the three
cases it refuses. "Source and signal" names that blind spot as the third
limit of automatic mode and points at it; "Shortcuts" lists the key,
counts twelve actions instead of eleven, and says why F7 sits next to F8.
"Recording" gets the source-change split under Splitting: the two
thresholds, why the frame size is rounded before comparing, why the rate
is compared undoubled, and what the 1.5 seconds are for. The
out-of-bounds read underneath it is written down as the reason the split
is not optional.
"Encoder settings" gets the bitrate and quality pair under rate control,
and why the bitrate slider became logarithmic: linearly, the range this
hardware lands in took nine percent of the track.
Document how the video standard is found, and what every threshold is worth
New page: the two stages (the decoder settles the line count, the picture
settles the colour system), the candidate table, every threshold with the
measurement behind it, the lock times, the starvation rule, the retry
table, and the limits. Includes the round that ran on a 95 % black
picture and why a round now needs 10 % of the frame lit before it is
allowed to decide anything.
Source and signal loses its stale summary -- 250 ms poll, 0.6 s settle,
five candidates -- and links to the new page instead.
Shortcuts gains Shift+F5 and F8, and the enum snippet matches the eleven
actions that actually exist.
Cropping and geometry: the three ways to trigger Detect, and why a crop
is dropped rather than re-measured when the source changes size.
Rewrite the virtual camera page for the DirectShow filter
The page described a Media Foundation frame server that no longer exists. It
now describes what 3.0 actually ships, and why the argument that led to Media
Foundation in 1.9 was wrong: a source filter runs inside the consumer, so the
Global namespace and the privilege that goes with it are simply not needed.
New sections cover the source being passed through 1:1, the continuous ranges
that let a consumer ask for something in between, what OBS, Discord and the
browsers each end up with, the generation-named frame section, the seqlock and
the retry that fixed it, one wake event per consumer, and the consumer table.
Two things are recorded that were measured rather than reasoned about:
- The 8K120 collapse. A single torn read used to end the attempt, which at
large sizes turned ordinary contention into a black picture that never came
back: 94 frames delivered, 0 of them fresh. With three attempts it is 239 of
269.
- The producer half, exercised for the first time. A temporary per-user
registration got past the "installed?" gate and let CapView's own
VirtualCamera feed a real consumer off the SA7160, at native, at 720p30 and
at 640x480@15.
That per-user registration is written up as its own section, because it works:
the camera enumerates through the ordinary system device enumerator with no
administrator anywhere. 3.0 does not ship it, since nothing has shown that OBS
and Discord accept a registration without a FilterData blob, and a camera that
silently fails to appear is a bad thing to learn after release. It is the first
candidate for 3.1.
Building, Home, Updates and Shortcuts follow the same rename from "media
source" to "filter". Shortcuts also loses a wrong claim: the overlay does not
show the camera counters, Settings then Recording does.
The long version: one page per feature, and what the code does