@NickM-27 commented on GitHub (Mar 27, 2024):
@tobernguyen the config you have there is not the reolink recommended config, the difference being the recommended config uses ffmpeg:http
@ksanislo commented on GitHub (Mar 16, 2024):
So, after some fiddling, I found that I was able to get 0.13.2 working with a combination of using the ffmpeg:rtsp:// source in go2rtc along with the…
@Beeez commented on GitHub (Mar 27, 2024):
Also getting this after moving to v0.13. Though I am guessing it is due to performance and high inference.
@tobernguyen commented on GitHub (Mar 27, 2024):
I'm getting this too after upgrading to v0.13. I'm having reolink camera with the recommended setup (using HTTP stream with lower resolution). I…
@tobernguyen commented on GitHub (Mar 27, 2024):
Update: Downgrading go2rtc to 1.6.2 seems to fix the issue. I tested 1.7.0 and got the same issue.
@NickM-27 commented on GitHub (Jan 22, 2024):
Because the models aren't trained on security camera images they definitely vary highly from camera to camera in terms of false positives.
@SuperMaximus1984 commented on GitHub (Jan 22, 2024):
@NickM-27 One more question - I have a PTZ camera with parameters like this:
@NickM-27 commented on GitHub (Jan 22, 2024):
there are some things to clear up here:
- norfair does not do motion detection, it handles tracking objects as they move across the camera…
@ithesk commented on GitHub (Feb 6, 2024):
I have the same problem, and in version 0.12 it doesn't happen, only in version 13
:
I have Reolink RLC-523WA actually two separate HA setups. With Frigate 0.12.1 both setups are working, but upgrading Frigate to 0.13.2 those are not…
@PeterPalenik commented on GitHub (Mar 14, 2024):
Very similar here. I get the 'No frames have been received, check error logs' very often on all cameras simultaneously. This wasn't happening on…
@jarru66 commented on GitHub (Mar 14, 2024):
Very similar here. I get the 'No frames have been received, check error logs' very often on all cameras simultaneously. This wasn't happening…
@ksanislo commented on GitHub (Mar 15, 2024):
I also have this same issue with a variety of Amcrest cameras after upgrading to 0.13.2. Nearly all of my cameras are giving the "no frames have been…
@NickM-27 commented on GitHub (Jan 22, 2024):
another thing you could try is just turning off detect in the dashboard for all cameras and see if the issue improves
@SuperMaximus1984 commented on GitHub (Jan 22, 2024):
@NickM-27 Yeah, I managed to get 27-33 ms inference time with TRT Yolov7-640 model. Now it doesn't skip anything and "No frames" message…
@NickM-27 commented on GitHub (Jan 22, 2024):
the inference time has a direct affect on this issue, because when frigate is sitting waiting for the object detection inference to complete it is…
@NickM-27 commented on GitHub (Jan 21, 2024):
100ms is really slow, it means you can only run 10 inferences per second, which is not nearly enough for 5 fps across 6 cameras
@NickM-27 commented on GitHub (Jan 21, 2024):
In any case, we've not had any other reports of this issue so it will likely be something fairly specific
@SuperMaximus1984 commented on GitHub (Jan 22, 2024):
@NickM-27 OK, I can try reconfiguring Frigate for TensorRT despite its model's inferiority in terms of accuracy, but I don't think the…
@SuperMaximus1984 commented on GitHub (Jan 22, 2024):
I've tried running with TRT, now the inference time is much better, but it doesn't change the "No frames.." issue appearing periodically…