-
Notifications
You must be signed in to change notification settings - Fork 264
Remove socket camera streaming #985
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
| streamResultConsumers.clear(); | ||
|
|
||
| // Teardown and recreate streams | ||
| destroyStreams(); |
There was a problem hiding this comment.
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)
There was a problem hiding this comment.
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
|
you can probably remove the UISettings file as well as it was added under similar goals |
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
MJPGFrameConsumerand the streams were exactly the same, the freeze would occur when creating a newMjpegServerand require a refresh. I think this is simply how cscore works?