derbynet icon indicating copy to clipboard operation
derbynet copied to clipboard

Remote Camera works great on v8, has issues on v10

Open jakezilla opened this issue 1 year ago • 6 comments

First off thank you for the amazing software!

My test setup consists of a Windows laptop running the server (with self signed cert), a Raspberry Pi B 4 2GB with Logitech web cam and Chromium, Lenovo Windows laptop with Edge, and a dedicated LAN only router.

Testing the Pi setup as a Replay Kiosk using the local webcam works great on v10 and v8. The replay timing is consistent and there is little to no lag.

Configuring the Pi as a Remote Camera, then configuring the Lenovo as a Replay Kiosk utilizing the Remote Camera works great on v8, but on v10 it falls apart. The replays are inconsistently timed, there are studders in the video, large time lags, and sometimes the Replay Kiosk just stops responding and updating.

What I've tried: A different webcam on the Pi Setting up the Lenovo's built in webcam as the Remote Camera and the Pi as the Replay Kiosk Setting up the Lenovo's built in webcam as the Remote Camera and a desktop PC as the Replay Kiosk A different router A 3rd router

I'm more than happy to take video or send logs, but I don't know what would be helpful. Let me know how I can help solve this!

(This may possibly be related to issue #309 )

jakezilla avatar Jan 10 '25 02:01 jakezilla

I'm experiencing the same issues. My setup is a headless PC running Ubuntu 22.04 and the Derbynet server. I have another Windows 10 laptop running a replay kiosk connected to an Android phone running as a remote camera. The video preview on the Android device looks fine but when I trigger a replay from the server the replay kiosk just shows a black screen. I get the same result when trying a remote camera in a private window on the same laptop running the replay kiosk. I had opened #318 last year but didn't get a response.

chunter2 avatar Jan 22 '25 00:01 chunter2

I got around this during our race this year by setting up a PC with a local camera as a Replay Kiosk and then splitting the video output to several screens. The video playback was flawless that way. Try it as a workaround if needed!

ductaper avatar Feb 15 '25 01:02 ductaper

I haven't been able to reproduce this, but I did find a code issue that might cause enough of a performance issue to explain the described issues.

If anyone finds it's still happening, please confirm:

  • Is the server local or hosting.derbynet.org ? If local, what operating system (Windows, Mac, Raspbian, Linux) is it running on?
  • What OS is the camera device running?
  • What OS is the replay kiosk running?

jeffpiazza avatar Apr 13 '25 18:04 jeffpiazza

Just gave it a try again after updating to your 1804 release. Still get the same results. My setup is the same as I posted above.

Thanks

chunter2 avatar Apr 14 '25 11:04 chunter2

I'm thinking 839cfdc is the most likely culprit, although I don't see any obvious problems yet. The polling frequency is lower, but I wouldn't expect that to make a difference.

Summarizing the two configurations reported so far:

jakezilla has an RPi as camera, Windows laptop as replay kiosk, another Windows laptop as server. chunter2 has an Android phone as camera, Windows laptop as replay kiosk, Windows server.

jeffpiazza avatar Apr 15 '25 12:04 jeffpiazza

ebf4554 may be a fix for this. I'd appreciate any feedback to confirm or refute that this is resolved.

(Latest derby-timer.jar available here.)

jeffpiazza avatar May 08 '25 15:05 jeffpiazza