SCREEN RECORDING FORMAT STUDY
Published 16 October 2026
https://screenbuddy.xyz/screen-recording-format-study

Six delivery files from the same ten-second excerpt (seconds 2 through 12)
of /demos/windows/hero-zoom.mp4. This is a re-encode of existing ScreenBuddy
Windows demo footage, not a capture, application-export-speed or equal-quality
codec benchmark. There is no audio. Each pair matches dimensions and target fps.

Input SHA-256:
216e42e1accaadd856e81043aefe32b94c419eec04d4cbe9d4447a2945dd7585

MP4: libx264, CRF 23, slow, yuv420p, fast-start.
GIF: 256-color palette, diff palette statistics, Sierra 2-4A dithering,
rectangle difference mode. Scale: Lanczos.

Reproduction requires Node.js 22+ and FFmpeg with libx264, palettegen and
paletteuse. The original run used FFmpeg 6.1.1 (Gyan essentials Windows build).
Encoder builds can change bytes; inspect the reported version and output hashes.

From an empty working folder:
1. Create public/demos/windows and content directories.
2. Download https://screenbuddy.xyz/demos/windows/hero-zoom.mp4 into
   public/demos/windows/hero-zoom.mp4 and check the input hash above.
3. Download https://screenbuddy.xyz/research/recording-formats/reproduce.mjs
   into the working folder.
4. Run: node reproduce.mjs /absolute/path/to/ffmpeg --study-only
   On Windows, pass the absolute path to ffmpeg.exe.

Outputs are written under public/research/recording-formats. Measurements,
settings and hashes are written to results.json and content/recording-format-study.json.
GIF durations use frame-delay metadata; the 8 fps GIF lasts 10.01 seconds because
GIF time is represented in centiseconds. MP4 durations use track metadata.

Source footage and this example are separate from the 20-second editorial reel.
The reel combines existing October Windows recordings (zoom, callout, 3D editor)
without altering the application UI. Full shot provenance is available at
https://screenbuddy.xyz/press/windows-reviewer-brief/provenance.json

Questions: support@screenbuddy.xyz