Video Replay freezing up

[majora15]

During our race yesterday the replay station kept freezing and I kept having to refresh and closing the webpage. It would work maybe for a race and freeze up again. Was using a surfacelaptop running windows 11. Not sure if there is a place for logs for this but happy to provide them if needed. Running Edge as the browser in this situation.

[majora15]

Any ideas on this one?

[jeffpiazza]

Sorry this got overlooked.

If you were able to refresh or close the page, then at least that much of the browser was functional. When you say "freezing," do you mean that the replay showed only a still image, or that the tab stopped updating altogether (e.g., didn't advance to the next heat)?

If you were using a camera cabled directly to the laptop, then about the only thing I can think of is a low memory condition in the browser.

If you were using a "remote" camera, the camera browser page and the replay page effectively create a video conferencing link, and that can be subject to all kinds of issues. My usual advice is to prefer a direct camera connection (even if you have to buy a powered extension cable to go past the 5-meter limit. (https://www.avaccess.com/blogs/guides/usb-extender-a-useful-tech/, e.g.)

It's also possible the issue relates to some kind of overload condition arising on the server. That's not terribly likely if you're running your own server, but I hesitate to make any absolute claims.

If you're able to reproduce the condition, try looking at the browser's debug console for error messages and the like, along with any error logs on the server.

[majora15]

Lets say race 1 would start, I would get a video play back on that one, but when it came to race 2 and on from what I remember we would not get an instance reply. When I was watching the remote replay station it wasn't capturing anything as the feed was frozen. Closing the browser and reopening it allowed it to work for the next race, pending the race started soon. It had no impact on the race itself other than no reply. When I tried this prior to the race everything seemed to work fine, so it could very well be an update (Windows or Browser) that caused the issue. The camera was connected directly to the remote replay station. The remote replay station was then set to the machine that showed each race stat on a projector. I made sure to use wired network connection as I know WIFI can be an issue at times, but it seemed like the issue was on the remote reply station side. For the server, I have a dedicated laptop running a hyper-v ubuntu image as the server. The laptop is a gaming laptop so I make sure not to exceed the physical resources. Andrew

…

On Tue, May 7, 2024 at 3:02 AM Jeff Piazza ***@***.***> wrote: Sorry this got overlooked. If you were able to refresh or close the page, then at least that much of the browser was functional. When you say "freezing," do you mean that the replay showed only a still image, or that the tab stopped updating altogether (e.g., didn't advance to the next heat)? If you were using a camera cabled directly to the laptop, then about the only thing I can think of is a low memory condition in the browser. If you were using a "remote" camera, the camera browser page and the replay page effectively create a video conferencing link, and that can be subject to all kinds of issues. My usual advice is to prefer a direct camera connection (even if you have to buy a powered extension cable to go past the 5-meter limit. ( https://www.avaccess.com/blogs/guides/usb-extender-a-useful-tech/, e.g.) It's also possible the issue relates to some kind of overload condition arising on the server. That's not terribly likely if you're running your own server, but I hesitate to make any absolute claims. If you're able to reproduce the condition, try looking at the browser's debug console for error messages and the like, along with any error logs on the server. — Reply to this email directly, view it on GitHub <#309 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ARUMFP2XQFRBBVYOOACGEVLZBCDBNAVCNFSM6AAAAABCOIPACSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJXGY4DSOBUGY> . You are receiving this because you authored the thread.Message ID: ***@***.***>