[Non-BE][allow-regression] Resolve "MASA part rendering of OMASA does not always follow correct path in internal renderer"

Tapani Pihlajakujarequested to merge
float-1600-masa-part-rendering-of-omasa-does-not-always-follow-correct-path-in-internal-renderer into main

Reason why this change is needed

  • As described in issue, MASA part of OMASA does not follow correctly the same rendering path as MASA when rendering to Ambisonics.

Description of the change

  • Change one condition for MASA stereo type init check in internal rendering.

Affected operating points

  • Non-BE decoder only
  • OMASA 32 kbps and up when rendering to FOA/HOA (in theory, Mono output could also be affected)

Merge request reports