Record your screen, ship a demo. Free and open-source, GPU-accelerated, no watermarks, no subscriptions. Windows, macOS, Linux. Actively maintained.
TypeScript cross-platformelectronffmpegopen-sourceproduct-demorustscreen-capturescreen-recorderscreen-recordingscreen-studioscreencastspeech-to-texttypescriptvideo-editingvideo-editorwaylandwgpuwhisper
docs(testing): log the phone-frame motion blur export check
EtienneLescotf9b51c026052
diff --git a/technical-documentation/testing/manual-e2e-checklist.md b/technical-documentation/testing/manual-e2e-checklist.mdindex 3263e5dd5..4988ad2ac 100644--- a/technical-documentation/testing/manual-e2e-checklist.md+++ b/technical-documentation/testing/manual-e2e-checklist.md@@ -637,3 +637,4 @@ The mask comes from the native compositor (ONNX Runtime + the vendored selfie-se| 2026-09-24 | `claude/zoom-speed-adjustment-fb8abd`, the zoom-pace PR for #683, on `d951e532`; `compositor_view.node` rebuilt from its first commit `cc88c423` (the later motion-blur fix at speed boundaries does not touch these measurements, taken with motion blur off) by `npm run build:native:compositor` (2026-09-24 22:17), ffmpeg DLLs hash-identical to the vendored SDK; renderer rebuilt with `npm run build-vite` | Windows 11 26200 | Partial — no defect | **Zoom pace and speed regions, through the app's real export (`electron . export <project> -o <mp4>`).** Source: synthetic 1920×1080 clip, a 160 px white square centred. Two legacy projects: `plain` at 1× with a 1.25× zoom on [2 s, 3 s] and a 5× zoom on [6 s, 8 s]; `sped` with the whole clip at 4× and the same zooms at 4× the source times. Zoom scale measured on every frame of the 60 fps exports (area-weighted width of the square). New addon: `plain` and `sped` match frame for frame within a maximum scale difference of 0.0001; 1.25× moves 2→98 % in 0.53 s, peak 0.9 e-folds/s; 5× in 1.12 s, peak 2.8 e-folds/s; each zoom reaches 98 % before its region starts and leaves when it ends. Same app build pointed at the 2026-09-13 addon (`OPENSCREEN_COMPOSITOR_VIEW_NODE`): 5× peaks at 13 e-folds/s at 1× and 31 at 4×, where the whole zoom-in takes 0.18 s. **Not covered:** the GUI editor preview (same `plan_frame` as the export, not driven), Full Camera under a speed region and chained zooms (unit-tested only), macOS and Linux rendering. || 2026-09-25 | `claude/ratio-auto-screen-studio-df6b2e` (Auto format), tree of `ace7af33` + `972f8cf3` before the default flip; the test projects state `auto` explicitly, so the flip does not change them. `compositor_view.node` not rebuilt (no Rust change in the PR): the 2026-09-24 22:17 build from `zoom-speed-adjustment-fb8abd`, its whole `bin/win32-x64` directory copied aside and loaded through `OPENSCREEN_COMPOSITOR_VIEW_NODE`; renderer rebuilt with `npm run build-vite` | Windows 11 26200, NVENC export | Partial — no defect | **Auto format, preview geometry and real export.** Preview: the renderer in browser mode (`vite-dev`, `?windowType=editor`), 4:3 fixture `tests/fixtures/sample.webm` with `website/static/video/webcam.mp4` as camera, padding 50, geometry read from the DOM. Fixed 16:9 + top / bottom left 265 px empty per side against 42 px on top; Auto gave a portrait 259×418 frame, square 207×207 camera, 26 px on all four sides. Side by side, padding 0 → 100: frame 2.36 → 1.82, border 0 → 84 px, camera square throughout. Fixed 16:9 side by side gave a 4:5 camera and the block at 80 % of the width, which is the old formula's answer (computed, not re-measured on the old build). Export: `electron . export <project> -o <mp4> --quality source`, synthetic 1280×720 blue screen and 640×480 green camera, wallpaper `#303030`, padding 50, roundness and shadow 0, frame at 1.5 s parsed as PPM. Top / bottom 858×1258, camera 687×686, margins 86/86/85/86; side by side 1240×506, camera 405×406, margins 50 on all sides; PiP 1194×736, screen margins 74/74/74/76. **Not run:** the real Electron editor window (preview checked in browser mode only), the native live preview, the default flip on a fresh recording (unit tests only), a non-English Format menu, macOS and Linux. || 2026-09-25 | worktree `zoom-overflow-layouts-698eb0`, `claude/zoom-overflow-layouts-698eb0` on `ff3c3f51` + the slot-mask change; `compositor_view.node` rebuilt from this tree (`cargo build -p compositor-view-napi --release`), baseline addon built the same way from `ff3c3f51`; ffmpeg DLLs hash-identical to the vendored SDK; renderer rebuilt with `npm run build-vite` | Windows 11 26200, NVENC export | Partial — no defect | **The block layouts' screen slot masks the zoom and the 3D (overflow hidden), through the app's real export (`electron . export <project> -o <mp4>`).** Source: synthetic 1920×1080 `testsrc2` screen and 1280×720 bars webcam, 4 s. Legacy 16:9 projects, padding 50 %, a depth-4 (2.2×) zoom at focus (0.3, 0.6) on [0.5 s, 3.5 s], frame at 2 s. `dual-frame`: the baseline addon spills the zoomed screen under the camera and off the frame; the new one crops it to its rounded slot, camera and gap untouched. `dual-frame` + `iso`: the footage tilts as in any layout and the slot, which stays upright, crops it; where the tilted footage leaves the slot, the wallpaper shows and the shadow follows the visible part. `picture-in-picture`: the whole export is bit-identical between the two addons (PSNR inf on all 240 frames). D3D11 frames through `live::Player`, the preview engine, also checked `vertical-stack`, the `right` preset and the `follow-cursor` camera. **Not covered:** the GUI editor preview (same `plan_frame`, not driven), a window or device frame in a block layout (left unmasked), privacy blur and click impacts in a slot (unit-tested only), macOS and Linux rendering (WGSL validated with naga, Metal not compiled). |+| 2026-09-26 | worktree `motion-blur-padding-issue-11befb`, `claude/motion-blur-padding-issue-11befb` on `1a669c22` (#794); `compositor_view.node` built from this tree (`cargo build -p compositor-view-napi --release`), baseline addon built the same way from `218bdbb0` (`main`); ffmpeg DLLs hash-identical to the vendored SDK; renderer rebuilt with `npm run build-vite`, plus a local, uncommitted pass-through of `editor.frame` in `normalizeProjectEditor` (the v2 CLI path drops it) | Windows 11 26200, NVENC export | Partial — one defect found and fixed | **Motion blur of the framed screen, through the app's real export (`electron . export <project> -o <mp4>`).** Legacy 16:9 project: phone frame, padding 50, motion blur 1, shadow 0.6, a depth-3 zoom on [3 s, 8 s]; sources: synthetic 1920×1080 `testsrc2`, then solid red and solid green to isolate the footage (red/green difference). Static frames: only encoder noise between the two addons. Ramps (60 fps frames 132 and 501): the baseline keeps the shell's rim and bezel razor-sharp around a smeared picture; the new addon smears them with it (87–109k px of shell and shadow change that are never footage). Footage outside the union of the sharp apertures at n−1 and n, +2 px: **1,185 px** on one frame at first (a ~20 % tint over the bezel in the four output corners, where the phone overflows the output), fixed in `1a669c22`, then **0 px over all 55 moving frames**. **Not covered:** the GUI editor preview (same compositor path, not driven), window chrome and laptop/monitor frames on this machine (window chrome covered by the Linux lavapipe test), macOS (Metal not compiled here). |