[META] Road to v2.0.0 Release

[ehfd]

Will be consistently updated. Entries without assignees are all open to pull requests. Vibe coding is welcome as long as functional validation is correct.

Checkmarked entries are currently in Pull Requests. Will be unchecked if it gets closed without merging, and will be struck out and moved to the bottom if merged.

Tier 1: High Priority, blockers for v2.0.0

Tier 2: Moderate, preferred to land in v2.0.0

Tier 3: Roadmap, but not necessarily for v2.0.0

Done

• Expose CBR for WebSockets and CRB as an option for WebRTC mode. - Assignee: @PMohanJ
• [META] Implement chunked transport for WebRTC DataChannel / Image Clipboards #74 - Assignee: @PMohanJ
• TURN-REST subproject does not conform to specifications #172 - Assignee: @ehfd
• Use one port for Data and WebSocket Streams, and embed an internal asyncio web server instead of NGINX (NGINX can be used to make things faster, optionally, but Selkies is self-contained otherwise). - Assignee: @PMohanJ
• Integrate the web components inside the Python wheel, not as a separate directory that has to be installed. - Assignee: @ehfd or @PMohanJ
• Instead of erroring with no audio server, restore server-side --disable_audio CLI option or automatically detect no PulseAudio server #147, expose Add an option to configure server latency pcmflux#4 to Selkies - Assignee: @PMohanJ
• Bring NVENC with X11 back to working state in containers with multiple GPUs; Contact me for details, although it's likely I'll do it myself. - Assignee: @ehfd.
• Fix NVENC encoder dropping a lot of frames with Windows Chromium D3D11VideoDecoder - Consult settings in https://github.com/selkies-project/selkies/blob/7dd6a93065332e5b3fe48fe5e5eb911a91f82746/src/selkies/legacy/gstwebrtc_app.py#L257-L938. The decoder initially starts from baseline profile and changes to high (open Details in [META] Road to v2.0.0 Release #227 (comment)).
• Integrate Python-Xlib code into Selkies and remove that repository (removes the ugly workaround in pyproject.toml). Abide by the LGPL license so that such code is only connected with Selkies using import statements, and leave the license file in the subdirectory.(Reduce reliance on external libraries / certain upstream packages are unmaintained #85) - Assignee: @ehfd
• Coalesce fragmented environments into Selkies and incorporate externally dependent (pixelflux, pcmflux) environment variables into settings passed to dependencies (pixelflux, pcmflux) from Selkies. Change SELKIES_AUTO_GPU (and the AUTO_GPU fallback) so that an alternative value to true, so e.g., nvidia -> nvidia / amd -> amdgpu,radeon / intel -> i915,xe,gma500, etc., are mapped, and the first GPU in each vendor is chosen instead of the first GPU overall (make the input case-insensitive). Note that you should map to non-x86 GPUs as well as necessary.
• Refer to https://docs.kasm.com/docs/how-to/manual_intel_amd/index.html so that DRM KMS devices are mapped correctly in both LinuxServer.io and Selkies containers, when e.g., /dev/dri/card0 is occupied by IPMI without an additional /dev/dri/renderD* device, and the correct mapping for GPUs is instead /dev/dri/card1 to /dev/dri/renderD128. Utilize the /sys/class/drm/ interface, which is also available in containers.
• [Enhancement] Test client CPU and GPU consumption through MediaStreamTrackGenerator/VideoTrackGenerator linuxserver/docker-baseimage-selkies#47 and Improve polyfills for MediaStreamTrackProcessor and MediaStreamTrackGenerator/VideoTrackGenerator support sealskin#7 in tandem
• Deduplicate PixelFlux C and Rust code. Optimize PixelFlux C/Rust to Python frame delivery and prevent copying from C to Python; zero-copy until the websockets library sends the memoryview. This could improve a potential AV1 implementation in the future, due to AV1 having a lot more number of packets per frame than H.264. Find a way so that https://github.com/linuxserver/pixelflux/blob/master/example/screen_to_browser.py doesn't have to make a new bytes with raw_data_from_cpp = bytes(result.data[:result.size]) and also apply it to Selkies.
• Keyboard keystrokes continue to be held when packets are lost by congestion or unstable connection / Improve the last bit of keyboard latency overall while accommodating unstable connections #145
• Most of [FEAT] The Road to WebRTC linuxserver/docker-baseimage-selkies#46
• Reimplement congestion control mechanisms.
• Identify more zero-copy optimizations in PixelFlux.
• Compare directly inputting RGB and converting before RGB input. If using cudaconvert, add the equivalent of cudaupload and cudaconvert to PixelFlux so that color conversion is done by CUDA in NVENC mode as well. Default to this mode when libnvrtc is present and fall back to the original software color conversion when not present.
• Port and optimize https://github.com/selkies-project/selkies/blob/7dd6a93065332e5b3fe48fe5e5eb911a91f82746/src/selkies/legacy/gstwebrtc_app.py#L257-L938 to PixelFlux.
• [META] Optimize the WebRTC stack to the maximum #157, Improve Opus: reduce NetEQ jitterbuffer & eliminate discontinuous audio artifacts from jitter with Opus + RED #153
• Achieve higher efficiency and quality in low-bandwidth and high-latency environments #152
• Rewire the GitHub Actions so that we now build for both amd64 and arm64 using the new GitLab ARM runners. Simplify the containerization and build procedures. Integrate the web components files inside the Python wheel, not as a separate directory that has to be distributed on its own. ([META] ARM encoders, mobile/embedded devices #50) - Assignee: @ehfd
• NVIDIA Container Toolkit: Dynamically expose NVIDIA X.Org X11 display server libraries and configure the container correctly NVIDIA/nvidia-container-toolkit#563, Automatically provisioning X11 and Wayland devices of GPU inside container? NVIDIA/nvidia-container-toolkit#1477 - Addressed in fix: NVIDIA X.Org driver modules mount fixes NVIDIA/nvidia-container-toolkit#1980
• Investigate inconsistent behavior with headless NVIDIA XWayland with Vulkan pixelflux#11 - Addressed in fix: Create NVIDIA control device nodes in nvidia-cdi-refresh.service NVIDIA/nvidia-container-toolkit#1979
• Rewrite docs.
• All other possible bugs in https://github.com/selkies-project/selkies/issues?q=is%3Aissue%20state%3Aopen%20label%3Abug

[ehfd]

Details for NVENC encoder dropping a lot of frames with Windows Chromium D3D11VideoDecoder - Consult settings in https://github.com/selkies-project/selkies/blob/7dd6a93065332e5b3fe48fe5e5eb911a91f82746/src/selkies/legacy/gstwebrtc_app.py#L257-L938. The decoder initially starts from baseline profile and changes to high.

Details

Timestamp	Property	Value
00:00:00.000	created	
"2026-03-25 10:21:43.784039 UTC"
00:00:00.000	url	
"WebCodecs::VideoDecoder"
00:00:00.000	kFrameTitle	
"Fedora KDE"
00:00:00.000	kFrameUrl	
"https://ehf-xgl-test.nrp-nautilus.io/"
00:00:00.007	info	
"Use D3D11VideoDecoder"
00:00:00.007	info	
"D3D11VideoDecoder is using h264 baseline / 4:2:0"
00:00:00.007	info	
"D3D11VideoDecoder producing NV12"
00:00:00.007	info	
"D3D11VideoDecoder: Selected NV12"
00:00:00.007	info	
"D3D11VideoDecoder is binding textures"
00:00:00.007	info	
"D3D11VideoDecoder is using D3D11 backend"
00:00:00.011	info	
"D3D11VideoDecoder is using array texture"
00:00:00.011	info	
"Selected D3D11VideoDecoder adapter LUID:{0, 64263}"
00:00:00.011	info	
"Video is supported by D3D11VideoDecoder"
00:00:00.011	kVideoDecoderName	
"D3D11VideoDecoder"
00:00:00.011	kIsPlatformVideoDecoder	
true
00:00:00.011	kVideoTracks	
[
  {
    "alpha mode": "is_opaque",
    "codec": "h264",
    "coded size": "1920x1080",
    "color space": {
      "matrix": "BT709",
      "primaries": "BT709",
      "range": "LIMITED",
      "transfer": "BT709"
    },
    "encryption scheme": "Unencrypted",
    "has extra data": false,
    "hdr metadata": {},
    "natural size": "1920x1080",
    "orientation": "0°",
    "profile": "h264 baseline",
    "visible rect": "0,0 1920x1080"
  }
]
00:00:00.011	info	
"Initialized VideoDecoder: codec: h264, profile: h264 baseline, level: not available, alpha_mode: is_opaque, coded size: [1920,1080], visible rect: [0,0,1920,1080], natural size: [1920,1080], has extra data: false, encryption scheme: Unencrypted, rotation: 0°, flipped: 0, color space: {primaries:BT709, transfer:BT709, matrix:BT709, range:LIMITED}"
00:00:00.013	info	
"D3D11VideoDecoder config change: profile: h264 high, chroma_sampling_format: 4:2:0, coded_size: 1920x1088, bit_depth: 8, color_space: {primary=1, transfer=1, matrix=1, range=1}"
00:00:00.013	info	
"D3D11VideoDecoder is using h264 high / 4:2:0"
00:00:00.013	info	
"D3D11VideoDecoder producing NV12"
00:00:00.013	info	
"D3D11VideoDecoder: Selected NV12"
00:00:00.013	info	
"D3D11VideoDecoder is binding textures"
00:00:00.013	info	
"D3D11VideoDecoder is using D3D11 backend"
00:00:00.016	info	
"D3D11VideoDecoder is using array texture"
00:03:22.846	event	
"kWebMediaPlayerDestroyed"
Use D3D11VideoDecoder
D3D11VideoDecoder is using h264 baseline / 4:2:0
D3D11VideoDecoder producing NV12
D3D11VideoDecoder: Selected NV12
D3D11VideoDecoder is binding textures
D3D11VideoDecoder is using D3D11 backend
D3D11VideoDecoder is using array texture
Selected D3D11VideoDecoder adapter LUID:{0, 64263}
Video is supported by D3D11VideoDecoder
Initialized VideoDecoder: codec: h264, profile: h264 baseline, level: not available, alpha_mode: is_opaque, coded size: [1920,1080], visible rect: [0,0,1920,1080], natural size: [1920,1080], has extra data: false, encryption scheme: Unencrypted, rotation: 0°, flipped: 0, color space: {primaries:BT709, transfer:BT709, matrix:BT709, range:LIMITED}
D3D11VideoDecoder config change: profile: h264 high, chroma_sampling_format: 4:2:0, coded_size: 1920x1088, bit_depth: 8, color_space: {primary=1, transfer=1, matrix=1, range=1}
D3D11VideoDecoder is using h264 high / 4:2:0
D3D11VideoDecoder producing NV12
D3D11VideoDecoder: Selected NV12
D3D11VideoDecoder is binding textures
D3D11VideoDecoder is using D3D11 backend
D3D11VideoDecoder is using array texture

[ehfd]

Example image is ready in ghcr.io/selkies-project/selkies/example:main-ubuntu26.04.

[huoxingdawang]

Hi there! I was just wondering if there's any rough estimate for when v2.0.0 might be released?

[ehfd]

We can get a release candidate out very soon. CI/CD has been wired up. We do have to get a couple PRs sorted out from pixelflux and pcmflux.

[kingdudely]

I pray for MacOS + Windows support one day. . .