LiveKit Community

Thank you <@U01UB0LHTTQ> and <@U01KZ0SCDKL> for your fast response!

The reason we haven't updated yet is a different behaviour in the output's frame rate.
Our aim is to get a constant rate. Unfortunately we noticed variable frame rates in 1.4 and higher.

That was an experiment to save on CPU, but it introduced other issues so the behavior was reverted in v1.6.3

By the way, the `pipeline frozen` error is due to timestamping issues, where even if the egress finished the file would be broken. I’ve done a lot of work in the 1.6 versions to solve it, but you might still get an occasional `timestamping issue` error even after updating (but the egress should end properly). I plan on having it fully resolved in v1.7.1

<@U01UB0LHTTQ>
So we can hope for constant frame rates since v1.6.3?
This sounds amazing!

<@U01UB0LHTTQ>
Thank you again for your explanation.