We continue to have corrupt Composite output from the LiveKit cloud roughly 5% of the time. • "egress_id":"EG_ArtFvLdWJ6un" • the ogg and webm files are all good, just the final composite is bad • the composite is configured as 4k resolution HLS in 6 second chunks • we have multiple cameras and a screen share coming in and the screen share can be 1080p or higher 1. Can you check what the issue is - is it on your end with your server not handling that much IO/CPU 2. Can you provide us with a gstreamer or ffmpeg python script that will create a composite from the json files? We can't get the audio to sync properly with the video and it's overly complex to stitch it all together, especially if the screenshare files have their own video. This has been an ongoing issue we have reported a few times and we'lre looking for a workflow to solve it. Thank you!

Thanks for reporting this @gorgeous-elephant-19666. Looking at the egress request for EG_ArtFvLdWJ6un - it's a track egress but found a track composite egress for the same track id, this is a track composite recording a single video track as HLS segments with no audio. Since you mentioned multiple cameras and a screen share — are you running separate track composite egresses per track and then stitching the outputs together? That would explain why individual ogg/webm files are fine but the final composite has issues. Syncing outputs from separate egresses is inherently fragile since each has its own independent clock and start time. If you need a single composited output with all participants and screen share, that's exactly what room composite is designed for — it handles the mixing, layout, and sync internally so you don't need to stitch anything in post.