Sync the self-hosting stack
This commit is contained in:
@@ -9,6 +9,25 @@ one of them changed. An entry says which artefact and which version, so `web 0.1
|
||||
Every version published to a channel appears here. Nothing is written from memory afterwards: a build
|
||||
cannot be published without its entry.
|
||||
|
||||
## 2026-10-08 — Remote desktop streams video as H.264 `agent 0.35.0` `web 0.151.0` `api 0.121.0`
|
||||
|
||||
The remote screen is now streamed as H.264 video when your browser and the machine both can, so a
|
||||
video playing on the machine, a window being dragged or a page scrolling reaches you smoothly instead
|
||||
of as a stream of still images, and with far less bandwidth. The agent uses the graphics card's
|
||||
encoder when there is one and the Windows software encoder otherwise; your browser decodes the stream
|
||||
itself. The bitrate adapts to the connection, and a screen that stops changing stops costing anything
|
||||
after half a second.
|
||||
|
||||
When either end cannot — an older browser, an older agent, or a machine without a Media Foundation
|
||||
encoder — the session uses the existing image stream exactly as before. The status line under the
|
||||
picture now says which one you are getting: **H.264 video** or **JPEG images**. On Windows Server the
|
||||
software encoder comes with the optional Media Foundation feature (`Install-WindowsFeature
|
||||
Server-Media-Foundation`, then restart); without it the server streams images and the agent's event
|
||||
log says why.
|
||||
|
||||
Update the agent release image, the API image and the web console image. They can be updated in any
|
||||
order; video starts once all three are. No database update is required.
|
||||
|
||||
## 2026-10-07 — Remote desktop follows the lock screen and UAC prompts `agent 0.34.0` `web 0.150.1`
|
||||
|
||||
A remote-desktop session no longer pauses when the person at the machine locks it or a Windows
|
||||
|
||||
Reference in New Issue
Block a user