This message was deleted.
# helpdesk
s
This message was deleted.
e
Sorry, that's a very broad question. Can you elaborate on what those needs are?
k
for a seamless live streaming
e
Yes, we support that
k
Can you suggest me some proof of concept for reference
We need sub-second latency (ideally <200ms), especially in situations like the video keypad where we need to allow talk-back
e
You can try the sample apps located here: https://github.com/livekit/client-sdk-android
👍 1
k
I already tried that, but I just want to understand why I should opt for LiveKit
Actually we need sub-second latency (ideally <200ms), especially in situations like the video keypad where we need to allow talk-back. Does LiveKit meets my need?
e
Yes, we can do sub-second latency. This will ultimately depend on your latency to the server of course, but sub second is easily doable
k
Can you please tell me some advantages
e
cc: @magnificent-art-43333 @dry-elephant-14928
d
@kind-alligator-70925 take a look at https://livekit.io/use-cases/livestreaming, https://livekit.io/cloud, and other product pages. they should cover the benefits of LiveKit well. let us know if you have any follow up questions
k
Does livekit uses WebRTC-HTTP egress protocol(WHEP) or WHAP
Someone please help me on this
e
cc @able-gigabyte-21598
m
@kind-alligator-70925 in what context do you need WHEP? We don’t support it at this time.
k
WebRTC explicitly decided not to adopt any signaling protocol for the media streaming industry. However, this decision proved to be less than ideal, as there was a need for a well-known protocol with ready-made implementations. This necessity led to the development of WHIP and WHEP.
m
Right, just wondering what you’re trying to build such that you need WHIP and WHEP.