[kyzer1023]

Use D3D11 VideoProcessorBlt to scale resized WGC frames into pooled GPU targets. The software encoder reads back only the output-sized texture, and initialization or blit failures retain the existing CPU scaling fallback.

Synthetic texture benchmark medians (3 runs × 12 frames), Ryzen 7 8745HS / Radeon 780M, Windows:

Resize	CPU scale call before	GPU scale submission after	Software output path before	Software output path after
1920×1080 → 1280×720	14.468 ms	0.263 ms	15.411 ms	3.568 ms
3840×2160 → 1920×1080	49.872 ms	0.300 ms	52.077 ms	9.836 ms

Synthetic output matched the CPU scaler within 1 channel value maximum error in both cases.

Validation: cargo fmt --all --check, cargo check -p cap-recording, and cargo clippy -p cap-recording -- -D warnings passed. The D3D11 benchmark/pixel test passed. cargo test -p cap-recording had three existing AMF instant-mode scenario failures; the 50+ segment case also fails identically on upstream main at 60ef63232.

Confidence Score: 5/5

The PR appears safe to merge, with no actionable new issues found.

Summary

This PR scales resized Windows capture frames with D3D11 and keeps CPU scaling as a fallback.

• Resized Windows capture frames scale on the GPU.
• Wayland display queries wait longer for compositor replies.
• Hyprland screenshot checks follow the active monitor size.
• Camera CI setup loads the video modules it needs.

No actionable new issues or repository-rule violations were found.

_{Reviews (6) · Last reviewed commit: "fix: allow busy Wayland compositors to e..." · Reviewed by Greptile}

[kyzer1023]

@greptileai review

[vercel]

@kyzer1023 is attempting to deploy a commit to the Cap Software Inc Team on Vercel.

A member of the Team first needs to authorize it.

[kyzer1023]

@greptileai review

[kyzer1023]

@greptileai review

[kyzer1023]

@greptileai review

[kyzer1023]

@greptileai review