-
-
Notifications
You must be signed in to change notification settings - Fork 12
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
Egress #24
Comments
Running the egress for my cluster would actually incur quite a bit of cost. I may look into this in the future, but I'm afraid I'd have to charge more for it than I do for my standard cluster. If you mean for a self-hosted cluster - I don't think there is anything that prevents setting up the egress yourself, however I haven't had a chance to play with it yet and I'm not sure how easy it is to bring it into OBS in that way. |
I don't think I undestood. The livekit group told me egress were a way to export a track. This is what I need. I just want to grab the each participant track to use with OBS. Do you know how can I do that? Link: livekit/livekit#825 Tks |
The egress is a service that must be run. It joins the meeting itself and allows you to record or stream the data back out. However, since it has to process all of the video and audio, it requires a decent amount of computing power and bandwidth. I haven't had the chance to look into it very deeply yet, but as I said I would almost certainly have to charge more per month to provide that as a service in order to cover the costs of running it. |
oh... I don't think people will like that. Maybe create two servers. One livekit, the other one livekit+egress |
It would be a separate optional charge for sure. It's also not something that I will likely have time to work on in the near future, unfortunately. |
Hi.
Can you add an option to get the participant link, so you can use it for OBS?
This is useful for lives, you can get each participant stream and make it look nice on OBS.
Docs
https://blog.livekit.io/livekit-universal-egress-launch/
Tks
The text was updated successfully, but these errors were encountered: