feat: PyVNCServer 3.3 — native DXGI metadata and encoding interoperability - #13
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PyVNCServer 3.3 — DXGI metadata + interoperability
This PR implements the v3.3 capture/interoperability milestone.
Native DXGI metadata
IDXGIOutputDuplication::GetFrameDirtyRectsandGetFrameMoveRectswhile the DXCam frame is still acquiredUltraVNC / encoding interoperability
Adds real TCP/RFB end-to-end regressions that keep one connection open while changing the client's advertised encoding set.
The CI matrix parses the actual wire payload for:
Raw → RRE → Hextile → Zlib → ZRLE → Tight → RawThere is also an explicit RRE → Tight regression matching the failure mode previously observed with UltraVNC. These tests validate both the rectangle encoding ID and the corresponding payload framing/decoding.
DXCam contract protection
dxcam>=0.3.0.[dev,performance]Diagnostics and docs
benchmarks/benchmark_dxgi_metadata.py3.3.0Run the real Windows diagnostic with:
Validation
Current GitHub Actions result is fully green:
[performance]contract: ✅Remaining manual validation before release
A GitHub-hosted Windows runner can validate the DXCam ABI but cannot provide a representative interactive desktop/GPU capture workload. Before merging/releasing v3.3, run the DXGI metadata benchmark and an UltraVNC session on a real Windows desktop, especially window movement, scrolling, Tight and RRE switching.