-
Notifications
You must be signed in to change notification settings - Fork 906
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 Support #1083
Comments
WHIP is on our radar. I'm curious what is your use case with it. Is there an app that you are trying to ingest from that supports WHIP? |
To date, the open source Meedoze WebRTC Media Server, Janus WebRTC Server and Millicast WebRTC PaaS have implemented WHIP. If you are interested in more technical details about the Medooze implementation, or the Janus implementation, you can read those great blog posts by their respective authors. from |
@davidzhao Have some raw thoughts about simplified connection handling and skipping the Livekit websocket and connect video rooms using existing web sockets (we're running 2 web sockets for already). Still i'm not sure its possible. @osmanhomek Thanks I've seen already |
WHIP is a good move for the industry, and we do plan to support it. My question is trying to understand the use cases that you are trying to achieve today, and how critical is WHIP to those use cases. |
We're not planning on WHIP right now, just a thought. Regarding your question: We need to connect to 2-3 different sources and show them in single Livekit room. If all 3 support WHIP the connection handling will be simple and easy to integrate. In short there will be main livekit video room and 2 other video sources will be displayed on the same page. Currently we're proxying in the backend. |
That's good to know. Which sources are you ingesting from? |
WHIP has made it's way into OBS (albeit not an official release, yet). Would be really awesome to stream from OBS to LiveKit using WHIP. |
Gstreamer now supports WHIP, which makes ingesting any kind of source very easy using the Gstreamer pipeline. My use case is ingesting camera feeds (mostly with RTSP) into a room. |
We are looking into WHIP support now as part of our upcoming Ingress component. Will update here when we have news to share :) |
OBS Studio has a PR open now for WHIP support. |
then, will livekit support WHEP ? :> |
We are going to start with WHIP! and then see where it takes us :) |
What for WHEP |
Following this Larix already supports WHIP to ingest. https://www.youtube.com/watch?v=FVhRJQDwimo&ab_channel=Softvelum |
@davidzhao please would it be possible to get an update on WHIP status ( and when it would be supported in Livekit Cloud )? We are keen to switch from our webrtc datachannel solution to WHIP and avoid a long running process. I've seen some recent commits that suggest an implementation exists / is in the works; if it does exist how do we go about using it via the egress API? Many thanks! |
WHIP support will be shipping soon! The development will be taking place in our Ingress module |
We now have full WHIP support in Ingress. Docs: https://docs.livekit.io/server/ingress/ |
Is WHIP going to be supported in near future in LiveKit?
https://www.ietf.org/archive/id/draft-ietf-wish-whip-03.html
The text was updated successfully, but these errors were encountered: