Skip to content

Conversation

@amquake
Copy link
Member

@amquake amquake commented Oct 26, 2023

Removes websocket-based camera streaming functionality.

Fixes #975. This was caused by destroying the camera streams and recreating them on nickname change. Even when directly using MJPGFrameConsumer and the streams were exactly the same, the freeze would occur when creating a new MjpegServer and require a refresh. I think this is simply how cscore works?

@amquake amquake requested a review from a team as a code owner October 26, 2023 06:14
streamResultConsumers.clear();

// Teardown and recreate streams
destroyStreams();
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So does this mean we don't actually ever recreate the MJPGFrameConsumer now? That shouldn't cause issues (I guess the metadata about camera name in NT might be wrong unless we tell it to change? But AFAIK nobody uses that anyways)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The camera name isn't used in the MJPGFrameConsumer constructor, so nothing should change afaik

@srimanachanta srimanachanta linked an issue Oct 26, 2023 that may be closed by this pull request
@srimanachanta
Copy link
Member

srimanachanta commented Oct 28, 2023

you can probably remove the UISettings file as well as it was added under similar goals

@mcm001 mcm001 merged commit 76e3c6d into PhotonVision:master Oct 30, 2023
@amquake amquake deleted the remove-camera-socket branch October 31, 2023 00:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Changing camera names causes streams to freeze Camera frame WS broadcaster doesn't do anything

3 participants