Closed y-nk closed 1 month ago
What esp32 core version are you using ? Did you try with another version ? Did you also try to optimize the A2DP configuration settings ?
I think CodecMP3MAD is using much more resources so I don't think that this is a good idea here... Did you see any errors or warnings in the log ? Since you use A2DP also activate the ESP32 logging
auto_reconnect
but buffer_size
and delay_ms
are things I'm gonna play with now.I've explored further how to achieve my project, trying to make the Helix example work flawlessly and found another panic when using Helix and a 64kbps mp3. I'm starting to wonder if it's not all the fault of the uSD reader i own + the custom VSPI pins i'm using.
I think you should wirte some separate test cases to pin down the issue
My conclusion is that you are running out of RAM. A2DP is not leaving much RAM available and MP3 decoding also needs considerable RAM.
Monitor the RAM usage and better activate and use PSRAM
Thank you, it seems a good diagnostic indeed.
Problem Description
I've been trying to swap Codec Helix to the MAD one. At build I had a bunch of warnings such as these ones:
But then when running, I have a panic with the following stacktrace:
Device Description
ESP32-D0WD-V3
Sketch
Other Steps to Reproduce
Swapping the Helix decoder back looks like working fine except for the hashed output on the speaker.
What is your development environment
No response
I have checked existing issues, discussions and online documentation