"[E] AudioStreamsConverter.h : 565 - bit combination not supported 16 -> 0" on XIAO ESP32C3 and ESP32S3

[forresto]

I checked out arduino-audio-tools and arduino-libhelix from git today.

Starting from streams-url_mp3-out.ino example.

In the serial monitor I see a loop of:

[E] AudioStreamsConverter.h : 565 - bit combination not supported 16 -> 0

Do the pins need to be configured for the XIAO boards?

[forresto]

If you're coming here trying to play internet radio with a XIAO ESP32C3, and also have an Adafruit max98357 I2S mono amp, the streams-url_mp3_helix-i2s example does work!

With these config additions:

  // LRC
  config.pin_ws = D0;
  // BCLK
  config.pin_bck = D1;
  // DIN
  config.pin_data = D2; 

[pschatzmann]

Why would you even try to use the AnalogAudioStream knowing that there is no DAC on the ESP32-S3 ?
I suggest you check the return code of begin(): I am pretty sure that in this case it returns false. In addition you just ignored the relevant error message that comes before:

16:20:03.549 -> [I] StreamCopy.h : 173 - StreamCopy::copy 1024 -> 1024 -> 1024 bytes - in 1 hops
16:20:03.549 -> [I] AudioTypes.h : 124 - MP3DecoderHelix sample_rate: 48000 / channels: 2 / bits_per_sample: 16
16:20:03.549 -> [I] AnalogAudioStream.h : 46 - virtual void audio_tools::AnalogAudioStream::setAudioInfo(audio_tools::AudioInfo)
16:20:03.549 -> [I] AudioTypes.h : 124 - sample_rate: 48000 / channels: 2 / bits_per_sample: 16
16:20:03.549 -> [I] AnalogAudioStream.h : 72 - virtual void audio_tools::AnalogAudioStream::end()
16:20:03.549 -> [I] AnalogDriverESP32V1.h : 71 - virtual void audio_tools::AnalogDriverESP32V1::end()
16:20:03.549 -> [I] AnalogAudioStream.h : 66 - bool audio_tools::AnalogAudioStream::begin(audio_tools::AnalogConfig)
16:20:03.549 -> [I] AnalogDriverESP32V1.h : 41 - virtual bool audio_tools::AnalogDriverESP32V1::begin(audio_tools::AnalogConfigESP32V1)
16:20:03.549 -> [E] AnalogDriverESP32V1.h : 455 - DAC not supported

[forresto]

there is no DAC on the ESP32-S3

I didn't realize that.

you just ignored the relevant error message that comes before

I couldn't catch the first error messages because of how many 565 - bit combination not supported 16 -> 0 messages were in the serial monitor.