Closed anthonws closed 9 months ago
Don't suppose you can send me a wireshark dump. I will check the packets and see if there's anything odd in the time stamps or something.
Ok could you try #101 it behaves a bit more like the old one. If that camera still gives you trouble you can set buffer size to zero to drop the time stamps in that build and just send as it.
I should point out that you won't get any buffer exhausted messages as that build removes the buffer refill mechanic where the stream was paused until refilled. You will just see frames come late and possible jumps in speed of the frames
Any updates on this?
Maybe I can help. I suffer the same issue with my lumus.
I can get you wireshark dumps if you help me a little bit how you need the data and how I can get it to you.
Can to update to the latest version and replicate there? I don't think latest has this sort of buffer exhaustion since it's done in a different way.
Using the latest version. No issues with buffer at the moment.
And new error freezes the camera operation:
[2023-08-22T16:12:31Z INFO neolink::rtsp::states::loggedin] lumus: Camera reports firmware version v2.0.0.687_20102800
[2023-08-22T16:12:31Z INFO neolink::rtsp::states::streaming] lumus: Starting video stream Main Stream (Clear)
[2023-08-22T16:12:31Z INFO neolink::rtsp::states::streaming] lumus: Starting video stream Sub Stream (Fluent)
Extension Txt: "<?xml version=\"1.0\" encoding=\"UTF-8\" ?>\n<Extension version=\"1.1\">\n
This should now be fixed on latest, can anyone confirm?
Closing because I think this is addressed in latest, but if not please re-open
Camera: Reolink Argus 2E Camera firmware version: 0323_712_572_477 Video stream Sub Stream (Fluent) configured to 640x480 and 160kbps Neolink cf67a05dd1d1ac0cb3f1019c7f7b4f24382c9992 release
Have removed go2rtc from Frigate for this camera specifically. Activated PIR in Low Mode sensitivity (28).
Hth, anthonws.