RexSystem1 voteoriginally by @Armindster on GitHub
Can confirm that still happens in stable build 87 (28da28c)
Setting a user volume to anything more than 100% does reproduce the bug
Manually resetting the volume to 1 in the ParticipantVolumeStore in the local storage does fix it
Thread
Comment by @Armindster
volumeto 1 in theParticipantVolumeStorein the local storage does fix it