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.
6.0: worker threads per area, screenshots without waiting for the GPU, encoder warning
5.2: measured crawl cycle, vertical motion search, standard watch, resolution match, General tab, Vulkan
Screenshots and Recording: the clipboard, and a toast that shows the file
Ctrl+F10 had no mention at all. Clicking the toast after a screenshot or
a recording opens Explorer with the file selected; the page says how long
it stays and why it runs on a thread of its own.
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.
Document the second grab point for screenshots
A screenshot used to be one thing: the picture, at source resolution, taken
between the first draw pass and the interface. The Recording tab now has a
switch that moves the grab to the far side of that line, and the page has to
say where the line is, what GrabBackBuffer does with the back buffer, and the
two things that change as a result -- window size instead of source size, and
SDR always, because the scRGB back buffer is refused rather than converted by
untested maths.
The JPEG XR paragraph no longer claims that screenshots never need ffmpeg. AVIF
sits three paragraphs below and needs it, which the same page had already said.
The two page descriptions on Home now match what those pages have grown into.
The long version: one page per feature, and what the code does