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

How do I Start an OBS stream using WHIP and view it with vdo ninja? #1112

Open
pto199 opened this issue Mar 13, 2024 · 4 comments
Open

How do I Start an OBS stream using WHIP and view it with vdo ninja? #1112

pto199 opened this issue Mar 13, 2024 · 4 comments

Comments

@pto199
Copy link

pto199 commented Mar 13, 2024

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?

@steveseguin
Copy link
Owner

steveseguin commented Mar 13, 2024

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.
https://github.com/steveseguin/whip

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.

image

image

@pto199
Copy link
Author

pto199 commented Mar 13, 2024

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?

@steveseguin
Copy link
Owner

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.

@zapf2000
Copy link

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).

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

3 participants