You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
and webRTC card uses mode: mse to display it in a browser ie. Chrome latest version. On HA page I have 5 cards and each displays one stream. h265 is displayd at the top of the page. At the bottom of the page there is another stream for Reolink camera but it uses rtc and h264 stream. It doesn't fit the page so I have to scroll a bit to see it. And now what is wrong. Both those streams display current time. Sometimes when I scroll to bottom to display h264 stream I notice that the time on it is different from the one at the top for h265. Then when scrolling back to the top, h265 stream "speeds up" and suddenly the time is right and with sync with other at the bottom. Without scrolling it seems like it "slows down", time is a few seconds before actual but the stream seems to work OK.
The text was updated successfully, but these errors were encountered:
Hello,
I am using Version: 1.9.8 together with WebRTC card and I have Reolink Duo 2 WiFi camera h265 strem configured as:
rtsp://USER:[email protected]:554/h265Preview_01_main
and webRTC card uses mode: mse to display it in a browser ie. Chrome latest version. On HA page I have 5 cards and each displays one stream. h265 is displayd at the top of the page. At the bottom of the page there is another stream for Reolink camera but it uses rtc and h264 stream. It doesn't fit the page so I have to scroll a bit to see it. And now what is wrong. Both those streams display current time. Sometimes when I scroll to bottom to display h264 stream I notice that the time on it is different from the one at the top for h265. Then when scrolling back to the top, h265 stream "speeds up" and suddenly the time is right and with sync with other at the bottom. Without scrolling it seems like it "slows down", time is a few seconds before actual but the stream seems to work OK.
The text was updated successfully, but these errors were encountered: