Skip to content

[NON-BE] Fix bad decoded direction values for FER in OMASA

vasilacherequested to merge
944-bad-decoded-direction-values-for-fer-in-omasa-one-separated-object into main

Reason why this change is needed

  • The separated object metadata for the MASA representation case in OMASA, under FER conditions decodes incorrect values during and after separated object change if the differential encoding is used to the object directional metadata because it refers to metadata of the wrong object.

Description of the change

  • The object change in the separated object is identified and the direction encoding is forced to absolute coding for the current and a number of following frames.

Affected operating points

  • OMASA modes using one separated object with MASA representation modes (OMASA at 32kbps, 48kbps for 3 and 4 objects, and OMASA with 2 objects at 32kbps)

  • NONBE for the above mentioned modes, but decodable (BC).

  • Difference is both in object metadata and in output audio. Only the audio in the object is affected, but depending on the input format it will transmit to the overall audio output.

Related to #944 (closed)

Edited by vasilache

Merge request reports