Open nledenyi opened 1 year ago
You have not set
ffmpeg:
hwaccel_args: preset-nvidia-h264
Globally which means your cpu is being used to encode birdseye. If you set it globally then the GPU will be used and it should work much better.
I have a very similar setup and have not seen this issue with birdseye
Unfortunately that didn't make a difference. Added that to globally to the root level and commented it out from the individual camera nodes.
What else could I provide to diagnose this?
Would need to see new logs. Also, is there a reason you are telling go2rtc to re encode your stream has h264? It seems that the original camera stream should also be h264 already
- "ffmpeg:kapu#audio=opus#video=h264"
yeah, the original is already in h264, addig that to go2rtc too was just part of the testing, didn't imporve nor worse the sitution, so just removed it now. Also testing the global preset-nvidia-h265 flag now just to see if it improves anything or not.
What log you'd most need, frigates debug or go2rtcs?
yeah, the original is already in h264, addig that to go2rtc too was just part of the testing, didn't imporve nor worse the sitution, so just removed it now. Also testing the global preset-nvidia-h265 flag now just to see if it improves anything or not.
That would only be usable if your incoming stream is h265
What log you'd most need, frigates debug or go2rtcs?
go2rtc since that is the one doing all the actual work here. I would also suggest testing having at least one camera set to continuous
mode in birdseye and see if that helps
so with at least one camera on continuous mode, birdseye is pretty stable - haven't experienced neither of the symptons
as soon as i removed the continuous flags, I got both a crash and a corrupted feed within like 15 minutes. Logs are here: https://gist.github.com/nledenyi/3a29011df11210e8c71caa596c1c9319
so looks like you were onto something with having at least one camera on continuous because that helped - any other info i can provide which would help you?
Thanks
i see 12-RC2 landed, upgraded just now, will report back if the issue still persists
still the same in 12-RC2 too
0.12 is fully released. No changes were made related to this. It makes sense that a stream will have a harder time starting when there are no cameras running since a stream has to start on a key frame and there's not many key frames when there are no camera images to update.
Birdseye will likely be rewritten in a future version so this will be fully fixed then.
thanks. So should we keep this open till that? I would leave it up to you guys, I'm fine either way
Any other workaround for the time being other than having at least one camera on continuous?
thanks. So should we keep this open till that? I would leave it up to you guys, I'm fine either way
Yes, that's why it's pinned
Any other workaround for the time being other than having at least one camera on continuous?
Don't think so
Describe the problem you are having
Hi,
First of all, loving the new 12-RC1 features. This ticket is related to birdseye resteam related issues, since I don't know whether they the same root cause I'm raising them in one ticket for now, but happy to separate them later if needed (or if they are go2rtc related, can raise it over there. For now I have to types of issues:
I'm running frigate on an unraid os, ryzen 3600, plenty of ram, 1050ti gpu, edge tpu usb, only unifi cameras (various models)
More details around crashing / restart: i was testing it both VLC and displaycameras. In VLC when it occurs the streams just stops and doesn't recover. Displaycameras recovers eventually. When this occurs I can load and view the birdseye in frigate's own web ui but only in mjpeg view - webrtc and mse just spins indefinitely. Switched both frigate and go2rtc into debug log level, but i see no error messages around the time when such thing happens
More details around the image falling apart / getting corrupted: after a frigate restart, the image is good for a while, but after only just a few minutes it becomes something similar to this: When this happens, the image:
Version
12-RC1
Frigate config file
Relevant log output
FFprobe output from your camera
Frigate stats
Operating system
UNRAID
Install method
Docker CLI
Coral version
USB
Network connection
Wired
Camera make and model
only unifi cameras
Any other information that may be helpful
The only birdseye log in frigate's debug i found was this: 2023-04-05 21:37:40.772927068 [2023-04-05 21:37:40] frigate.output DEBUG : Clearing the birdseye frame
go2rtc's debug is quite long, i tried to find and attach the most relevant looking portion