Handle Participant Reconnect for Track Egress - H2...
# ask-ai
c
Handle Participant Reconnect for Track Egress - H264/WEBM
t
Thanks for reaching out, shahi. I'm an AI assistant and I'm here to help. Give me a moment while I research this topic.
I'd love to better understand what you're aiming to achieve with participant reconnect and tracking egress for H264/WEBM. Are you running into any errors when reconnecting, or would you like some guidance on how to set up a particular feature? Feel free to share more details so I can assist you more effectively!
c
some guidance on how to set up a particular feature?
t
I'd love to better understand your goal with setting up participant reconnect handling alongside track egress. Could you share a bit more about what you're aiming for? For example: • Are you hoping to keep the recording seamless even when a participant reconnects? • Are you working with H264 or WEBM for track publishing, and want these formats to be preserved during egress after a reconnect? • Are you starting egress through a server SDK, or are you using auto-egress settings? Sources: Connecting to LiveKit | LiveKit Docs | pkg/rtc/participant.go | packages/livekit-server-sdk/src/EgressClient.ts | livekit/src/room/mod.rs
c
yes I need all of this . using aut egress settings
t
I don't have the answer you're looking for. You could also try asking your question: • in one of the other Slack channels or • to https://deepwiki.com/livekit/livekit_composite which is trained on all LiveKit source code If you find the answer, please post it here to help others!