WebRTC python sdk - realtime updating channel outputs #1710
Conversation
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
…o webrtc-python-sdk-update-channels
hansent
reviewed
Nov 12, 2025
| logger.info(f"Starting WebRTC worker with output_mode: {args.output_mode}") | ||
| if args.output_mode == "data_only": | ||
| logger.info( | ||
| "DATA_ONLY mode: Server will send JSON data via data channel only (no video track)" |
Collaborator
There was a problem hiding this comment.
maybe dont want these changes in this PR
grzegorz-roboflow
previously approved these changes
Nov 13, 2025
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.
Description
Adding sdk functionality to udpate outputs.
And adding the optional parameter to start the stream as data-only, depends on @lrosemberg branch #1700
It is also built on top of the initial webrtc sdk version: #1701
Which should be merged before this one too.
Type of change
How has this change been tested, please provide a testcase or example of how you tested the change?
locally
Any specific deployment considerations
None
Docs
Not updated yet. But it will be done in a future PR