Home of the Squeezebox™ & Transporter® network music players.
Page 157 of 159 FirstFirst ... 57107147155156157158159 LastLast
Results 1,561 to 1,570 of 1582
  1. #1561
    Senior Member sle118's Avatar
    Join Date
    Dec 2009
    Location
    Quebec City, Canada
    Posts
    494
    Quote Originally Posted by SlimChances View Post
    I saw an article for wireless speakers that are self charging (the speaker is covered in solar panels). It uses Bluetooth . I am afraid I am not technically minded enough to know if this will work with ESP-32. Can anybody comment?
    https://www.yankodesign.com/2022/05/...-to-be-charged
    https://www.kickstarter.com/projects...wered-speakers
    AFAIK, this is just a Bluetooth speaker and the squeezelite-esp32 can definitely stream to it, although this certainly not the the use case we optimized the software for.
    LMS 7.9 - 1xRadio, 1xBoom, 5xDuet,3xTouch, 1 SB2. Sony PlayStation, Emby, Chromecast v1 and v2 and...
    6xSqueezeAmp, several other ESP32-Wrover boards with jumper wires flying around, some with ethernet!

  2. #1562

    Latest 4.3 build

    Can somebody upload the latest 4.3 build (I2S-4M-16)? The assets of the latest push in the 4.3 branch are expired.

    https://github.com/sle118/squeezelit...uns/1938503535

    Thank you

  3. #1563
    Senior Member sle118's Avatar
    Join Date
    Dec 2009
    Location
    Quebec City, Canada
    Posts
    494
    Quote Originally Posted by martymcbro View Post
    Can somebody upload the latest 4.3 build (I2S-4M-16)? The assets of the latest push in the 4.3 branch are expired.

    https://github.com/sle118/squeezelit...uns/1938503535

    Thank you
    I triggered another build. Thanks for reporting

    https://github.com/sle118/squeezelit...uns/2443074704
    LMS 7.9 - 1xRadio, 1xBoom, 5xDuet,3xTouch, 1 SB2. Sony PlayStation, Emby, Chromecast v1 and v2 and...
    6xSqueezeAmp, several other ESP32-Wrover boards with jumper wires flying around, some with ethernet!

  4. #1564
    Quote Originally Posted by sle118 View Post
    I triggered another build. Thanks for reporting

    https://github.com/sle118/squeezelit...uns/2443074704
    I installed the latest 4.3 build and I'm having the following questions:

    1. When I choose the new preset option "ESP32A1S Old model", which is the correct one for my board, it breaks my display configuration because I'm using the GPIOs 21 and 22 for the display. The reason is that the preset seems to insert the value "21=amp,22=green:0,39=jack:0" into the parameter set_GPIO. When I remove it everything is working again. It's not a big deal but I would have expected that the preset only sets the board specific hard-wired IOs, e.g. for the DAC. Or is it my fault to use GPIOs 21 and 22?

    2. What do I have to do to get the new cspot integration running? The service is enabled and I have set a Device name. I can see the player in the spotify app but when I connect to it, it gets stuck in "connecting". I have a premium account and a working spotty lms plugin. Telnet says the following:

    I ZeroconfAuthenticator.cpp:37: Got request for adding user
    D Session.cpp:39: Connecting with AP <ap-gew1.spotify.com:40
    70>
    D PlainConnection.cpp:70: Connected to spotify server
    D Session.cpp:42: Sending APHello packet...
    D Session.cpp:102: Processing AP hello response...
    D Session.cpp:104: Received AP hello response
    D Session.cpp:150: Received shannon keys
    E Session.cpp:90: Authorization declined
    I (397655) cspot: Creating Spotify (using CSpot) player
    I (397655) cspot: Shutting down CSpot player
    I PlainConnection.cpp:175: Closing socket...

    Thank you and best regards

  5. #1565
    Senior Member sle118's Avatar
    Join Date
    Dec 2009
    Location
    Quebec City, Canada
    Posts
    494
    Quote Originally Posted by martymcbro View Post
    I installed the latest 4.3 build and I'm having the following questions:

    1. When I choose the new preset option "ESP32A1S Old model", which is the correct one for my board, it breaks my display configuration because I'm using the GPIOs 21 and 22 for the display. The reason is that the preset seems to insert the value "21=amp,22=green:0,39=jack:0" into the parameter set_GPIO. When I remove it everything is working again. It's not a big deal but I would have expected that the preset only sets the board specific hard-wired IOs, e.g. for the DAC. Or is it my fault to use GPIOs 21 and 22?

    2. What do I have to do to get the new cspot integration running? The service is enabled and I have set a Device name. I can see the player in the spotify app but when I connect to it, it gets stuck in "connecting". I have a premium account and a working spotty lms plugin. Telnet says the following:

    I ZeroconfAuthenticator.cpp:37: Got request for adding user
    D Session.cpp:39: Connecting with AP <ap-gew1.spotify.com:40
    70>
    D PlainConnection.cpp:70: Connected to spotify server
    D Session.cpp:42: Sending APHello packet...
    D Session.cpp:102: Processing AP hello response...
    D Session.cpp:104: Received AP hello response
    D Session.cpp:150: Received shannon keys
    E Session.cpp:90: Authorization declined
    I (397655) cspot: Creating Spotify (using CSpot) player
    I (397655) cspot: Shutting down CSpot player
    I PlainConnection.cpp:175: Closing socket...

    Thank you and best regards
    For some reason I deleted my answer regarding spotify, but in short that is still a work in progress for now.

    As for the GPIO, I believe GPIO21 is mapped to the "PA" pin. see here:
    https://github.com/Ai-Thinker-Open/E..._2/board_def.h
    LMS 7.9 - 1xRadio, 1xBoom, 5xDuet,3xTouch, 1 SB2. Sony PlayStation, Emby, Chromecast v1 and v2 and...
    6xSqueezeAmp, several other ESP32-Wrover boards with jumper wires flying around, some with ethernet!

  6. #1566
    Quote Originally Posted by sle118 View Post
    For some reason I deleted my answer regarding spotify, but in short that is still a work in progress for now.

    As for the GPIO, I believe GPIO21 is mapped to the "PA" pin. see here:
    https://github.com/Ai-Thinker-Open/E..._2/board_def.h
    OK, thank you for the answers.

  7. #1567

    Interesting board

    Hi,
    by accident I stumbled into the following ESP32 board + audio expansion. I think it would be nice to run squeezelite-esp32 on it.

    https://www.makerfabs.com/eps32-audio-player.html

    https://www.makerfabs.com/makepython-esp32.html

    https://www.makerfabs.com/makepython-audio.html

    https://www.makerfabs.com/esp32-audio-fixture-kit.html

    You can buy it with a wrover with 8MB PSRAM. Additionally it includes a 1,3'' SSD1306/SSD1315 display. The audio board uses a UDA1334ATS I2S DAC.

    Do you think squeezelite-ESP32 will run out of the box on it? I'm thinking about ordering one.

  8. #1568

    TAS5754 driving me crazy

    So I connected my Wrover (TTGO T8) module to my TAS5754 DAC (Wondom AA-AB32256) as this:
    AA-AB32256 pin TTGO T8 pin I2S signal
    LRCK 25 ws
    BCLK 33 bck
    SDATA 32 do
    GND GND
    3V3 3V3

    I set my dac_config as this:
    model=I2S,bck=33,ws=25,do=32

    I commit the nvs settings and reboot and ... boom !!! The music played through the attached speaker !

    Youhooo !!! Increadible.

    Then I thought I would add the 21=green:0 to the set_GPIO setting.
    I did commit and reboot but nothing played.

    I did set telnet_enable to y, commit, reboot, telnet to the box and saw:
    Code:
    Running version: I2S-4MFlash.16.1023.master-cmak
    ...
    ...
    [00:00:01.342310] output_init_embedded:70 init device: I2S
    [00:00:01.343327] equalizer_init:42 initializing equalizer
    [00:00:01.344132] output_init_common:433 supported rates: 192000 176400 96000 88200 48000 44100 32000 24000 22050 16000 12000 11025 8000
    [00:00:01.344383] output_init_embedded:92 init I2S/SPDIF
    W (2965) DAC core: DAC does not use i2c
    E (2965) i2c: /opt/esp/idf/components/driver/i2c.c:1273 (i2c_master_cmd_begin):i2c driver not installed
    W (2965) DAC core: I2C read failed
    E (2965) i2c: /opt/esp/idf/components/driver/i2c.c:1273 (i2c_master_cmd_begin):i2c driver not installed
    W (2965) DAC core: I2C read failed
    W (2965) TAS575x/8x: No TAS57xx detected
    E (2965) i2c: /opt/esp/idf/components/driver/i2c.c:353 (i2c_driver_delete):i2c driver install error
    I (2965) I2S: DMA Malloc info, datalen=blocksize=2048, dma_buf_count=12
    I (2965) I2S: APLL: Req RATE: 44100, real rate: 44099.988, BITS: 16, CLKM: 1, BCK_M: 8, MCLK: 11289597.000, SCLK: 1411199.625000, diva: 1, divb: 0
    [00:00:01.347188] output_init_i2s:319 TAS57xx DAC using I2S bck:33, ws:25, do:32, mute:-1:0 (res:-1)
    [00:00:01.347493] output_init_i2s:326 no DAC configured
    I checked several times the cables. Everything is fine.
    I checked around to see if anything on the table could have shorted something and broken the amp. There is no such thing.
    Power is applied to the amp and the power led is on.
    The busy led remains off (while when it first worked (before I tried the led parameter), the "busy" led was on unless I was stopping playback).

    How can I debug the TAS5754 detection ?
    I have no data analyser at hand at the moment.

    This is even more frustrating as it worked fine for an hour.

    Thank you in advance for your support.

    EDIT: I now found the reason: https://forums.slimdevices.com/showt...=1#post1056145
    Last edited by zorglups; 2022-06-13 at 14:07. Reason: Set the dac_config to the value it was really and added the root cause

  9. #1569
    Junior Member
    Join Date
    Jun 2022
    Posts
    1

    Some questions after playing around with this

    I've been looking around at what exists regarding multiroom audio systems, and i've got some ESP32's lying around, so decided to check this project out .

    Got it to work pretty nicely, but i've got a question:

    The documentation mentions "Stream from a Bluetooth device (iPhone, Android)": After trying a bit, i assume this just means that instead of audio coming from LMS, you can just stream directly to the ESP32 via bluetooth? I hoped this would mean i could use an ESP32 to connect to with an android device, and then whatever it receives gets sent to LMS, but that doesn't seem to be the case?

    Are there ways to achieve the above? Stream from an android device (or whatever else) via bluetooth to LMS?

  10. #1570
    Quote Originally Posted by racemaniac View Post
    I've been looking around at what exists regarding multiroom audio systems, and i've got some ESP32's lying around, so decided to check this project out .

    Got it to work pretty nicely, but i've got a question:

    The documentation mentions "Stream from a Bluetooth device (iPhone, Android)": After trying a bit, i assume this just means that instead of audio coming from LMS, you can just stream directly to the ESP32 via bluetooth? I hoped this would mean i could use an ESP32 to connect to with an android device, and then whatever it receives gets sent to LMS, but that doesn't seem to be the case?

    Are there ways to achieve the above? Stream from an android device (or whatever else) via bluetooth to LMS?
    The easiest way to stream from a mobile to LMS is to use picoreplayer: http://picoreplayer.org/

    You can enable bluetooth support and pair your phone using the Web UI. Then you have to enable the "Streamer for audio input" on the tweaks page. This will convert the bluetooth input to a network stream which
    can then be added to LMS.

    Before this, I also used the Line-In Plugin in LMS to stream from the input of a connected USB sound card, but this was rather complicated to setup.

    As far as I remember the Raspberry Pi 3 had problems when using Bluetooth and Wifi simultaneaously so I was using an additional bluetooth dongle. Don't know if this is still required when using a Pi 4.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •