Skip to content

EXT output for OMASA and OSBA: API_5MS wrong implementation in decodeG192()

Since the implementation and activation of API_5MS, some functionalities are lost.

In particular, I noticed a problem with the function decodeG192(). There is an inconsistency at least when calling the external MD writer: API_5MS activated

        /* Write ISm metadata to external file(s) */
        if ( decodedGoodFrame && arg.outputConfig == AUDIO_CONFIG_EXTERNAL )
        {
            if ( bsFormat == IVAS_DEC_BS_OBJ )

resp. API_5MS deactivated

        /* Write MASA/ISM metadata to external file(s) */
        if ( decodedGoodFrame && arg.outputConfig == AUDIO_CONFIG_EXTERNAL )
        {
            if ( bsFormat == IVAS_DEC_BS_OBJ || bsFormat == IVAS_DEC_BS_MASA_ISM || bsFormat == IVAS_DEC_BS_SBA_ISM )
            {

Consequently, the ETX output for OMASA and OSBA is broken.