Repository navigation
FDGCast 0.5.5 preview
Pre-releaseFDGCast Changelog — 0.4.0 to 0.5.5
Windows Preview • OBS Studio 32.2.2
Release dates below use America/New_York. Version 0.4.0 is the starting baseline; the 0.5.x entries describe changes since that baseline. These are preview releases, with live platform and OBS testing continuing.
0.5.5 — October 1, 2026
Destination setup inside OBS
- Added a platform dropdown directly to OBS’s Add FDGCast destination dialog: Twitch, YouTube, Kick, and Other / Custom.
- Twitch and YouTube automatically select their server addresses, so setup only requires a stream key.
- Kick attempts to retrieve its server address from the connected account. A custom server option remains available when the account permissions do not expose it.
- Other / Custom allows manual server entry. Optional names use a platform label when left blank.
- Fixed the gap in 0.5.3, where the simpler platform picker was available in Companion but the OBS dialog still asked for an RTMP(S) address.
Audio Guard sound customization
- Replaced the classic Windows warning sound with a short, two-note FDGCast chirp lasting approximately half a second.
- Added custom WAV upload, a 0–100% volume slider, Preview, and a button to restore the default chirp.
- Custom sounds are copied into FDGCast’s local data folder; moving the original file does not break playback.
- Supports uncompressed 8-bit/16-bit PCM WAVs, mono or stereo, 8–48 kHz, up to five seconds and 2 MB.
- Preview works without enabling automatic reminders. Reminders remain optional.
- Sound playback runs outside the app’s main event loop.
Validation: 126 automated Python tests passed, plus Windows native compilation, browser UI, packaged app, and installer checks.
0.5.4 — October 1, 2026
Alert testing and sound delivery
- Added separate Test Windows notification and Test sound controls that work without going live.
- Made the optional two-minute mute reminder sound independent of Windows toast delivery.
- Added a check for Windows notification availability before submitting a toast.
- Improved test feedback and local history entries for requested, unavailable, or failed alerts. Submission does not guarantee that Windows displayed a banner or that a sound was audible.
Twitch redemptions and Events status
- Added Twitch channel-point redemption subscriptions and display in Combined Events.
- Redemption support requires a broadcaster-owned Twitch authorization with
channel:read:redemptionsorchannel:manage:redemptions. - Missing permission or a denied redemption subscription is reported separately and does not interrupt working Twitch chat.
- Empty Events views show redemption readiness or connection guidance instead of only “No events yet.”
Validation: 121 automated Python tests passed, plus Windows build and installer checks.
0.5.3 — October 1, 2026
Simpler Companion destination setup
- Added Twitch, YouTube, Kick, and Other / Custom platform choices to Companion’s Destinations form.
- Automatically selects Twitch and YouTube servers; attempts connected-account Kick server discovery.
- Moved manual server overrides under Advanced settings. Other / Custom opens manual entry.
- Made destination names optional and generates destination IDs automatically.
- Added Edit controls for saved destinations. Existing server settings and stream keys are preserved; a blank key keeps the saved key when replacing an existing destination.
This release changed Companion’s form. The equivalent OBS dialog update arrived in 0.5.5.
Validation: 115 automated Python tests passed, plus Windows build and installer checks.
0.5.2 — September 30, 2026
OBS connection clarity
- Keeps the OBS WebSocket password in its masked setup field after connecting.
- Restores the saved password after an app restart and adds Show/Hide controls.
- Displays an explicit green Connected indicator and a Reconnect OBS action.
- Reconnecting with a blank password field reuses the saved password.
- Password retrieval remains limited to authenticated local setup; normal state, reports, and native IPC do not expose it.
Chat and Events contrast
- Added lighter blue-gray feed backgrounds and stronger borders to distinguish Chat and Events from their enclosing docks.
- Made the chat input darker, with a stronger border and orange focus outline.
- Aligned feed and composer colors between OBS and Companion.
Validation: 112 automated Python tests passed, plus Windows build and installer checks.
0.5.1 — September 30, 2026
Compact, customizable OBS docks
- Removed repeated dock headings and persistent explanatory text.
- Added persistent per-dock menus for compact spacing, text size, connection-status visibility, and extra-control visibility.
- Added Chat options to hide the composer or origin labels. Original channel information remains visible by default and available on hover.
- Shortened chat connection labels and shows send feedback only while sending or after a failure.
- Simplified Stream Doctor’s default view, with details on hover or in Companion and audio fixes shown when relevant.
- Simplified Multistream’s default view to Start All, Stop All, and the destination list. Additional controls remain accessible through its menu.
- Removed stacked-control and destination-list minimum-height restrictions by using scrollable dock content.
- Dock content can shrink to approximately 100 × 60 pixels; OBS title bars and neighboring docks can still impose layout limits.
- Fixed stale Events content after reconnect and marks Multistream destinations UNKNOWN when Companion is offline.
- Stores display preferences separately from OBS’s saved dock positions.
Validation: automated Python, JavaScript, Windows native compilation, app, and installer checks passed. Actual docking and resizing still require OBS workspace testing.
0.5.0 — September 30, 2026
Chat presentation and connection reliability
- Added platform icons, deterministic username colors, shortened names with full-name hover, creator markers, and available creator avatars.
- Added Twitch/Kick emote images, including GIF animation, in OBS and Companion. Companion falls back to text when an image fails.
- Improved automatic Hub account synchronization, credential persistence, and failure isolation between platforms.
- Added active YouTube live-chat discovery and rediscovery after a broadcast ends, with improved cursor, quota, and rate-limit handling.
- Added verification/recreation of Kick’s chat webhook subscription and clearer distinction between subscription readiness and actual received messages.
- Improved safe platform error messages and filtering of Kick relay messages to the linked broadcaster.
- Kept Combined Events focused on supported audience activity, separating it from app operations and diagnostic history.
Multistream controls
- Added Start All and Stop All for the main OBS stream and selected secondary destinations.
- Added persistent per-destination selection checkboxes, while retaining individual start/stop controls.
- Added clearer LIVE, CONNECTING, RECONNECTING, ERROR, and OFFLINE states, plus readable failure messages.
- Secondary outputs reuse the main H.264 video and AAC audio encoders; each destination still uses its own upload bandwidth.
Audio Guard
- Added monitoring for selected microphone and optional game/desktop audio sources.
- Detects prolonged mute, missing/inactive sources, zero source volume, Monitor Only, stream-track exclusion, prolonged silence, and missing meter updates.
- Checks routing against the actual active stream audio encoder rather than assuming Track 1.
- Added configurable quiet scenes, Snooze 10 Minutes, I Know, explicit Unmute, and explicit routing fixes.
- Added live-only Windows warnings and bounded local audio incident history.
- Muted-source timing: dock warning at 30 seconds, notification at 60 seconds, optional sound at two minutes, and reminder at five minutes.
- Audio Guard does not automatically change audio settings. Silence is treated as a symptom, not proof of a disconnected device.
Stream Doctor, history, and preflight
- Added destination-specific reconnect, failed-start, unexpected-stop, and network-frame-drop history.
- Added possible shared-issue grouping, stable recovery detection, and live-only Windows Doctor notifications.
- Added persistent local sessions, incident timelines, audio entries, session filtering, and Copy Diagnostic Report with a selectable-text fallback.
- Expanded preflight to check OBS/plugin connections, selected audio, available routing evidence, destination keys, and chat status.
- Added explicit audio fixes and Go Live Anyway without imposing a hard streaming block.
- Diagnostic reports exclude credentials, chat content, and audio source identities from shared JSON history.
Companion startup and saved connections
- Keeps the Hub pairing code saved and masked, with Show/Hide and clearer connection status.
- Opens the installed Companion when OBS starts and its local service is absent.
- Prevents duplicate Companion windows and avoids an automatic relaunch loop after the user closes it.
- Restores saved OBS WebSocket settings and retries connections after OBS restarts.
- Improved dock arrangement and installer verification.
Validation: 110 automated Python tests passed. Windows checks cover native compilation, browser UI, packaged service/app behavior, icons, duplicate-instance handling, installed plugin files, and the registered Companion launch path.
0.4.0 — September 28, 2026 — Starting baseline
- Rebranded ForgeCast’s visible desktop, OBS dock, and installer names to FDGCast.
- Applied FDG branding and icons to the desktop app, taskbar, OBS presentation, and Windows installer.
- Retained existing internal module IDs and local data paths for upgrade compatibility.
- Included the native Chat, Events, Stream Doctor, Multistream, and Control docks, desktop Companion, Hub account pairing, and Twitch/YouTube/Kick chat targets.
- Included individual multistream output controls, shared-chat origin information, and available platform activity.
These baseline features were already present in 0.4.0; they are not new additions in 0.5.x.
Remaining limitations in 0.5.5
- Twitch redemptions need the Hub OAuth permission update and a broadcaster reconnect before they can work. Twitch follows and Kick audience alerts require additional integrations.
- YouTube chat replies depend on the required Google authorization and approval. Third-party emotes and YouTube custom/member emote images are not implemented.
- Kick automatic server lookup depends on account permissions; manual entry remains available.
- Windows settings, Do Not Disturb, output devices, and volume can affect notification visibility or audibility.
- Vertical streaming, separate canvases/encoders, and native overlays remain deferred.
- Automated build checks do not establish viewer playback quality, complete live platform compatibility, or a measured performance advantage over another plugin.