72 Releases 115 Tags

RSS Feed

• v0.31.4 d2c6e1c9c0

  Compare

  v0.31.4 Stable

  enricobuehler released this 2026-08-24 22:27:35 +00:00 | 6806 commits to main since this release

  Wire-compatible with 0.31.x — everything you have already paired keeps working, and you can update one side at a time. Nothing here changes how a host and a client agree on what to send each other, so an old client on a new host, or the other way round, streams exactly as it does today.

  This is a fix release about the machine you stream from behaving itself while you are not in the room with it. Asking for your screens off during a stream only ever worked on a box running a KDE desktop — a Steam Deck, or anything else sitting in Game Mode, kept its television lit for the whole session, playing your game to an empty room. That works now on every kind of Linux box, including ones with no desktop at all. Putting that box to sleep or shutting it down from Steam's own power menu had stopped working during a stream, in two separate ways, and works again. On the client side, a long session on a connection that was never the problem could slide from 57 Mbps down to 5 and stay there; the Mac app could quit outright the moment a stream started; and the web console served a certificate browsers refuse, so the page you are told to open did not load, while on Linux the tray insisted the console was dead the whole time it was running perfectly. There is a little new work too: the gamepad console's bitrate reaches 2 Gbps and takes a number you type, and on Linux there is finally a way into that console that is not a command line.

  TL;DR

  • "Turn my screens off while I stream" now actually turns them off. It only ever worked on a KDE desktop. A Steam Deck or any other box in Game Mode ignored it silently, which is the deployment where you most want it. It works there, and on sway and Hyprland desktops too. GNOME is the one that still cannot be served, and the host now says so instead of leaving you guessing.
  • Steam's power menu did nothing during a stream. Sleep, Restart and Shut Down all work again. Two unrelated faults with one symptom: your host was refusing every suspend request for the length of a stream, including yours, and on some setups the box lost the permission to power itself off at all while it was streaming.
  • A long session could slide to the worst picture quality on a perfectly good connection. One 1440p session walked from 57 Mbps down to 5 over ten minutes without dropping a single packet, and never recovered. Both causes are fixed.
  • Mac: the app could quit the instant a stream started. Not at launch — at the moment you connected, which made it look like the host's fault.
  • The web console would not open in a browser, and on Linux the tray labelled it "not responding" while it was serving fine.
  • New: the gamepad console's bitrate goes to 2 Gbps, steps finely at the low end, and takes a typed number; on Linux the gamepad console gets a button, a menu entry and its own app-grid launcher.

  Before you update

  • Only if your host takes the box over by stopping its login screen, and you want Steam's power menu to work: be in the punktfunk group. That is the same group the takeover already needs to do its job, so if the takeover works for you today you are already in it and there is nothing to do. If you set that up some other way, join it — the docs page titled Steam / gamescope carries the one-line command — because the permission this release adds is granted to that group and nobody else, deliberately.

  New

  • Bitrate in the gamepad console reaches 2 Gbps, and you can type a rate. The picker had seven rungs stopping at 80 Mbps since the console shipped, which someone ran straight into — and the desktop app beside it has always gone far higher, so the two disagreed about what your own machine was allowed to ask for. There are 30 rungs now, from 1 Mbps to 2 Gbps: tight at the bottom, where a single step decides whether a thin connection is watchable, and coarse at the top, where a step is noise. Press Y on that row to type a rate instead, using the same on-screen keyboard as the add-host and pairing fields, including Steam's own keyboard on a Deck. And a rate that is not one of the rungs — typed here, or set from the desktop app — now steps to its neighbour instead of being thrown away and snapped back to Automatic by a single nudge. The desktop app gets the other half of the same complaint: its bitrate box steps 1 Mbps at a time instead of 5, so 3, 4 and 6 are reachable without typing.
  • Linux: a front door to the gamepad console. The couch interface has shipped for a while, but on Linux the only way to reach it was a command-line switch, which is not something you find by looking. There are three ways in now: a gamepad button in the app's host list, a "Console UI" entry in its menu, and a separate launcher in your applications grid that you can also add to Steam as a non-Steam game so it opens straight from the couch. All three land in the same place. This comes with the packaged builds; a from-source Nix build still does not include the separate launcher, because that build leaves the console interface out.

  Improved

  • The adaptive bitrate control no longer gives up on a whole session. Part of the picture-quality fix below: when your client decided the host's encoder was the bottleneck and stopped listening to that signal, it stopped listening for the rest of the session. But the thing that provokes it is temporary by nature — a game hammering the graphics card, a shader storm, a second program on the same card — and all of those end. It now starts listening again after a clean stretch, and if the noise comes straight back it backs off for longer each time rather than flapping.
  • When your host cannot turn a screen off, it says so. Every one of those refusals means "you asked for your screens off and they stayed on", and the most common one was being recorded at a level nobody reads. It is now a warning, with the reason.

  Fixed

  • Your screens stayed lit through the whole stream, on every Linux box except a KDE desktop. Reported on Nobara: launching a game from the library with screens-off selected left the operator's monitor showing live Game Mode for the entire session. Three separate things were wrong. The setting was implemented by asking the desktop to turn its screens off — right when there is a desktop to ask, and a box in Game Mode has none, which is precisely the box whose television you want dark. That case is now handled by switching the display off through the graphics hardware directly, which needs no extra privileges and cannot leave a screen dark if the host crashes, because the screen comes back the moment the host lets go. A sway or Hyprland desktop was not served either, and now is, through each one's own controls, taking care to leave any screen it did not darken alone rather than "fixing" one that was already off. And separately, the part of the host that moves the box's own gaming session out of the way only did so for a Steam launch, because freeing Steam was the only reason anyone had ever needed it — so a non-Steam game from your library left that session running and driving the television regardless. Wanting your screens off is now a second, independent reason to move it aside. GNOME remains a genuine gap, not an oversight: it offers applications no way to turn a screen off, and holds the graphics card itself so the direct route is refused. The host warns instead of pretending.
  • The recommended way of streaming a Game Mode box ignored the setting entirely. The route that gives the best experience — and the only one that can serve your client its own screen at its own resolution — was the one route that never darkened anything, because there was nowhere safe to undo it and a screen left dark after every stream is worse than one left lit. The undo now lives in the single teardown every one of those sessions passes through, so it is honoured. A reconnect does not darken twice, and a session that keeps running between connections stays dark rather than flickering.
  • Steam's power menu did nothing during a stream, and neither did Sleep. Two independent faults, one symptom, both on Linux. Your host holds a lock for the length of a stream so the box cannot suspend out from under someone who is only watching and never touching anything — but that lock refuses every suspend, including the one you asked for by pressing Sleep, and nothing in Steam's interface shows the refusal, so the entry simply did nothing for as long as anyone was connected. The lock is now held only while the stream is genuinely quiet: any input from any client drops it immediately, so a Sleep press cannot lose the race, and it comes back after 30 seconds of silence. The case it was written for is unchanged — a passive viewer sends nothing, and the box still will not sleep under them. The second fault is Shut Down and Restart, on the takeover setups that stop the box's login screen: doing that leaves the box with no signed-in session, and the system's rules only allow powering off from one. All three entries quietly became a password prompt — asked of something that cannot answer, on a screen that is switched off. The packages now ship a rule granting exactly those three actions, to the punktfunk group and to nobody else, and only those three: a box with a second person logged in still asks first.
  • A long session slid to the lowest picture quality on a connection that never lost a packet. Reported from a 1440p60 session that ratcheted 57 Mbps down to 5 over ten minutes, with the host granting every rate it was asked for and nothing at all going wrong on the link. Two causes, both in the part of your client that watches how long the host is taking to compress each frame. Its thresholds were tuned on a 120-frames-a-second session, where one frame is 8 milliseconds; on a 60-frame session a frame is twice that, so an ordinary one-frame hiccup cleared the "something is badly wrong" bar that the identical hiccup at 120 never reached. They are now measured against the session's own frame budget. And the signal was firing for something cutting the rate cannot fix: it exists to find the point where the encoder runs out of compute, where less rate means less work — but when a game is saturating the graphics card that premise is false, the reduction changes nothing, and it would fire again a moment later. Two reductions in a row that buy no improvement now stand the signal down. Everything else your client watches — packet loss, delay, decoding, and the host's own refusal to climb — keeps its full authority throughout, so a real encoder limit is still caught.
  • Mac: the app could quit outright the moment a stream started. Not at launch, which is what made it look like a host problem. Setting up your microphone takes a snapshot of the input device's audio format and then hands that snapshot back a moment later, and on a Mac the input can change underneath in that window — you switch devices, something changes the sample rate, or the app itself switches to the device you chose two lines earlier. Any mismatch was fatal and could not be caught. It now asks the system to use whatever format the device actually has, so there is no snapshot to go stale, and follows the device if it changes rate mid-stream instead of resampling by the wrong ratio and pitch-shifting your voice.
  • The web console would not load in a browser, and the tray called it dead. A Linux operator saw "Open web console (not responding)" in the tray, beside a tooltip that said the host was idle — which was the clue, because that tooltip proved the host was answering perfectly on the very same check. Your host has kept two identities for a while now: a modern one that everything current uses, and an older one kept unchanged so Moonlight-compatible clients keep working. The web console never followed that split, and none of the things that start it could choose — so it served the old identity, which no browser will accept, and the page you were told to open failed to load. Meanwhile the tray was checking on the console using the modern identity, so its check was refused and a completely healthy console was labelled as not responding. The console now serves the modern identity whenever the host has one, and the tray's check no longer insists on any particular one, because it reads nothing, sends nothing, and decides only what a menu entry says. A host that predates the split, or one where you supplied your own certificate, is unaffected and behaves exactly as before.
  • Hyprland: the request to turn a screen off is a toggle, and would have turned a dark screen back on. Found on a live Hyprland box rather than in review, and worth saying because the first version of this fix was wrong in both directions: the command ignores whether you asked for on or off and simply flips whatever the screen is currently doing. So "turn it off now, turn it back on later" would have lit a screen that was already dark at the start of a stream, and darkened a lit one at the end — the operator's screen left off after streaming, which is the exact failure this whole feature exists to avoid. Your host now reads the screen's real state first, acts only if it differs, and checks afterwards that it worked. A screen already in the state you wanted is left completely alone.

  Thanks

  Every fix above started as somebody saying exactly what they saw. The monitor still showing Game Mode through a whole stream, and which kind of game they had launched. The power menu that did nothing, on which box. The 1440p session whose quality walked downhill for ten minutes while every other number stayed flat — that report came with the measurements that separated the two causes, which is the hard half. The bitrate ceiling somebody hit and pointed out was lower than the app right next to it. The Mac that quit on connect. And the tray that said "not responding" beside a tooltip reading "idle" — noticing that those two things contradicted each other is what found the bug. Thank you.

  One caveat we would rather write down than let you discover: the sway arm of the screens-off work has not been run against a real sway session — there is no sway machine in the lab. Hyprland, KDE, and the no-desktop route were all measured on real hardware. If you stream from sway, we would like to hear how it goes.

  For developers

  Protocol, ABI, driver and embedder detail — including the version table — is in CHANGELOG.md.

  The short version: nothing versioned moves, at all. The streaming protocol, the embedding interface, the driver protocol, the gamepad channel, the add-on contract and the management API are exactly where 0.31.3 left them — the embedding header is byte-identical for the third release running, and the API description changes only its stamped version number. No header, package, plugin or integration needs rebuilding, re-pairing or re-publishing in any direction, and the add-on toolkit and TypeScript package are both untouched. Two behaviour changes are worth knowing about if you integrate: the host's sleep veto is now conditional on stream quiet rather than held for the whole session, and the client's encode-attributed backoff both re-arms after standing down and sizes its thresholds from the negotiated refresh rather than in absolute milliseconds.

  Downloads

  • Punktfunk-0.31.4.dmg
    11 MiB

    2026-08-24 22:58:43 +00:00
  • Punktfunk-0.31.4.dmg.sha256
    87 B

    2026-08-24 22:58:44 +00:00
  • Punktfunk-0.31.4.ipa
    10 MiB

    2026-08-24 23:03:27 +00:00
  • Punktfunk-0.31.4.ipa.sha256
    87 B

    2026-08-24 23:03:28 +00:00
  • punktfunk-0.31.4-1-x86-64.f43.raw
    64 MiB

    2026-08-24 23:11:51 +00:00
  • punktfunk-0.31.4-1-x86-64.f43.raw.sha256
    100 B

    2026-08-24 23:11:52 +00:00
  • punktfunk-0.31.4-1-x86-64.f44.raw
    65 MiB

    2026-08-24 23:14:08 +00:00
  • punktfunk-0.31.4-1-x86-64.f44.raw.sha256
    100 B

    2026-08-24 23:14:09 +00:00
  • punktfunk-0.31.4-1.fc43.x86_64.bazzite.rpm
    12 MiB

    2026-08-24 23:10:51 +00:00
  • punktfunk-0.31.4-1.fc43.x86_64.bazzite.rpm.sha256
    109 B

    2026-08-24 23:10:52 +00:00
  • punktfunk-0.31.4-1.fc44.x86_64.fedora-44.rpm
    12 MiB

    2026-08-24 23:13:09 +00:00
  • punktfunk-0.31.4-1.fc44.x86_64.fedora-44.rpm.sha256
    111 B

    2026-08-24 23:13:11 +00:00
  • punktfunk-0.31.4.aab
    36 MiB

    2026-08-24 22:49:15 +00:00
  • punktfunk-0.31.4.aab.sha256
    87 B

    2026-08-24 22:49:16 +00:00
  • punktfunk-0.31.4.apk
    80 MiB

    2026-08-24 22:50:11 +00:00
  • punktfunk-0.31.4.apk.sha256
    87 B

    2026-08-24 22:50:13 +00:00
  • punktfunk-0.31.4.cdx.json
    4.9 MiB

    2026-08-24 22:56:51 +00:00
  • punktfunk-0.31.4.cdx.json.sha256
    92 B

    2026-08-24 22:56:52 +00:00
  • punktfunk-0.31.4.zip
    1.3 MiB

    2026-08-24 22:52:02 +00:00
  • punktfunk-0.31.4.zip.sha256
    87 B

    2026-08-24 22:52:03 +00:00
  • punktfunk-client-0.31.4-1-x86_64.pkg.tar.zst
    21 MiB

    2026-08-24 22:52:26 +00:00
  • punktfunk-client-0.31.4-1-x86_64.pkg.tar.zst.sha256
    111 B

    2026-08-24 22:52:27 +00:00
  • punktfunk-client-0.31.4-1.fc43.x86_64.bazzite.rpm
    18 MiB

    2026-08-24 23:10:58 +00:00
  • punktfunk-client-0.31.4-1.fc43.x86_64.bazzite.rpm.sha256
    116 B

    2026-08-24 23:11:00 +00:00
  • punktfunk-client-0.31.4-1.fc44.x86_64.fedora-44.rpm
    18 MiB

    2026-08-24 23:13:20 +00:00
  • punktfunk-client-0.31.4-1.fc44.x86_64.fedora-44.rpm.sha256
    118 B

    2026-08-24 23:13:21 +00:00
  • punktfunk-client-0.31.4.flatpak
    17 MiB

    2026-08-24 23:00:29 +00:00
  • punktfunk-client-0.31.4.flatpak.sha256
    98 B

    2026-08-24 23:00:32 +00:00
  • punktfunk-client-setup-0.31.4.0_arm64.exe
    11 MiB

    2026-08-24 23:22:01 +00:00
  • punktfunk-client-setup-0.31.4.0_arm64.exe.sha256
    108 B

    2026-08-24 23:22:02 +00:00
  • punktfunk-client-setup-0.31.4.0_x64.exe
    19 MiB

    2026-08-24 22:50:08 +00:00
  • punktfunk-client-setup-0.31.4.0_x64.exe.sha256
    106 B

    2026-08-24 22:50:10 +00:00
  • punktfunk-client-windows_0.31.4.0_arm64-portable.zip
    13 MiB

    2026-08-24 23:22:07 +00:00
  • punktfunk-client-windows_0.31.4.0_arm64-portable.zip.sha256
    119 B

    2026-08-24 23:22:08 +00:00
  • punktfunk-client-windows_0.31.4.0_arm64.msix
    14 MiB

    2026-08-24 23:22:14 +00:00
  • punktfunk-client-windows_0.31.4.0_arm64.msix.sha256
    111 B

    2026-08-24 23:22:15 +00:00
  • punktfunk-client-windows_0.31.4.0_x64-portable.zip
    23 MiB

    2026-08-24 22:50:20 +00:00
  • punktfunk-client-windows_0.31.4.0_x64-portable.zip.sha256
    117 B

    2026-08-24 22:50:21 +00:00
  • punktfunk-client-windows_0.31.4.0_x64.msix
    23 MiB

    2026-08-24 22:50:32 +00:00
  • punktfunk-client-windows_0.31.4.0_x64.msix.sha256
    109 B

    2026-08-24 22:50:34 +00:00
  • punktfunk-client_0.31.4_amd64.deb
    19 MiB

    2026-08-24 22:50:27 +00:00
  • punktfunk-client_0.31.4_amd64.deb.sha256
    100 B

    2026-08-24 22:50:28 +00:00
  • punktfunk-client_0.31.4_arm64.deb
    18 MiB

    2026-08-24 22:52:02 +00:00
  • punktfunk-client_0.31.4_arm64.deb.sha256
    100 B

    2026-08-24 22:52:03 +00:00
  • punktfunk-gamescope-3.16.25.pfhdr8-1-x86_64.pkg.tar.zst
    2.6 MiB

    2026-08-24 22:52:30 +00:00
  • punktfunk-gamescope-3.16.25.pfhdr8-1-x86_64.pkg.tar.zst.sha256
    122 B

    2026-08-24 22:52:32 +00:00
  • punktfunk-gamescope-3.16.25.pfhdr8-1.fc43.x86_64.bazzite.rpm
    2.1 MiB

    2026-08-24 23:11:02 +00:00
  • punktfunk-gamescope-3.16.25.pfhdr8-1.fc43.x86_64.bazzite.rpm.sha256
    127 B

    2026-08-24 23:11:03 +00:00
  • punktfunk-gamescope-3.16.25.pfhdr8-1.fc44.x86_64.fedora-44.rpm
    2.2 MiB

    2026-08-24 23:13:24 +00:00
  • punktfunk-gamescope-3.16.25.pfhdr8-1.fc44.x86_64.fedora-44.rpm.sha256
    129 B

    2026-08-24 23:13:25 +00:00
  • punktfunk-gamescope_3.16.25.pfhdr8_amd64.deb
    2.1 MiB

    2026-08-24 22:50:32 +00:00
  • punktfunk-gamescope_3.16.25.pfhdr8_amd64.deb.sha256
    111 B

    2026-08-24 22:50:34 +00:00
  • punktfunk-host-0.31.4-1-x86_64.pkg.tar.zst
    15 MiB

    2026-08-24 22:52:37 +00:00
  • punktfunk-host-0.31.4-1-x86_64.pkg.tar.zst.sha256
    109 B

    2026-08-24 22:52:38 +00:00
  • punktfunk-host-setup-0.31.4.exe
    73 MiB

    2026-08-24 23:05:27 +00:00
  • punktfunk-host-setup-0.31.4.exe.sha256
    98 B

    2026-08-24 23:05:28 +00:00
  • punktfunk-host_0.31.4_amd64.deb
    24 MiB

    2026-08-24 22:49:48 +00:00
  • punktfunk-host_0.31.4_amd64.deb.sha256
    98 B

    2026-08-24 22:49:49 +00:00
  • punktfunk-scripting-0.31.4-1-x86_64.pkg.tar.zst
    33 MiB

    2026-08-24 22:52:50 +00:00
  • punktfunk-scripting-0.31.4-1-x86_64.pkg.tar.zst.sha256
    114 B

    2026-08-24 22:52:52 +00:00
  • punktfunk-scripting-0.31.4-1.fc43.x86_64.bazzite.rpm
    26 MiB

    2026-08-24 23:11:13 +00:00
  • punktfunk-scripting-0.31.4-1.fc43.x86_64.bazzite.rpm.sha256
    119 B

    2026-08-24 23:11:14 +00:00
  • punktfunk-scripting-0.31.4-1.fc44.x86_64.fedora-44.rpm
    26 MiB

    2026-08-24 23:13:35 +00:00
  • punktfunk-scripting-0.31.4-1.fc44.x86_64.fedora-44.rpm.sha256
    121 B

    2026-08-24 23:13:36 +00:00
  • punktfunk-scripting_0.31.4_amd64.deb
    26 MiB

    2026-08-24 22:50:39 +00:00
  • punktfunk-scripting_0.31.4_amd64.deb.sha256
    103 B

    2026-08-24 22:50:40 +00:00
  • punktfunk-web-0.31.4-1-x86_64.pkg.tar.zst
    34 MiB

    2026-08-24 22:53:02 +00:00
  • punktfunk-web-0.31.4-1-x86_64.pkg.tar.zst.sha256
    108 B

    2026-08-24 22:53:02 +00:00
  • punktfunk-web-0.31.4-1.fc43.x86_64.bazzite.rpm
    27 MiB

    2026-08-24 23:11:23 +00:00
  • punktfunk-web-0.31.4-1.fc43.x86_64.bazzite.rpm.sha256
    113 B

    2026-08-24 23:11:25 +00:00
  • punktfunk-web-0.31.4-1.fc44.x86_64.fedora-44.rpm
    27 MiB

    2026-08-24 23:13:45 +00:00
  • punktfunk-web-0.31.4-1.fc44.x86_64.fedora-44.rpm.sha256
    115 B

    2026-08-24 23:13:47 +00:00
  • punktfunk-web_0.31.4_amd64.deb
    27 MiB

    2026-08-24 22:50:49 +00:00
  • punktfunk-web_0.31.4_amd64.deb.sha256
    97 B

    2026-08-24 22:50:50 +00:00
  • unom.PunktfunkHost.installer.yaml
    3.5 KiB

    2026-08-24 23:05:31 +00:00
  • unom.PunktfunkHost.installer.yaml.sha256
    100 B

    2026-08-24 23:05:31 +00:00
  • unom.PunktfunkHost.locale.en-US.yaml
    3.7 KiB

    2026-08-24 23:05:32 +00:00
  • unom.PunktfunkHost.locale.en-US.yaml.sha256
    103 B

    2026-08-24 23:05:33 +00:00
  • unom.PunktfunkHost.yaml
    496 B

    2026-08-24 23:05:33 +00:00
  • unom.PunktfunkHost.yaml.sha256
    90 B

    2026-08-24 23:05:34 +00:00
  • Source Code (ZIP)
  • Source Code (TAR.GZ)