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
Is it possible to detect if webrtc will play smoothly using the player only? Or would that require some sort of backend work with OME?
It would be nice to be able to auto detect the best available playback option of (llhls, hls, and webrtc) and use that. It's a project we're hoping to work on and perhaps push upstream if possible
The text was updated successfully, but these errors were encountered:
with llhls and hls, b-frames is always supported. When using webrtc, b-frame playback is never supported. I don't think this needs any extra "detection". Reason for that are the limited low-latency decoders of WebBrowsers and the b-frames timing information which OME doesn't "correct"/adjust.
We have arbitrary incoming streams from users, with or without b frames. llhls will of course always play assuming no dropped/skipped/missed frames in OBS. webrtc may or may not play based on the streamer's settings, and those that haven't configured their stream properly sending b frames.
We can write something to detect whether webrtc will play smoothly in the backend, but a frontend solution may be cleaner, hence the question
Is it possible to detect if webrtc will play smoothly using the player only? Or would that require some sort of backend work with OME?
It would be nice to be able to auto detect the best available playback option of (llhls, hls, and webrtc) and use that. It's a project we're hoping to work on and perhaps push upstream if possible
The text was updated successfully, but these errors were encountered: