This message was deleted.

is this Cloud? or selfhosted?

@dry-elephant-14928 livekit is on cloud, server is running locally

can you describe your flow in more detail? this is using LiveKit Ingress?

yes livekit ingress is being used inside the golang web server which is being deployed locally using Docker

sorry I'm still not following.. it would be helpful if you illustrate step by step what's happening

1. I've developed a web-server using golang. 2. I'm using livekit-go-sdk inside that server to connect to livekit-cloud and do stuff with it. 3. I'm using basic room service and ingress service using ffmpeg. 4. This whole setup is working locally without using docker to deploy the web-server. By working, I mean the video is getting streamed using livekit ingress service. 5. When I'm using docker to deploy the web-server, the video stutters so much that its unwatchable.

thank you for the update Arnab, I see what you are doing now.. I'm assuming you are encoding from FFmpeg to RTMP and then feeding into Ingress? FYI, we will also support the ability of sending any file to Ingress via URL pull (docs will be ready in the next few days)

Oh great! but how does that work? so no need to use ffmpeg encoding?

Ingress pulls the file via HTTP, and handles transcoding internally

@dry-elephant-14928 I can see the updated docs for ingress media pull, I wanted to know how to figure out that the stream is finished after I use this feature? for the ffmpeg one, the stream would've finished when ffmpeg process stopped.

Hey @rough-grass-53340, there are several ways to find out: • Ingress state would have changed • the participant you've indicated would have left the stream there should be webhook events for both of the above