JBM: JBM control gets the wrong information in case of non-20ms rendering frames

Basic info

• Commit SHA: 894ce68d
• Platform: all

Bug description

The JBM control logic needs some information about how much signal is buffered to determine if it drops/adds/time scale modifies packets and the amount of TSM applied. For non-20ms rendering frames, this information is currently not correct

Ways to reproduce

Run VoIP decoding with either -fr 5 or -fr 20 leads to non-BE