Home of the Squeezebox™ & Transporter® network music players.
Page 92 of 106 FirstFirst ... 42829091929394102 ... LastLast
Results 911 to 920 of 1051
  1. #911
    Senior Member
    Join Date
    May 2008
    Location
    Canada
    Posts
    7,298
    Quote Originally Posted by Dominik82 View Post
    One more question for the ESP32-Hardware

    What is the almost-best quality DAC that I can connect to an ESP32-WROVER via I2S?
    At least I need stereo jack/cinch output
    Often I found boards with a PCM5102 chipset, which are quiete cheap. But in my mind the output quality will not be the best
    You can virtually use any DAC that accepts I2S, there is even now the possibility to add own I2C commands if needed. Re quality, well - you might open a can of worms with that question.
    LMS 8.2 on Odroid-C4 - SqueezeAMP!, 5xRadio, 5xBoom, 2xDuet, 1xTouch, 1xSB3. Sonos PLAY:3, PLAY:5, Marantz NR1603, Foobar2000, ShairPortW, 2xChromecast Audio, Chromecast v1 and v2, Squeezelite on Pi, Yamaha WX-010, AppleTV 4, Airport Express, GGMM E5, RivaArena 1 & 3

  2. #912
    Junior Member
    Join Date
    Feb 2021
    Location
    near Berlin
    Posts
    14
    Quote Originally Posted by Dominik82 View Post
    What is the almost-best quality DAC that I can connect to an ESP32-WROVER via I2S?:
    Good question, as reliable information on their audio quality seems to be available for Raspi HAT type DACs - and for the better ones special drivers are required for the raspi (and therefore not working out-of-the-box with squeezelite-esp32). This is also the case for the allo boss2 with its CS43198 DAC (which was also discussed in a different thread here, but in context of Raspi+PCP). Therefore I have now ordered a no-name board from aliexpress which is also based on the CS43198, but according to the (lack of) description does not require a special driver (https://www.aliexpress.com/item/1005002681132944.html). Digital filters can be set via jumpers and I am assuming that the standard I2C driver and connections are sufficient. However, I'm not aware that audio quality testing has been tested anywhere, but at least it should be significantly better that the rather old BB PCM5102(A) DAC - but even those could provide very good quality (like the DAC32, which has a similar BB DAC).

  3. #913
    Senior Member
    Join Date
    Feb 2008
    Posts
    422
    Quote Originally Posted by Dominik82 View Post
    One more question for the ESP32-Hardware

    What is the almost-best quality DAC that I can connect to an ESP32-WROVER via I2S?
    At least I need stereo jack/cinch output
    Often I found boards with a PCM5102 chipset, which are quiete cheap. But in my mind the output quality will not be the best
    The best measuring DAC on audioscience review that comes with I2S input is the Gustard X16

  4. #914

    ST7789 display issues

    Quote Originally Posted by philippe_44 View Post
    Did you notice that the pinout is inverted in the picture on GitHub and first post of the squeeezeamo thread ?
    Yes, I checked numerous configurations (and other ST7789 displays), but failed. Will check sle118's suggestion first before coming back again...

    Thank you all!

    C.

  5. #915
    Senior Member sle118's Avatar
    Join Date
    Dec 2009
    Location
    Quebec City, Canada
    Posts
    446
    Quote Originally Posted by shaffenmeister View Post
    Yes, I checked numerous configurations (and other ST7789 displays), but failed. Will check sle118's suggestion first before coming back again...

    Thank you all!

    C.
    The connector pinout was reversed on the picture, so for me that was the other key to success
    LMS 7.9 - 1xRadio, 1xBoom, 5xDuet,3xTouch, 1 SB2. Sony PlayStation, Emby, Chromecast v1 and v2 and...
    6xSqueezeAmp!
    Contributing to Folding@Home : https://stats.foldingathome.org/donor/squeezelite-esp32

  6. #916

    Flashing A1S Audio Kit V2.2 from OpenSuse

    Although the description in Post #1 is very good i did not know how to flash my new board (A1S Audio Kit V2.2) from an OpenSuse system. So I just want to write down what I did:

    1) Install esptool and pip
    zypper install pip
    pip install esptool

    2) Download firmware
    go to download page https://github.com/sle118/squeezelite-esp32/tags
    chose your version and click on downloads, eg. https://github.com/sle118/squeezelit...9.master-cmake
    (I tried to use the .bin file, but I did not know how to use with esptool.)
    download .zip file, eg. https://github.com/sle118/squeezelit...S-16-1.689.zip
    unzip

    3) Flash module
    Since the different bin files are in subdirectories, you have to change path names of command from post #1:
    ~/.local/bin/esptool.py --chip esp32 --port /dev/ttyUSB0 --baud 115200 --before default_reset --after hard_reset write_flash -z --flash_mode dio --flash_freq 80m --flash_size detect 0xd000 ota_data_initial.bin 0x1000 bootloader/bootloader.bin 0x10000 recovery.bin 0x8000 partition_table/partition-table.bin
    let module reboot

    4) Configure board and update
    use smartphone to login new access point as described in post #1 ==> config site of the module will open automatically
    enter your wifi password
    reboot module
    connect to module via browser
    Since the board did not store my wifi password, I started again at 4)...
    update firmware like described on https://github.com/sle118/squeezelite-esp32, section configuration
    (I used the same firmware version I already flashed. After that the board stored my wifi password.)

    5) Configure and use board for your own purpose

  7. #917

    dac_config for Audio Kit V2.2? / dac does not work

    I configured the AI Audio Kit V2.2 (like this one) as described here:

    So a possible config would be
    set_GPIO: 21=amp,22=green:0,39=jack:0
    dac_config: model=AC101,bck=27,ws=26,do=25,di=35,sda=33,scl=32

    The relevant part in my NVS config it is:

    "dac_config": "model=AC101,bck=27,ws=26,do=25,di=35,sda=33,scl=3 2",
    "dac_controlset": "",
    "set_GPIO": "21=amp,22=green:0,39=jack:0",

    Dip switches are: off, off, off, on, on

    When I plug in my earphones the indicator icon upper right in the web ui shows up. So gpio 39 seems to work.

    Unfortunately the dac does not work (no sound on speaker neither on headphone). The model does not seem to be AC101. The console log tells me:

    [00:00:04.330990] output_init_embedded:86 init I2S/SPDIF
    [0;32mI (5997) DAC core: DAC uses I2C port:0, sda:33, scl:32
    [0;33mW (5997) DAC core: I2C read failed
    [0;33mW (6007) AC101: No AC101 detected
    [0;32mI (6007) I2S: DMA Malloc info, datalen=blocksize=2048, dma_buf_count=12
    [0;32mI (6017) 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:04.369230] output_init_i2s:318 AC101 DAC using I2S bck:27, ws:26, do:25, mute:-1:0 (res:-1)
    [00:00:04.370583] output_init_i2s:325 no DAC configured


    Any hint to solve my problem? Which config works for you? Which dac model shoud I configure?

  8. #918
    Senior Member
    Join Date
    May 2008
    Location
    Canada
    Posts
    7,298
    Quote Originally Posted by jofland View Post
    I configured the AI Audio Kit V2.2 (like this one) as described here:

    So a possible config would be
    set_GPIO: 21=amp,22=green:0,39=jack:0
    dac_config: model=AC101,bck=27,ws=26,do=25,di=35,sda=33,scl=32

    The relevant part in my NVS config it is:

    "dac_config": "model=AC101,bck=27,ws=26,do=25,di=35,sda=33,scl=3 2",
    "dac_controlset": "",
    "set_GPIO": "21=amp,22=green:0,39=jack:0",

    Dip switches are: off, off, off, on, on

    When I plug in my earphones the indicator icon upper right in the web ui shows up. So gpio 39 seems to work.

    Unfortunately the dac does not work (no sound on speaker neither on headphone). The model does not seem to be AC101. The console log tells me:

    [00:00:04.330990] output_init_embedded:86 init I2S/SPDIF
    [0;32mI (5997) DAC core: DAC uses I2C port:0, sda:33, scl:32[0m
    [0;33mW (5997) DAC core: I2C read failed[0m
    [0;33mW (6007) AC101: No AC101 detected[0m
    [0;32mI (6007) I2S: DMA Malloc info, datalen=blocksize=2048, dma_buf_count=12[0m
    [0;32mI (6017) 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[0m
    [00:00:04.369230] output_init_i2s:318 AC101 DAC using I2S bck:27, ws:26, do:25, mute:-1:0 (res:-1)
    [00:00:04.370583] output_init_i2s:325 no DAC configured


    Any hint to solve my problem? Which config works for you? Which dac model shoud I configure?
    Have you tried to download the specially-build binary for A1S? I've not verified in a while that the I2S version with that config still matches the custom build, so maybe I've forgotten something there
    LMS 8.2 on Odroid-C4 - SqueezeAMP!, 5xRadio, 5xBoom, 2xDuet, 1xTouch, 1xSB3. Sonos PLAY:3, PLAY:5, Marantz NR1603, Foobar2000, ShairPortW, 2xChromecast Audio, Chromecast v1 and v2, Squeezelite on Pi, Yamaha WX-010, AppleTV 4, Airport Express, GGMM E5, RivaArena 1 & 3

  9. #919
    Quote Originally Posted by philippe_44 View Post
    Have you tried to download the specially-build binary for A1S? I've not verified in a while that the I2S version with that config still matches the custom build, so maybe I've forgotten something there
    Yes, in Post #916 I described what I did.

    I downloaded: https://github.com/sle118/squeezelit...S-16-1.689.zip

    Then updated with the web ui the same version again.

    The same behavior is with 1.665-16 and dev.653-16.


    The strange thing is, if I change the dac_config from

    dac_config: model=AC101,bck=27,ws=26,do=25,di=35,sda=33,scl=32

    to

    dac_config: model=AC101,bck=27,ws=26,do=35,di=25,sda=33,scl=32

    the log output does not change. Even if I erase the parameters of dac_config the log stays the same:
    output_init_i2s:318 AC101 DAC using I2S bck:27, ws:26, do:25, mute:-1:0 (res:-1)

    It seems there is no effect of the variable dac_config.


    Why did I try to change do and di? Because in https://www.makerfabs.com/desfile/fi...cification.pdf on Page 5:
    I2S_SDIN = IO 25
    I2S_SDOUT = IO 35


    Maybe there are two topics in the firmware? 1) Fixed IO parameters and 2) swaped IO parameters for di and do?


    Second strange thing: If I understood it right, the dac is controlled by I2C (I know the data is on I2S). So in my opinion the dac should be listed in the matrix output of i2cdetect if sda and slc are configured right. But if I run i2xdetect from the web UI I get an I2C driver error and I can┤t see any device in the output:

    [0;31mE (25208) i2c: /opt/esp/idf/components/driver/i2c.c:1273 (i2c_master_cmd_begin):i2c driver not installed
    <repeated many times>
    [0;32mI (26638) messaging: i2cdetect

    0 1 2 3 4 5 6 7 8 9 a b c d e f
    00: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    70: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    Last edited by jofland; 2021-06-20 at 11:45.

  10. #920
    Senior Member
    Join Date
    May 2008
    Location
    Canada
    Posts
    7,298
    Quote Originally Posted by jofland View Post
    Yes, in Post #916 I described what I did.

    I downloaded: https://github.com/sle118/squeezelit...S-16-1.689.zip

    Then updated with the web ui the same version again.


    The strange thing is, if I change the dac_config from

    dac_config: model=AC101,bck=27,ws=26,do=25,di=35,sda=33,scl=32

    to

    dac_config: model=AC101,bck=27,ws=26,do=35,di=25,sda=33,scl=32

    the log output does not change. Even if I erase the parameters of dac_config the log stays the same:
    output_init_i2s:318 AC101 DAC using I2S bck:27, ws:26, do:25, mute:-1:0 (res:-1)

    It seems there is no effect of the variable dac_config.


    Why did I try to change do and di? Because in https://www.makerfabs.com/desfile/fi...cification.pdf on Page 5:
    I2S_SDIN = IO 25
    I2S_SDOUT = IO 35


    Maybe there are two topics in the firmware? 1) Fixed IO parameters and 2) swaped IO parameters for di and do?


    Second strange thing: If I understood it right, the dac is controlled by I2C (I know the data is on I2S). So in my opinion the dac should be listed in the matrix output of i2cdetect if sda and slc are configured right. But if I run i2xdetect from the web UI I get an I2C driver error and I can┤t see any device in the output:

    [0;31mE (25208) i2c: /opt/esp/idf/components/driver/i2c.c:1273 (i2c_master_cmd_begin):i2c driver not installed
    <repeated many times>
    [0;32mI (26638) messaging: i2cdetect

    0 1 2 3 4 5 6 7 8 9 a b c d e f
    00: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    70: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    When you use a custom build, the dac_config does not matter. Rightfully, build-in parameters take over.
    Re i2C, yes if you don't see anything, maybe your board is defective. Have you tried with nothing connected on any GPIO?
    LMS 8.2 on Odroid-C4 - SqueezeAMP!, 5xRadio, 5xBoom, 2xDuet, 1xTouch, 1xSB3. Sonos PLAY:3, PLAY:5, Marantz NR1603, Foobar2000, ShairPortW, 2xChromecast Audio, Chromecast v1 and v2, Squeezelite on Pi, Yamaha WX-010, AppleTV 4, Airport Express, GGMM E5, RivaArena 1 & 3

Posting Permissions

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