-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* Use env var to control max number of frames * Handle type * Fix frame_name not being sent * Formatting
- Loading branch information
Showing
3 changed files
with
10 additions
and
2 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
002fdea
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.
After one of these recent builds, any cameras named like so:
cameraname < —— fails to get frames
cameraname2
The first one will fail to get the detect stream with a generic unable to read frames from the ffmpeg process. adding a character to the first one fixes it.
cameraname1 < —— works
cameraname2
I have multiple cameras named in this manner, I am okay if this is expected behavior moving forward but i just wanted to note it somewhere.
002fdea
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.
yeah this is a known issue, we should be able to make a tweak to fix this