Skip to content

History / Recording

Revisions

  • Recording: lossless encoders, unfiltered, larger buffer

    @NuclearMeltdown NuclearMeltdown committed Oct 20, 2026
  • Recording: 4:4:4 goes to NVENC as CUDA frames

    @NuclearMeltdown NuclearMeltdown committed Oct 20, 2026
  • Document the recording sources The microphone section becomes the list of sources: inputs, output devices, system sound. Track layout per source, every source on the recording's clock, and the smaller mentions across the pages.

    @NuclearMeltdown NuclearMeltdown committed Oct 19, 2026
  • Recording: GPU frames measured again, CPU is lower

    @NuclearMeltdown NuclearMeltdown committed Oct 19, 2026
  • Recording: hardware encoders get the picture on the GPU

    @NuclearMeltdown NuclearMeltdown committed Oct 19, 2026
  • 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.

    @NuclearMeltdown NuclearMeltdown committed Oct 19, 2026
  • 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.

    @NuclearMeltdown NuclearMeltdown committed Oct 19, 2026
  • 6.0: worker threads per area, screenshots without waiting for the GPU, encoder warning

    @NuclearMeltdown NuclearMeltdown committed Oct 18, 2026
  • 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.

    @NuclearMeltdown NuclearMeltdown committed Sep 23, 2026
  • 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.

    @NuclearMeltdown NuclearMeltdown committed Sep 8, 2026
  • 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.

    @NuclearMeltdown NuclearMeltdown committed Aug 31, 2026
  • The long version: one page per feature, and what the code does

    @NuclearMeltdown NuclearMeltdown committed Aug 24, 2026