The v0.1.0 Windows artifact loaded into OBS 32.2.2 on Windows 11 (build 26200) on a director's machine on 2026-09-09, from C:\ProgramData\obs-studio\plugins\streamer-tools-camera\bin\64bit\.
That retires "It has not been run in the OBS GUI on any platform", which this README asserted in four places (status section, Windows CI paragraph, "Testing this by hand", and the "Not verified anywhere" list).
Scoped to what was actually observed: the module loads and registers its source type. Still unverified, and still stated as such:
whether video actually renders — right way up, right colours
A/V sync and end-to-end latency versus the existing egress path
whether a publisher restarting mid-show recovers on screen
Linux and macOS in the GUI at all (macOS's artifact still isn't loadable — see the macOS packaging gap)
Also drops the release-draft rationale that pointed at the no-GUI-load state, and carries the ProgramData install-path warning up into the status section — that mistake is what kept the first GUI load from happening sooner (fixed in PR #2).
The v0.1.0 Windows artifact loaded into **OBS 32.2.2 on Windows 11 (build 26200)** on a director's machine on 2026-09-09, from `C:\ProgramData\obs-studio\plugins\streamer-tools-camera\bin\64bit\`.
That retires *"It has not been run in the OBS GUI on any platform"*, which this README asserted in four places (status section, Windows CI paragraph, "Testing this by hand", and the "Not verified anywhere" list).
**Scoped to what was actually observed:** the module loads and registers its source type. Still unverified, and still stated as such:
- whether video actually renders — right way up, right colours
- A/V sync and end-to-end latency versus the existing egress path
- whether a publisher restarting mid-show recovers on screen
- Linux and macOS in the GUI at all (macOS's artifact still isn't loadable — see the macOS packaging gap)
Also drops the release-draft rationale that pointed at the no-GUI-load state, and carries the `ProgramData` install-path warning up into the status section — that mistake is what kept the first GUI load from happening sooner (fixed in PR #2).
Docs only.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
https://claude.ai/code/session_01AzGnvQ6wfD7bw7PZN35ft9
The v0.1.0 Windows artifact loaded into OBS 32.2.2 on Windows 11 (build
26200) on a director's machine on 2026-09-09, from
C:\ProgramData\obs-studio\plugins\streamer-tools-camera\bin\64bit\. That
retires "has not been run in the OBS GUI on any platform", which this README
asserted in four places.
Scoped deliberately to what was actually observed: the module loads and
registers its source type. Whether video renders, the colours, A/V sync,
latency, and mid-show publisher restart are all still unverified, and Linux
and macOS have still never been opened in the GUI. The "Not verified
anywhere" list now says so explicitly rather than being deleted.
Also drops the release-draft rationale that pointed at the no-GUI-load state,
and carries the ProgramData install-path warning up into the status section,
since that is what stopped the first GUI load from happening sooner.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01AzGnvQ6wfD7bw7PZN35ft9
jknapp
merged commit ee44fb6a73 into main2026-09-09 23:47:05 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The v0.1.0 Windows artifact loaded into OBS 32.2.2 on Windows 11 (build 26200) on a director's machine on 2026-09-09, from
C:\ProgramData\obs-studio\plugins\streamer-tools-camera\bin\64bit\.That retires "It has not been run in the OBS GUI on any platform", which this README asserted in four places (status section, Windows CI paragraph, "Testing this by hand", and the "Not verified anywhere" list).
Scoped to what was actually observed: the module loads and registers its source type. Still unverified, and still stated as such:
Also drops the release-draft rationale that pointed at the no-GUI-load state, and carries the
ProgramDatainstall-path warning up into the status section — that mistake is what kept the first GUI load from happening sooner (fixed in PR #2).Docs only.
🤖 Generated with Claude Code
https://claude.ai/code/session_01AzGnvQ6wfD7bw7PZN35ft9