-
-
Notifications
You must be signed in to change notification settings - Fork 812
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
How do I Start an OBS stream using WHIP and view it with vdo ninja? #1112
Comments
https://whip.mydomain.com/test I suppose, however this assumes a LOT of things, since you're self deployed. You would need to ensure you've also deployed the whip-signaling server, if you wanted to have that self-hosted as well. You could in theory just use the vdo.ninja whip server, so publish to https://whip.vdo.ninja/testpto199 , while having https://stream.mydomain.com/?whip=testpto199 already open. I think the default will use the whip endpoint I'm still hosting. Just ensure its a unique stream ID; test isn't desireable. |
Ahh ok, I thought The whip server part was part of vdo.ninja, didn't realize it was separate. I think this may be out of the scope for my self hosting solution as I'm running an Nginx docker on unraid and then vdo.ninja is installed on that. For the WHIP server I dont see how I can easily set that up as the nginx docker doubtfully will have the dependencies I need Thanks for the quick response anyway. Maybe any plans to setup a docker directly for vdo.ninja along with any other extras perhaps? |
There's been some community members that have done their own dockers, although they haven't been well supported or all that complete. I know there's some demand for me to support a complete official docker deployment option, so it's on the to-do list, but I'll need to ensure I have the time to actually support such an option. Thank you for the request. |
As vdo.ninja is a pure browser based App, there is no media server possible. I think the easiest way is to install a media server on your computer and publish/read from there in WHIP/WHEP. Currently the best and easiest server for me is mediamtx (https://github.com/bluenviron/mediamtx). Just take the pre-build binaries, add TLS support (add cert path to config file) and publish via WHIP from vdo.ninja. You can use the WHEP player from vdo.ninja, because it's more flexible than the mediamtx web player (and supports AV1 very well). |
Im not exactly sure what to do here. I have vdo.ninja spun up on my local server using my own domain. I goto stream.mydomain.com and I can use vdo ninja just fine.
But I want to use WHIP.
So I goto https://stream.mydomain.com/?whip=test in my browser so I am ready. Ok.
Now I goto OBS but how do I start the stream? I select Whip and enter https://stream.mydomain.com as the URL but then when I hit stream I get the could not access specified channel or stream key erro in obss. Do I need to configure something in vdo ninja or is there a specific URL I should be using for the server?
The text was updated successfully, but these errors were encountered: