Recording: hardware encoders get the picture on the GPU
Describe encoding inside the process
- Recording: threads, muxer queue, closer, what the encoder is told,
mix and microphone clock, what in-process costs.
- ffmpeg: loading the libraries, the shared build download, staging,
updates within the header major, two frame probe.
- Encoder settings: options as name and value, qp on NVENC, AV1 times four.
- Audio, Building, Screenshots, HDR, Home: follow-ups.
Recording in 4:4:4, and the format model behind it
Recording: one YuvFormat for both -pix_fmt, with the layout table.
Encoder settings: the 4:4:4 switch and which encoders can.
High dynamic range: readback rings per format, shared when equal.
ffmpeg: the 4:4:4 probe, its cache keys, and current function names.
Document the P010 fix in the clean pass
Point file references at the files the 5.2 split created
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.
Finish reading the remaining pages against the source
The rest of the sweep. Five more corrections, all found the same way -- opening
the file the page cites instead of trusting the page:
Updates named RemoveLeftovers() and RestartIntoNew(). The functions are
CleanUpPreviousBuild() and RestartIntoNewBuild().
Audio named tapOverflows(). It is tapOverruns(), on the ring rather than on the
engine.
Colour range had RGB reading offset 0 with a step of 1 over all channels.
LumaLayout() reads green -- offset 1, step 3 or 4 by subtype -- because green
carries most of the brightness at a third of the reads.
High dynamic range still claimed screenshots never need ffmpeg, four paragraphs
above AVIF, which does. Same sentence as the one on the Screenshots page, same
fix.
Building said 1.6 MB. The executable is just under 2 MB.
Recording, Encoder settings, Scaling and sharpening, Virtual camera and
Translations were read line by line and needed nothing.
The long version: one page per feature, and what the code does