Skip to content

OMASA rateswitch to PARAM_ONE_OBJ uses invalid data for the first 2sf

Basic info

  • Commit SHA: c6ae2d8d (main)
  • Platform: all

Bug description

When the bitrate switching in the decoder enters the OMASA mode PARAM_ONE_OBJ from another mode, the object metadata in st_ivas->hMasaIsmData is not zeroed and may contain old values. Since the reading and writing of this ringbuffer -like structure is done with an offset of 2 sub-frames the values read for the first 2 subframes are invalid. When staying in the mode, the ringbuffer content is valid.

Ways to reproduce

(Clear steps or refer to a failing automated test, e.g. with a pipeline link)