You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
always have a small area showing the black when edit the recording #1747
This issue appears to be related to a rendering change in PR #1674 (merged 2026-03-21), which coincides with the version range you mentioned (0.4.81+). That PR changed the WebGPU render pass loadOp from "clear" to "load" in apps/desktop/src/utils/webgpu-renderer.ts (lines 302 and 415). The PR review comments specifically flagged this could cause stale/garbage pixels on the first frame or after certain events since loadOp: "load" skips clearing the framebuffer.
Looking at the screenshot, the black area appears at a consistent location which suggests the composite shader may not be covering the full canvas in certain scenarios during editing/playback.
apps/desktop/src/utils/webgpu-renderer.ts:302,415 - the loadOp settings for both render paths
crates/rendering/src/ - Rust-side rendering pipeline if the black area persists in exported videos
If the black area only appears in the editor preview (not in exported videos), the fix is likely reverting to loadOp: "clear" with a clearValue as originally suggested in the PR review. If it appears in exports as well, the issue may be deeper in the rendering pipeline.
This is tracked by #1737 (Windows recording self-exclusion not yet implemented), so we're closing this as a duplicate. Thanks for the report, further discussion can continue over there.
Activity
linear commentedon Apr 22, 2026
CAP-686
tembo commentedon Apr 22, 2026
This issue appears to be related to a rendering change in PR #1674 (merged 2026-03-21), which coincides with the version range you mentioned (0.4.81+). That PR changed the WebGPU render pass
loadOpfrom"clear"to"load"inapps/desktop/src/utils/webgpu-renderer.ts(lines 302 and 415). The PR review comments specifically flagged this could cause stale/garbage pixels on the first frame or after certain events sinceloadOp: "load"skips clearing the framebuffer.Looking at the screenshot, the black area appears at a consistent location which suggests the composite shader may not be covering the full canvas in certain scenarios during editing/playback.
Related issues:
Relevant code:
apps/desktop/src/utils/webgpu-renderer.ts:302,415- theloadOpsettings for both render pathscrates/rendering/src/- Rust-side rendering pipeline if the black area persists in exported videosIf the black area only appears in the editor preview (not in exported videos), the fix is likely reverting to
loadOp: "clear"with aclearValueas originally suggested in the PR review. If it appears in exports as well, the issue may be deeper in the rendering pipeline.cantonadong commentedon Apr 22, 2026
it appears in exports as well
richiemcilroy commentedon Aug 3, 2026
This is tracked by #1737 (Windows recording self-exclusion not yet implemented), so we're closing this as a duplicate. Thanks for the report, further discussion can continue over there.