Skip to content

[Non-BE] Resolve "JBM: JBM control gets the wrong information in case of non-20ms rendering frames"

bayersrequested to merge
864-jbm-jbm-control-gets-the-wrong-information-in-case-of-non-20ms-rendering-frames into main

Reason why this change is needed

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. Also the decoded wave form length will differ depending on the chosen render frame size.

Description of the change

Make sure the JBM control logic does the same independent of the rendering frame size by keeping track of the 20ms rendering borders. Add flushing at the end of the decoding to make BE tests between 5/10/20ms rendering possible.

Affected operating points

  • Non-BE for JBM decoding (output file length differs due to the introduced flushing)
  • Produced bitstream is BE compared to previous state (no encoder change)

Related to #864 (closed)

Edited by bayers

Merge request reports