Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Detect webrtc b frames #297

Open
naanlizard opened this issue Aug 2, 2022 · 2 comments
Open

Detect webrtc b frames #297

naanlizard opened this issue Aug 2, 2022 · 2 comments

Comments

@naanlizard
Copy link

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

@basisbit
Copy link

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.

@naanlizard
Copy link
Author

I'm not sure I follow

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants