No frames received by frigate #84
Comments
|
Ho Mortiz, Nice addition to use qualification to detect people! To oanswer you question; Streaming the video is a lot of data and what I see often is that the ESP32 cannot handle that much data. A drop in connectivity or attempting to send more data than is possible causes the RTSP stream to freeze and the RTSP client times out/stops functioning. VLC for example has some buffering build in to be able to display a continuous stream. To detect people I tried to detect using tensorflow lite on the ESP itself to overcome this problem. Take a look at the repository at https://github.com/rzeldent/esp32cam-persondetection. This works but the frame rate is not very high. However, you only need one ESP and no server or post processing. The training set can be found at https://studio.edgeimpulse.com/studio/29733. It works but the framerate is not very high. However, might be an idea to also add a repository to use the ESP32CAM as a security/detection camera. Optionally, take a look at the Sipeed MAIX BIT with the K210 neural processor. I bought these around 30 euros (a long time ago) but they can do detection (yolo) at 50 frames/sec! Also the tensorflow model can be transformed to the kmodel so this runs very fast. However, I think they do not have WiFi (but can be resolved by adding an ESP8266). Let me know if this helps or gave you inspiration... |
|
Hi, the detection is all done by frigate. ESP32 only sends the bare rtsp stream to it. But that's where the problem is: I can't get a stable rtsp stream... When it's there, everything is working perfectly, but this part rerpeating every 20 seconds, makes it unpossible. If the problem is the amount of data, what can I adjust? I have 4mb PSRAM (8mb version coming soon), less then 5m between router and esp32, image set to 800x600px. That's my current config: Maybe VGA or less (higher number) JPEG Quality can help? |
|
Hi Moritz, Decreasing the resolution will reduce the number of bytes sent so should work. If the compression is increased this results in a lower bitrate but also more cpu power used and this will reduce the effectiveness. So would go for lowering the image size, good placement/antenna. |
|
Any luck / progress? |
|
No not really. I tried an other board with 8mb psram, antenna, resolution down to 640x480 and many different qualities. Also trying not with RTSP, but jmpeg stream url over go2rtc... It's never stable over more then a short time. |
|
Maybe this helps: https://stackoverflow.com/questions/3367187/what-is-lib-swscale-used-for-by-ffmpeg-programers |
rzeldent
added
bug
|
Did you find a solution @MStapelfeldt? I am running into the same issue, I had the stream working for about 5 minutes on frigate then nothing. I can see the JPEG HTTP stream but RTSP will not load on either frigate or VLC. |
|
Unfortunately not... I gave up on espcam and switched to cheap v380pro cam. https://a.aliexpress.com/_Exi5Wlj |
|
I appreciate it, I’m at that point too.
…On Mon, Feb 19, 2024 at 23:44 Moritz Stapelfeldt ***@***.***> wrote:
Unfortunately not... I gave up on espcam and switched to cheap v380pro
cam. https://a.aliexpress.com/_Exi5Wlj
Set them up to onfiv and block Internet after setup. They work as a charm
for the money.
—
Reply to this email directly, view it on GitHub
<#84 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AZNVOZ3ORE7B7XH2RSFDKDTYURA6PAVCNFSM6AAAAAA2LZZOJWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJTGU3TQNZVG4>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
Still similar in recent usage for me. It can sometimes run for some extended periods when parameters are chosen to keep things in sustainable ranges for framerate/datarate etc.. but ultimately it flakes out fairly using the recommended mjpeg camera rtsp settings. I will say that I'm currently getting a bit better behavior out of a stream from one with an ov5640 (which also does a better job with getting color right and having lower noise levels). I'm wondering if the lower noise might keep the frame sizes down or if there's something with that setup that's just a bit more consistent. Still it does need to be watched and things sometimes need to be restarted to get the stream going again. I have that set at 1600x1200 and 1fps on a seeed w/ the ov5640 swapped for the original ov2640. Frigate's reported storage requirements / hr seem to reflect that stream having imagery that compresses less well too. I allowed the gain to go pretty high so that may not reflect everyone else's setups. For the life of me, I can't get acceptable image quality indoors out of the ov2640 without having quite a bit of light. the ov5640 is more forgiving. |
Hello,
I've set up a camera with your code in frigate yesterday and it was working very good. Today the stream stopped working and I couldn't get it back on.
Here is the log output from Frigate:
And this is the frigate.yaml
The camera is also set to 800x600px, PSRAM active (has 4mb) AI Thinker. The web stream works and I also can view RTSP with other apps. After Rest, power disconnect and restarting Frigate, Camera shows again with log
But I see stream...
Any Idea what I can do to find the issue and get it working all the time?
Additional info:
Detection also works, but I can't load the record but can view the snapshot of capture.
The text was updated successfully, but these errors were encountered: