-
Notifications
You must be signed in to change notification settings - Fork 22
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
400 Bad Request on pushing to twitch #18
Comments
I don't know how I'm supposed to test this. I see a static endpoint, but for tokens it says |
Yeah you need an account (which is free), here is what I tested (after adding some args in the dockerfile):
|
Created one but god the settings are so annoying. Just to create a stream I have to go through a 1000 hoops, pick a category I don't want to pick, can't make it private or unlisted who knows why. I have zero interest in giving this a go, to be honest. 400 means the server doesn't like something we send, and there's no way for me to know what just by guessing. Hopefully someone with Twitch knowledge will chime in and tell me what to fix. |
Pinging @danjenkins as he may know who to nudge about that. |
I enabled libsoup3 debugging, which shows this:
Apparently it doesn't like the way H.264 is negotiated. |
I pushed a commit to enable HTTP debugging, if you want to make more tests. Adding something like |
My guess is something like missing profile-level-id here:
vs. the functional version in OBS
If I can confirm this is just a gstreamer issue hopefully I can fix it in the dockerfile and close. |
In my case the profile-level-id was there, just not one they'd like maybe
|
I haven't followed: has this been fixed by Twitch in the meanwhile? |
I've tried vp8, vp9 and h264 with no luck, see:
https://www.reddit.com/r/WebRTC/comments/12nc5md/twitchtv_now_supports_webrtc_ingestion_via_whip/
cc @Sean-Der
By contrast, https://github.com/ggarber/whip-go does work with twitch.tv.
The text was updated successfully, but these errors were encountered: