Repository navigation
Add opt-in WebSocket media publisher for Discord Activity - #45
Merged
Merged
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: cc42d54193
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Publishers can optionally send encoded H.264/Opus over WebSocket for Discord Activity while keeping the existing RTC publisher path. FRAMERELAY_WEBSOCKET_MEDIA_ENABLED defaults to false; enabling it obtains RelayControl upload grants and starts an independent reconnecting output with bounded owned buffers.
Reuses H.264 output when available and adds a separate copied-frame H.264 encoder when RTC uses AV1. Includes the approved design/plans, shared protocol fixtures and implementation verification report.
Validation: full desktop solution build passed with zero warnings/errors; 50 focused media tests and 9 API client/session tests passed. Tests cover default-off behavior, memory ownership, bounded queues, fragmented control frames and real ClientWebSocket upload. Native browser fixture verified forwarding and WebCodecs playback across companion components.
Runtime limits: real Windows capture opt-in, live Discord Activity and simultaneous two-machine RTC viewing remain unverified. No production deployment performed.
Companion PRs: RelayControl #61, FrameRelay #45, Activity #9. Deploy the companion components together before enabling the new flags.