-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
[Camera Support]: #5860
Comments
most likely it is just coming back like this from the camera. You're not using hwaccel so there is nothing that would affect the data coming from the camera I don't think |
That's what I was thinking as well, except I don't have this problem when viewing the rtsp feed directly, It will just run for hours without issue, and this happens fairly regularly with frigate. Most times within moments of the initial error, I can click on the camera itself and the video is absolutely fine, but birdseye and the snapshot for the camera is not. I somewhat feel like there could be an optimization for ffmpeg that could overcome this, but don't know where to start. |
would expect more logs after that from ffmpeg, otherwise not sure |
Doing more digging, I've found it only goes to the white screen for the camera on jsmpeg, it shows up properly under webrtc and mse. birdseye still shows the curropted frame and does not update |
right, because the ffmpeg process for detect is what supplies that snapshot to both of those while the other live views are separate |
Okay, so it could be something with the setup of my detect stream?
I'm going to try this to see if it helps:
|
It may have been this also?
|
I would definitely suggest not overriding those and just let it use frigate defaults |
I thought for at least record, in order to get audio you need to unless that has changed? |
I have edited my config file ffmpeg section to look like this:
and my camera section to look like this:
It appears to be a working config. I'll run like this for the next day or so and report back the findings. Thank you for the help and realizing that I was over complicating things. |
sure but you are overriding that setting on the camera level so what you set globally has no affect (and you should definitely be using ffmpeg presets everywhere) |
Gotcha. That makes sense. I'll change the ffmpeg to preset-record-generic-audio-copy and override just those cameras that I don't want audio. That does actually make sense. I initially made this configuration file over a year ago before the presets were a documented part of frigate. |
Well, everything is working great now. It usually would have failed at this point. Thank you for your time, I know it is valuable. Hopefully someone can find my mistakes useful in troubleshooting :) |
As a side note, this issue came back. I fixed the problem by setting this camera up like so:
It seems that using |
Describe the problem you are having
I have 2 Merkury 1080p outdoor bullet cameras modified to output an rtsp stream. These cameras every once in a while look like the following screenshots:
I am using
Version
0.12.0-7D589BD
Frigate config file
Relevant log output
FFprobe output from your camera
Frigate stats
Operating system
Other Linux
Install method
Docker Compose
Coral version
USB
Network connection
Wireless
Camera make and model
Merkury 1080p Outdoor Camera
Any other information that may be helpful
https://github.com/williamkennyAK/Merkury1080P is used to modify camera to give rtsp output
The text was updated successfully, but these errors were encountered: