File encoded with 'Fraunhofer Encoding and Muxing Tool' fails to decode about libmpegh

[SakethSathuvalli]

@SakethSathuvalli thanks for your reply. If I understand correctly, this sounds to me like the encoder was breaking the specification for LC profile, is that correct?

Yes, that was our first inference based on the initial debugging.

However, when we tried decoding the files with DRC processing disabled and with a fix (currently available only internally) for handling configuration packets, We see that the whole file gets decoded fine.

We are currently debugging the bit-streaming parsing path in the DRC module since enabling this is resulting in decode failure.

[Update]

The files You shared are decoding fine with the reference software. We were not using the correct reference executable for decoding when we faced the decode failure. We will check the issue with our decoder and share a fix at the earliest.

Thanks,
Saketh

[amiartus]

the tool is part of 'Fraunhofer MPEG-H Authoring Suite' https://www.iis.fraunhofer.de/en/ff/amm/dl/software/mas.html

the tool used to create the audio files is called 'MPEG-H Encoding and Muxing Too'

[SakethSathuvalli]

Hi @miartad - We tried decoding these streams with the reference decoder that comes from ISO. The reference decoder also throws up the error on the lines of sampling frequency (for the file https://github.com/ittiam-systems/libmpegh/assets/2679418/c7b4b3e7-a19a-4cd0-b041-837cb029bfec).

if (td_config->fscale > FSCALE_MAX)
{
  return IA_MPEGH_DEC_EXE_FATAL_INVALID_FSCALE;
}

This error comes up when TD/switched mode is used in LC profile for streams with sampling frequency greater than 32000 Hz.(restriction put by the specification for LC profile).

We will give a try with mhas files extracted from the mp4 files once.

[amiartus]

@SakethSathuvalli thanks for your reply. If I understand correctly, this sounds to me like the encoder was breaking the specification for LC profile, is that correct?

[SakethSathuvalli]

@SakethSathuvalli thanks for your reply. If I understand correctly, this sounds to me like the encoder was breaking the specification for LC profile, is that correct?

Yes, that was our first inference based on the initial debugging.

However, when we tried decoding the files with DRC processing disabled and with a fix (currently available only internally) for handling configuration packets, We see that the whole file gets decoded fine.

We are currently debugging the bit-streaming parsing path in the DRC module since enabling this is resulting in decode failure.

[amiartus]

Hi @SakethSathuvalli, thank you for clarification, do you have a plan for releasing a fix for this issue?

[SakethSathuvalli]

Hi @miartad,

Yes, We will be uploading the same. We are currently working on it. We will be uploading it after testing it on all platforms.

Can You let us know the tool You have used to generate these files ?

Thanks,
Saketh

[benjamin-weiss]

Hi @SakethSathuvalli,

it sounds like you were already working on a fix, but it was never released. Do you have any news when this fix will be available? Thanks!
Benjamin

[SakethSathuvalli]

Hi @benjamin-weiss,

Sorry for the delay! We will have this fix uploaded by early next week.

Thanks!

[SakethSathuvalli]

Hi @benjamin-weiss,

The fix is now available on main.

Thanks!

[benjamin-weiss]

I just confirmed that the files are now decodable. So feel free to close this issue. Thanks!

[SakethSathuvalli]

Hi @benjamin-weiss ,

Can You please comment on this issue as well #60 ?