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

WHIP/WHEP example not working with OpenH264 encoder #171

Open
kevinschweikert opened this issue Oct 17, 2024 · 3 comments
Open

WHIP/WHEP example not working with OpenH264 encoder #171

kevinschweikert opened this issue Oct 17, 2024 · 3 comments

Comments

@kevinschweikert
Copy link

Hi, i tried out the WHIP/WHEP example with a Fedora 40 Workstation OS and OBS which uses the Cisco OpenH264 encoder by default. The video player gets stuck in the loading state but no image is shown. After switching to x264 the stream worked flawlessly.
Let me know if you need more information or if i should open this issue somewhere else in the Membrane space.
Cheers and thanks for all your work!

@mickel8
Copy link
Member

mickel8 commented Oct 17, 2024

Hi @kevinschweikert!

Thanks for the report. We are OOF until Monday but will take a look once we come back :)

@mickel8
Copy link
Member

mickel8 commented Dec 5, 2024

Hi @kevinschweikert, I completely forgot about this issue. I check and indeed, streaming from OBS using openH264 does not work. It looks like browser drops all the packets. What I noticed is that OBS always offers 42e01f profile level id, no matter I select constrained baseline, main or high profile. I don't think the issue is on our side, more on OBS/browser incompatibility. I asked on video-dev slack. Will also check browser logs

@mickel8
Copy link
Member

mickel8 commented Dec 6, 2024

We might have been chosing wrong codec (H264 with wrong profile id) but even after setting it to 0x42e01f (the one offered by the obs), web browser still cannot decode the stream. It logs "no decodable frame in ... requesting keyframe".

Checked with broadcast-box and there is the same behaviour so after merging #179, I don't think the problem is in Elixir WebRTC 🤔

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