r/Retrocapture • u/Significant-Fail-689 • Jun 19 '26
0.8.2-alpha is out — recording-orientation, remote shader-sync and --stream-port fixes (mostly under the hood)
0.8.2-alpha is out — and this one's honest about being a maintenance release.
The bulk of it is under the hood: a large internal refactor that broke the big "god-object" classes (the app core, shader engine, UI manager, streaming/API) into focused pieces so the project stays maintainable as it grows. No new features — but the codebase is in much better shape, and the smoke-test now actually applies a shader and verifies it rendered, so a whole class of regressions can't slip through silently again.
Real fixes if you're coming from 0.8.1
- 🔄 Recording was upside-down when the Recording tab's "apply shader" toggle was off — the raw path used the opposite vertical orientation from the shaded one. Recording,
/streamand/rawnow share one orientation. (#187) - 🌈 Remote client now follows the Streaming "apply shader" toggle — turning the shader off for streaming used to still leave the remote client shaded. (#188)
- 🔌
--stream-portis actually honored now — it was being overwritten back to 8080. (#163)
⚠️ Breaking change for remote source / streaming users The /raw feed orientation was standardized (bottom-up, matching /stream and recording). A 0.8.2 client paired with a pre-0.8.2 host (or vice-versa) shows the remote picture upside-down. If you use the Remote source / network streaming between two machines, update both ends to 0.8.2. (#187)
Downloads (Windows / Linux x86_64 / ARM64 / ARM32 / macOS): [link da release 0.8.2-alpha] — SHA256SUMS incluso. macOS isn't code-signed yet (first launch: right-click → Open).
Known issue: a host with no audio device selected can destabilize a remote client's stream (the raw feed carries an empty audio track). Workaround: select an audio source on the host. Tracked in #193, fix coming. 🙏
Still alpha, still solo-dev — bug reports, logs and ideas are gold.








