-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
OBS 30.2 Beta 1 - NVENC HEVC encoder fails with mediamtx whip server #3435
Comments
Hello, as clearly mentioned in the README we don't support using H265 with WebRTC, mainly because the great majority of browsers do not support it. The OBS team decided to unlock the WebRTC-H265 combination last month (see obsproject/obs-studio#10577) , therefore we can add support for ingesting H265 streams with WebRTC, but not for reading them from the server. |
IMPORTANT NOTE: this doesn't allow to read H265 tracks with WebRTC, just to publish them. The inability to read H265 tracks with WebRTC is not in any way related to the server but depends on browsers and on the fact that they are not legally entitled to embed a H265 decoder inside them.
IMPORTANT NOTE: this doesn't allow to read H265 tracks with WebRTC, just to publish them. The inability to read H265 tracks with WebRTC is not in any way related to the server but depends on browsers and on the fact that they are not legally entitled to embed a H265 decoder inside them.
This issue is mentioned in release v1.8.4 🚀 |
This issue is being locked automatically because it has been closed for more than 6 months. |
Which version are you using?
v1.8.2
Which operating system are you using?
Describe the issue
NVENC HEVC encoder fails with mediamtx whip server. Continual disconnect and reconnect to the server as shown by OBS notifications:
Describe how to replicate the issue
Did you attach the server logs?
yes: mediamtx.log
Did you attach a network dump?
no
OBS discord notified me that this looks like a mediamtx issue. They advised I send you the OBS debug log too. Here you go: obs-verbose.log
The text was updated successfully, but these errors were encountered: