The goal would be to use either the RTSP stream as currently (which must be complex and resource-intensive) or the JPG images created at regular intervals in a camera folder. By refreshing regularly, you get a more fluid image than what Gladys offers with the RTSP stream (I have the impression that it’s a periodic screenshot). In terms of resources, we should be able to gain a lot as well. Most cameras offer these JPG images (which do not have good resolution) allowing simplified display on websites. RTSP streams are known to be complex to integrate into real-time viewing, making it complicated to create an equivalent of an NVR in JS or PHP.
For example, my two RTSP and JPG configurations (no-name Chinese IP camera):
rtsp://login:password@192.168.XXX.XXX:554/11
192.168.XXX.XXX:2000/web/auto.jpg?-usr=xxxx&pwd=xxxxx
HTML/PHP integration with a refresh on the corresponding
If I compare the two results, Gladys and « homemade » installation, the fluidity is clearly on the side of the .jpg management.