MichaIng

I reviewed all open pull requests now. Some became obsolete in the meantime (closed), some partly (asked for rebase), some are quite nice and seem safe to apply (asked for...

Sounds like a bandwidth issue, since the remote camera stream is "downloaded" by motion, passed over to motionEye, then "uploaded" to the client/browser. When connecting via VLC, the round trip...

A limited bandwidth? Reducing camera resolutions, amount of cameras streamed on web UI e.g. But this is just the first theory I had in mind. Also check CPU usage, RAM...

Could you try the new Python 3 based motionEye version from `dev` branch: https://github.com/motioneye-project/motioneye/tree/dev#installation CPU usage is notable, but since you have multiple cores (?) not maxed. Did you try...

Many thanks for your report. Before we invest time into the Python 2 version, could you try it out with the `dev` branch motionEye using Python 3 and newer module/library...

> Should I update Motion as well (not sure which versions are supported by motioneye)? No, 4.3.2 is best, 4.4 is not yet fully supported by motionEye: #2333 Btw with...

> Could it be that I need to open more ports motionEye is only listening on a single port as of the config, other ports would remain unused. Also a...

Would be interesting to know whether this happens the same way with a native installation of the current motionEye `dev` branch: https://github.com/motioneye-project/motioneye/blob/fcf1b1f/README.md#installation Not sure when I find time to test...

That asset URLs look wrong, AFAIK the cam-specific prefix shouldn't be there. Could you try to switch to the new motionEye version developed on the `dev` branch? https://github.com/motioneye-project/motioneye/tree/dev#installation

To start with, the motionEye logs could help: ```sh journalctl -u motioneye ``` To rule out issues with bandwidth or so, did you try it with a single netcam only?...