DMST is the parent hub for DigiMancer3D's local-first streaming, presentation, and accessible creator-tool ecosystem.
Tool suite · Architecture · Workflow · Get started · Safety
A live show should not require an operator to manually juggle a dozen windows. DigiMancer Streamer Tools (DMST) groups a set of independently useful applications into a flexible, local desktop workflow. Build slides, arrange cards, configure pinboards, time show segments, automate transitions and keep the host in control of what appears in OBS.
DMST is the index and integration guide, not a replacement for the applications or a duplicate source-code bundle. Each project has its own repository, installation steps, release cadence and save formats.
Note
Features described here span multiple alpha-stage applications. Not every component is required or necessarily available in every published version. Check the individual repositories and use local compatibility checks before upgrading a live studio.
| Project | Role in the studio | Repository |
|---|---|---|
| Streamer Board & Console (SBC) | Application launch, profiles, adapters, saved pinboards and friendly app names | Open SBC |
| DMS Live Switcher | Deck/pinboard switching, pre-show order, triggers, delays and timed actions | Open DMS |
| Deck Card Widget (DCW) | Stream-overlay cards, layered PNG/emoji/text and Full-Data/QR-Data output | Open DCW |
| Field Guide Forge (FGF) | Episode editor, SWAR scripts, proof displays, broadcaster/public exports, Studio Cues | Open FGF |
| FGF Broadcaster Launcher (FGF-BCL) | Native C++/Qt6 launcher that picks the newest configured private episode | FGF-BCL source |
| SWAR | Script/reader ecosystem used by compatible authoring workflows | Open SWAR |
| Bitninja Mocap Lite | VTuber/VRM motion capture for the studio | Open Bitninja |
| G502V | Mouse/input visualization and accessible control experiments | Open G502V |
Other DigiMancer3D projects may integrate with the studio later without being required by this core workflow.
flowchart TB
SBC[Streamer Board & Console] -->|Launch/manage| FGF[Field Guide Forge]
SBC -->|Launch/manage| DMS[DMS Live Switcher]
SBC -->|Launch/manage| DCW[Deck Card Widget]
BCL[FGF-BCL] -->|Choose private episode| FGF
FGF -->|Paired page/source/block Studio Cues| DMS
DMS -->|Registered deck selection + QR-Data| DCW
DMS -->|Registered pinboard selection| SBC
FGF -->|Presenter capture| OBS[OBS]
DCW -->|Deck output capture| OBS
SBC -->|Pinboard output capture| OBS
The FGF broadcaster is a presenter, not an uncontrolled remote launcher. It sends an assigned cue to DMS, which checks that the referenced Deck Card or pinboard is registered before requesting a change. DMS can confirm whether Deck Card Widget is online and whether a QR mode request was acknowledged.
Deck Card Widget can present the same card as a text-forward Full-Data composition or a QR-focused QR-Data composition. Layers can have different positions and visibility on the two sides. DMS exposes a live display switch, and FGF can use that same connection after local pairing.
- Prepare: Author pages/sources in FGF and map their Deck Cards, pinboards and display modes with Studio Cues.
- Load: Open the appropriate
.buttstorein DCW and register matching deck/.sboardselections in DMS. - Launch: Use SBC for studio apps, or FGF-BCL to find the latest matching private broadcaster episode.
- Pair: Enter DMS's local pairing code in the FGF broadcaster when asked; verify it shows PAIRED.
- Present: Navigate with
W/S/A/D; keep Auto Cues ON for mapped transitions or OFF for manual moments. - Adapt: Toggle QR-Data, Full-Data, stickers or an optional Chat Thank You page as the live show requires.
- Publish afterward: Export a privacy-reviewed public FGF HTML, not the private broadcaster page, as the post-show companion.
DMST itself does not install the entire studio as one monolithic application. Choose the tools you need and follow their READMEs:
1. SBC , app launcher and pinboard hub
2. DCW , cards and overlay output
3. DMS , switching, timing and validated automation
4. FGF , authoring and private/public presenter exports
5. FGF-BCL , optional newest-episode launcher
Each tool can be used separately. On Linux, native Python tools generally require Python 3 and Tk; FGF uses a browser plus a local Python helper; FGF-BCL requires C++20 and Qt6 to build. OBS is needed only for actual scene capture.
Keep real studio data out of public source repositories. Examples of files that usually should not be committed include:
.buttstore,.deckbutt,.sboard,.fgfwith private episode/studio information.- DMS/FGF pairing codes, user tokens and authenticated local-bridge metadata.
- Adapter JSON containing personal executables or private filesystem paths.
- Private broadcaster HTML, local
user_data/collections, backups and unfinished episode source notes.
The integration is designed around local commands and registered assets, not general-purpose Internet control. FGF's public companion output should be reviewed for personal information, image contents and external links before uploading.
This DMST repository is best used as the documentation hub and link index. Application source changes belong in the specific tool's own repository. To publish a coordinated release, update each application source and README independently, verify their compatibility, and only then update this hub's links and overview.
For new contributors: check the individual project's license and issue tracker before redistributing artwork, sample content or application-specific code. License terms may differ across repos.
Created by DigiMancer3D for independent creators and shows including 3D Changes Perspectives.
Links: GitHub profile · 3D Changes Perspectives · Streamer Board & Console · Deck Card Widget
License: see LICENSE if present; each linked project maintains its own licensing and documentation.