LiveKit Community

Hey <@U03C8KQDJMA>, 2 things here
• This `pipeline frozen` issue is an issue I’ve been working on, related to latencies, synchronization, and timestamping. There are a lot of moving pieces, so I already have some updates written that are still unreleased, but I’m hoping to have it all solidified this week.
• `duration`, `size`, and `location` are empty because it failed to close out the file. The resulting file is just an empty mp4. However, that is a bug that the status is `ENDING` instead of `FAILED` with no `endedAt` set. I’ll add that to my backlog to look at after the timestamping issues.

Thanks for your effort <@U01UB0LHTTQ>!
It's good to hear that it's a known issue that is taken care of.

If there is anything right now we can already adjust in a k8s setup to prevent such an issue, let me know please.

Hi <@U01UB0LHTTQ>

I'm wondering if there is a related Github ticket to the *'pipeline frozen'* issue?

Am I right, that your recent commits and PRs (<https://github.com/livekit/egress/branches/active>) could hopefully improve the situation?

Thanks again for your help!

There isn't a GitHub issue for it, but my past 5 or so PRs to egress and server-sdk-go have been addressing it. I'll be releasing a new egress version tomorrow and I'm hoping the issue is fully resolved

We are so excited to test the new Egress release 1.7.2 :partying_face:
I'm sure, we will give a feedback soon.