ANNOUNCE: Squeezelite-ESP32 (dedicated thread)

[mark wollschlager]

Rolled back to development.148.master-cmake. It been solid all day.
No hangs or pauses.

[sle118]

Rolled back to development.148.master-cmake. It been solid all day.
No hangs or pauses.

I'm still working on a future release which I'm hoping will resolve some of the issues with the latest development builds.

Stay tuned!

[ElFishi]

Rolled back to development.148.master-cmake. It been solid all day.
No hangs or pauses.

fw: I2S-4MFlash.517.master-cmake, display removed from config. Has been playing ca 1h per day for a week or so. No glitches.

[mherger]

ANNOUNCE: Squeezelite-ESP32(dedicated thread)

> fw: I2S-4MFlash.517.master-cmake, display removed from config. Has been
> playing ca 1h per day for a week or so. No glitches.

Mine is playing much more than that ;-). Yes, playback seems to be
solid. But I've seen issues with the web UI (which I only see when I
want to know whether there's an update). sle118 is working on this.

--

Michael

[KeBul]

I agree that this board has its quirks, and having studied the schematic, it would appear that the green led is connected to a power/charge chip which is not addressable. My highly technical remedy for the overly bright green light, is a small square of insulating tape!��

Cheers, guess I'll be digging out the tape then.

Just out of curiosity where did you find the schematic, I've searched and the only link I found for it is now a 404.

While I'm here I'll throw this out there... has anyone managed to get any of the buttons/keys 1-6 working on the Ai Thinker Audio Development Board? At the moment I'm just trying to get Play and Pause working on two of them, been using the README.md on sle118/squeezelite-esp32 github and I'm sure I understand the principle plus I'm pretty sure the key to GPIO mapping information in there is correct (key3 to GPIO19 for example) and I've configured up following the examples but it's not working and I'm not seeing any report of a key press in telnet.

Update... Ha typical, when I ask for help, I stumble upon getting it working myself. Copied the example in the README.md for Volume up and down and that worked, so then changed the ACTRLS commands to PLAY and PAUSE respectively and that works, I'd previously tried to remove the long press and toggle stuff from that example to simplify it... I'll go back and try and understand what's needed and what isn't.
Big "Doh" moment, in the readme there's an example for buttons in the ESP32-A1S section, but then there's a more detailed general write up on configuring buttons further down, What I'd been trying was based on those examples, not the one supplied for the A1S, sigh what a muppet, when I copied the A1S example tonight... that's what worked.
Final word from me on the button config on A1S Audio Development...
Once more very impressed with the Squeezelite-ESP32 team, the button mapping example in the A1S section of github README.md provides for:

Button 6 - Play/Pause toggle
Button 5 - Volume up
Button 4 - Volume down

Button 6 is also a shift... press and hold and then
Button 5 - Skip forward to next track in queue
Button 4 - Skip backwards to previous track in queue

Top work guys.

Cheers

Kev

[philippe_44]

Cheers, guess I'll be digging out the tape then.

Just out of curiosity where did you find the schematic, I've searched and the only link I found for it is now a 404.

While I'm here I'll throw this out there... has anyone managed to get any of the buttons/keys 1-6 working on the Ai Thinker Audio Development Board? At the moment I'm just trying to get Play and Pause working on two of them, been using the README.md on sle118/squeezelite-esp32 github and I'm sure I understand the principle plus I'm pretty sure the key to GPIO mapping information in there is correct (key3 to GPIO19 for example) and I've configured up following the examples but it's not working and I'm not seeing any report of a key press in telnet.

Thanks for any help

Kev

Look at the log at boot to see if the key is configured

[KeBul]

Look at the log at boot to see if the key is configured

Thanks, Philippe, all working now, I've updated my post with more details and yes, now I can see the configured buttons in the log at boot.

Kev

[ElFishi]

fw: I2S-4MFlash.517.master-cmake, display removed from config. Has been playing ca 1h per day for a week or so. No glitches.

switched to fw: development.145-I2S-4MFlash yesterday and configured the display again: just had crash. No webinterface involved.

[funkybassman]

Cheers, guess I'll be digging out the tape then.

Just out of curiosity where did you find the schematic, I've searched and the only link I found for it is now a 404.

Kev

Here is the AI Thinker Audio Development board V2.2 schematic.

[KeBul]

Here is the AI Thinker Audio Development board V2.2 schematic.

Brilliant, thank you so much.

Kev

[ElFishi]

switched to fw: development.145-I2S-4MFlash yesterday and configured the display again: just had crash. No webinterface involved.

went to 142 yesterday.
just powered up the player and started a track: display shows title and VU-meter but no music. All frozen.
Stayed like this for a minute or so. Suddenly the music starts and everything is back to normal.

[KeBul]

went to 142 yesterday.
just powered up the player and started a track: display shows title and VU-meter but no music. All frozen.
Stayed like this for a minute or so. Suddenly the music starts and everything is back to normal.

I've been using 142 on 3 devices (2 SqueezeAMP and one A1S audio board) now for several weeks (if not longer on one of them), I've seen similar lack of responsiveness on first power up a few times, another power cycle or reset normally resolves.
The longest test period has been on one configured for I2S with speakers connected, so far this has been the most reliable set up and if left powered up is close to 100% reliable. Other two devices have primarily been using Bluetooth, with either a pair of Bose headphones, or an Anker Bluetooth speaker.
The Bose headphones can be really difficult to get up and running, thought at one stage I'd worked out the sequence needed to reliably connect and play, but not so sure now. The Anker speaker is much much better and easily connects and plays most of the time.

One thing I have found is the speed of boot can work against it, if the SA is rebooted and is back up before LMS has cleared disconnected/removed the instance of squeezelite then invariably the player will not play (this is only for Bluetooth I think and possibly more relevant to my Bose headphones), If I power off headphones, SA and wait for the squeezelite instance to be removed from LMS and then power everything back up again generally it will work.

One other thing with Bluetooth, just in case it helps others, I did have a period when the speaker kept connecting but I couldn't get it to play, turned out the beep on connection was my phone connecting to the speaker not the SA. Had me scratching my head a bit for a while.

Of course this is somewhat different to your setup, I've only run with a display for a short period to get one up and running and test for a while, but then filed it away until I take the time to permanently fix the display in the case and wire up up properly, and IIRC you are using SPDIF.

Kev

[ElFishi]

I've been using 142 on 3 devices ...

Thanks for sharing
I also run three systems, one of them (the last mentioned) S/PDIF, the others I2S.

I have now disabled Airplay and BT, and continue playing.

[bgiraut]

Hi

i have a receive my the Ai Thinker Audio Development Board yesterday and flash it with the last firmware with sucess. The board and the software work very well. I would like to know if it should possible to switch output mode (I2S/BT/SPDIF) with one of the key button on the board. I have saw it was possible de change volume or switch play/pause but found no "action" to switch output. Thx for your help.

[ElFishi]

How can I check which format is actually being streamed to the ESP?

I was trying to check the polarity of my DACs by means of a WAV file containing a 5 sample pulse @ 44.1kHz.
First picture is the output from my raspberry / piCorePlayer / ES9023 player, second is from ESP / ES9023.

I have the hunch that the difference has something to do with encoding, but how can I check?

In addition, I believe initially I had the same output from ESP and Raspberry. But when I tried to flip the polarity the ESP output went to the shape shown here and I could never flip it back.