DEFAULT_ESP_M4A_DECODER_CONFIG vs DEFAULT_AAC_DECODER_CONFIG
Posted: Fri Jan 10, 2020 11:22 am
Hi,
When we use the DEFAULT_AAC_DECODER_CONFIG in audio pipelines, the audio is very clear. But when we use DEFAULT_ESP_M4A_DECODER_CONFIG in esp_audio with auto-decoder-detection and the track uses two channels, there is a background noise (like scratching/popping backgournd noise) in one of the channels only. Have you come across a similar issue? What is the deference between these two decoder implementations?
Also, is there a way to force DEFAULT_AAC_DECODER_CONFIG using esp_audio library, without auto decoder detection, on files without extension?
Thank you in advance,
Christos
When we use the DEFAULT_AAC_DECODER_CONFIG in audio pipelines, the audio is very clear. But when we use DEFAULT_ESP_M4A_DECODER_CONFIG in esp_audio with auto-decoder-detection and the track uses two channels, there is a background noise (like scratching/popping backgournd noise) in one of the channels only. Have you come across a similar issue? What is the deference between these two decoder implementations?
Also, is there a way to force DEFAULT_AAC_DECODER_CONFIG using esp_audio library, without auto decoder detection, on files without extension?
Thank you in advance,
Christos