Recently we’ve been facing an issue with LiveKit peer-to-peer voice calls.
On our web platform ( NextJS + NodeJS), while people are recording their conversations via individual egress, we’ve noticed some noise appearing as brief plucking or crackling sounds—similar to a momentary loose microphone cable / Audio click / mic drag —lasting less than 1 second per occurrence but repeating multiple times within a session. I tried turning off autoGainControl: false and dtx: false as potential fixes, but we lost audio volume as a result and the issue remained persistent. Do you have any suggestions on what we can try to fix this issue?
Here’s our LiveKit configuration:
Call is working fine, both the user are able to hear each other fine without any crackling / distortion, but we get this issue in the egress recording
This issue was much less frequent earlier, but starting from early February 2026, it has been occurring in almost every session. We’ve tried changing the configuration by turning off DTX and autoGainControl, but the issue still persists. Is there anything specific we should check into?
Also here: While recording individual participants Egress Crackling sounds is coming up in between after Feb 2026 · Issue #1133 · livekit/egress · GitHub
Hello @Ravi_Agheda,
Thanks for reporting! To get a better picture - could you share an egressID of the affected recording? You mentioned individual recordings - do you use track egress requests for these? We should be able to see more from logs once we have the ID (assuming you are using cloud). If you use on-prem setup - we are going to need the service configuration and debug level logs capturing a session with the issue.
Best,
Milos
Hi @Milos_Pesic Thanks for the response,
We’re using LiveKit cloud and tracking egress to record the track’s audio,
Here’s the egressId of the affected recording: EG_rajMo9EQjEaj.
The crackling sound occurs around 41 seconds into the audio.
Let me know if you need more information
Thanks,
Ravi.
Thanks for the additional info @Ravi_Agheda - that was helpful - I can see the source of the issue - the fix will be available in the next egress release. Once deployed - I will let you know so you could double check.
Thanks,
Milos
1 Like
Thank you so much for the review @Milos_Pesic — that sounds good. If possible, could you share an estimated timeline for the next release? It would be very helpful for us to plan the next steps.
Thanks,
Ravi
Hey @Ravi_Agheda,
It should be deployed by the end of this week. I will let you know once it’s out.
Thanks,
Milos
1 Like
Hey @Ravi_Agheda,
The release with the fix has just been deployed - could you check if it fixes the issue? 
Thanks,
Milos
1 Like
Hi @Milos_Pesic ,
Thank you so much for getting back with the fix. We’ve already started testing the update, and it seems to be working better. We’re no longer facing the issue.
Thanks,
Ravi
2 Likes