Screen share 19 follow-up: run the MediaFoundation H.264 encoder on Windows hardware #229

Open
opened 2026-11-12 07:57:43 +00:00 by charles · 0 comments
Owner

Follow-up of Screen share 19 (#166): the MediaFoundation H.264 encoder (crates/fluxer-voice/src/mf_encoder.rs, feature mf-encoder, off by default) is built and type-checked, but has never run: no Windows machine with a GPU was available, and the Windows CI runner has none. Per the plan's exit rule the feature stays off and Windows ships software-only (spec §16 Q2) until this is done.

To do, on Windows 10/11 with an NVIDIA, an AMD and an Intel GPU if possible:

$env:FLUXER_HW_ENCODER_TESTS=1
cargo test -p fluxer-voice --features mf-encoder --test mf_encoder -- --ignored --nocapture
$env:FLUXER_LIVEKIT_TESTS=1   # with a livekit-server reachable (FLUXER_LIVEKIT_URL)
cargo test -p fluxer-voice --features mf-encoder --test livekit_interop -- --ignored --test-threads=1 screen_share_pattern_arrives_for_each_encodable_codec
  • mft_found_and_encodes_pattern, keyframe_on_request, rate_control_within_20_percent pass, and the pattern arrives over H.264 through the pre-encoded path in the interop test (exit criteria: keyframes on request, rate within 20 %).
  • Record the results per vendor in spikes §6 (docs/superpowers/research/2026-11-11-screenshare-spikes.md), including the unverified points listed in §6.4 (ForceKeyFrame latency, mid-stream bitrate changes, NV12 in system memory vs a D3D11 device manager, SPS/PPS inline).
  • If they pass: turn the feature on for Windows release builds (packaging, Screen share 30) and add a Windows CI step that at least builds --features mf-encoder so the code does not rot. If not: say why in §6 and leave it off.

Seen on: branch screenshare-19-spike-hw-encode-windows.

Follow-up of Screen share 19 (#166): the MediaFoundation H.264 encoder (`crates/fluxer-voice/src/mf_encoder.rs`, feature `mf-encoder`, off by default) is built and type-checked, but has never run: no Windows machine with a GPU was available, and the Windows CI runner has none. Per the plan's exit rule the feature stays off and Windows ships software-only (spec §16 Q2) until this is done. **To do, on Windows 10/11 with an NVIDIA, an AMD and an Intel GPU if possible:** ```text $env:FLUXER_HW_ENCODER_TESTS=1 cargo test -p fluxer-voice --features mf-encoder --test mf_encoder -- --ignored --nocapture $env:FLUXER_LIVEKIT_TESTS=1 # with a livekit-server reachable (FLUXER_LIVEKIT_URL) cargo test -p fluxer-voice --features mf-encoder --test livekit_interop -- --ignored --test-threads=1 screen_share_pattern_arrives_for_each_encodable_codec ``` - `mft_found_and_encodes_pattern`, `keyframe_on_request`, `rate_control_within_20_percent` pass, and the pattern arrives over H.264 through the pre-encoded path in the interop test (exit criteria: keyframes on request, rate within 20 %). - Record the results per vendor in spikes §6 (`docs/superpowers/research/2026-11-11-screenshare-spikes.md`), including the unverified points listed in §6.4 (ForceKeyFrame latency, mid-stream bitrate changes, NV12 in system memory vs a D3D11 device manager, SPS/PPS inline). - If they pass: turn the feature on for Windows release builds (packaging, Screen share 30) and add a Windows CI step that at least builds `--features mf-encoder` so the code does not rot. If not: say why in §6 and leave it off. Seen on: branch `screenshare-19-spike-hw-encode-windows`.
charles added this to the Screen share milestone 2026-11-12 07:57:43 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
charles/fluxer-native#229
No description provided.