Home of the Squeezebox™ & Transporter® network music players.
Page 64 of 70 FirstFirst ... 14546263646566 ... LastLast
Results 631 to 640 of 696
  1. #631
    Senior Member
    Join Date
    May 2008
    Location
    Canada
    Posts
    5,794

    ANNOUNCE: the SqueezeAMP, next generation squeezeboxen amplifier/receiver

    Quote Originally Posted by slimhase View Post
    Thanks, sle118!

    Updated & screenbrightness adjustment works again!
    That was my bad, I changed the brightness and I forgot to tag the update with release ...
    Last edited by philippe_44; 2020-05-29 at 09:49.
    LMS 7.7, 7.8 and 7.9 - 5xRadio, 3xBoom, 4xDuet, 1xTouch, 1 SB2. Sonos PLAY:3, PLAY:5, Marantz NR1603, JBL OnBeat, XBoxOne, XBMC, Foobar2000, ShairPortW, JRiver 21, 2xChromecast Audio, Chromecast v1 and v2, , Pi B3, B2, Pi B+, 2xPi A+, Odroid-C1, Odroid-C2, Cubie2, Yamaha WX-010, AppleTV 4, Airport Express, GGMM E5

  2. #632
    Junior Member
    Join Date
    May 2020
    Posts
    4

    Bluetooth and interlinking

    Question : is it possible to connect to 1 SqueezeAmp via Bluetooth and push the signal to a second one through their WiFi connection?
    In that way, we could have a pair of Bluetooth enabled wireless speakers
    Just Amazing !

  3. #633
    Senior Member
    Join Date
    Feb 2008
    Posts
    299
    Quote Originally Posted by sle118 View Post
    good news! I fixed the i2cset command, which means you can now send an arbitrary number of bytes to the i2c device of your choice.
    So, I returned home and got back to play with the ES9018. This time with bleeding.edge.62-I2S-4MFlash.

    I can confirm that I can now send I2C commands to the DAC and thus make it play 16bit I2S, which it OOTB doesn't.
    Thank you for that.

    However, it only works when I send the command to change the register by I2C from the telnet command line.
    If I introduce a new NVS key "autoexec2" and set it to "i2cset -c 72 -r 1 12" I get an error in the log that says
    Code:
    I (2937) wifi_manager: Wifi Connecting...
    W (2947) console: Processing autoexec commands while wifi_manager active.  Wifi related commands will be ignored.
    I (2947) console: autoexec is set to perform auto-process
    I (2957) console: Running command autoexec1 = squeezelite -b 500:2000 -d all=info -n "Scarlet" -o I2S
    I (2957) console: Running command autoexec2 = i2cset  -c 72 -r 1 12
    I (2957) squeezelite_cmd: Calling squeezelite
    I (2957) system_api: Base MAC address is not set, read default base MAC address from BLK0 of EFUSE
    E (2957) i2c: /var/lib/jenkins/workspace/v4.0/components/driver/i2c.c:1273 (i2c_master_cmd_begin):i2c driver not installed
    E (2957) messaging: i2c Read failed
    [00:43:18.839549] stream_init:370 init stream
    W (2957) config: Value not found for key autoexec3
    Can you help, please?

    BTW: the output of i2cdetect does not fit into that pop up bubble on the system page of the web GUI
    Last edited by ElFishi; 2020-06-02 at 12:58.

  4. #634
    Senior Member
    Join Date
    Dec 2009
    Location
    Quebec City, Canada
    Posts
    276
    Quote Originally Posted by ElFishi View Post
    Can you help, please?
    At least we have a confirmation that your DAC works, which is good news. As for your issue, are you certain that there's a proper i2c configuration in NVS? Error "i2c driver not installed" seems to indicate that i2c wasn't initialized, which isn't supposed to be the case in our init sequence as i2c is one of the core service being brought up during boot before Squeezelite starts. If you have an i2c configuration in nvs (and you are 100% certain it "works"), then you could try calling i2cconfig as part of autoexec2 and then send commands to the dac on autoexec3.

    Quote Originally Posted by ElFishi View Post
    BTW: the output of i2cdetect does not fit into that pop up bubble on the system page of the web GUI
    I know... the popup is a generic popup message which I "brute force" repurposed for commands output. This will be addressed at some point when everyone has migrated to the cmake branch (a.k.a bleeding edge). The syslog tab offers a better experience for large text.
    LMS 7.9 - 1xRadio, 1xBoom, 5xDuet,3xTouch, 1 SB2. Sony PlayStation, Emby, Chromecast v1 and v2 and...
    SqueezeAmp!
    Contributing to Folding@Home : https://stats.foldingathome.org/donor/squeezelite-esp32

  5. #635
    Senior Member
    Join Date
    Dec 2009
    Location
    Quebec City, Canada
    Posts
    276
    Quote Originally Posted by Gin_Fiz View Post
    Question : is it possible to connect to 1 SqueezeAmp via Bluetooth and push the signal to a second one through their WiFi connection?
    In that way, we could have a pair of Bluetooth enabled wireless speakers
    Just Amazing !
    Not quite, but it's been one of the things that I discussed with Philippe in the past. We think the best approach would be to implement a nano slim proto server on a node that would be configured as master, and all other amps/players (including the Logitech offerings) would then simply appear to be an extra zone that would have their playback synchronized. The biggest issue currently (aside from the spare time available to implement this type of feature) is that we're slowly approaching the limits of the firmware size that can fit on a 4Mb Flash. Squeezelite is ~2,480K (when only warning logs are kept) and the recovery 1,260K. The partition has room for a 2,750K squeezelite binary.
    LMS 7.9 - 1xRadio, 1xBoom, 5xDuet,3xTouch, 1 SB2. Sony PlayStation, Emby, Chromecast v1 and v2 and...
    SqueezeAmp!
    Contributing to Folding@Home : https://stats.foldingathome.org/donor/squeezelite-esp32

  6. #636
    Senior Member
    Join Date
    Feb 2008
    Posts
    299
    Quote Originally Posted by sle118 View Post
    ... are you certain that there's a proper i2c configuration in NVS? Error "i2c driver not installed" seems to indicate that i2c wasn't initialized, which isn't supposed to be the case in our init sequence as i2c is one of the core service being brought up during boot before Squeezelite starts. If you have an i2c configuration in nvs (and you are 100% certain it "works"), then you could try calling i2cconfig as part of autoexec2 and then send commands to the dac on autoexec3.
    Below you find more of my telnet log, including the I2C config. I have a display attached and it works. Can I do more?

    Code:
    I (1727) esp_app_main: Setting up config subsystem.
    I (1767) esp_app_main: Registering default values
    I (1767) system_api: Base MAC address is not set, read default base MAC address from BLK0 of EFUSE
    W (1767) config: Waiting for config commit ...
    I (2767) config: configuration has some uncommitted entries
    I (2767) config: Committing configuration to nvs. Locking config object.
    I (2767) config: Config committed!
    I (2767) esp_app_main: Configuring services
    I (2767) config: Done Committing configuration to nvs.
    I (2767) services: Configuring I2C sda:14 scl:13 port:1 speed:400000
    I (2767) services: Configuring SPI data:-1 clk:-1 host:1 dc:-1
    W (2767) services: no SPI configured
    I (2767) led: Configuring LEDs green:19 (active:0), red:18 (active:0)
    I (2767) battery: No battery
    I (2767) monitor: Initializing monitoring
    I (2767) monitor: Heap internal:238896 (min:223496) external:4078804 (min:4078804)
    I (2767) esp_app_main: Initializing display
    I (2767) display: Trying to configure display with I2C,width=128,height=64,address=60,driver=SSD1306
    I (2767) SSD1306: SSD1306 driver
    I (2807) display: Display is I2C on port 60
    I (2817) gds: Adding line 1 at -3 (height:14)
    I (2817) gds: Adding line 2 at 8 (height:24)
    I (2817) esp_app_main: Checking if certificates need to be updated
    I (2817) esp_app_main: About to check if certificates need to be updated in flash
    I (2817) esp_app_main: Running partition [ota_0] type 0 subtype 16 (offset 0x00150000)
    I (2817) esp_app_main: Running version: bleeding.edge.62-I2S-4MFlash
    I (2817) esp_app_main: Certificate version: bleeding.edge.62-I2S-4MFlash
    I (2817) esp_app_main: Checking for update url
    W (2817) config: Value not found for key fwurl
    I (2817) IR: Starting Infrared Receiver on gpio 21
    I (2817) buttons: starting button tasks

    as per your suggestion I introduced
    autoexec2 as "i2cconfig -p 1 -f 400000 -d 14 -c 13" and
    autoexec3 as "i2cset -c 72 -r 1 12"
    Now I get no more error
    Code:
    I (2957) wifi_manager: Wifi Connecting...
    W (2967) console: Processing autoexec commands while wifi_manager active.  Wifi related commands will be ignored.
    I (2977) console: autoexec is set to perform auto-process
    I (2977) console: Running command autoexec1 = squeezelite -b 500:2000 -d all=info -n "Scarlet" -o I2S
    I (2977) console: Running command autoexec2 = i2cconfig -p 1 -f 400000 -d 14 -c 13
    I (2977) squeezelite_cmd: Calling squeezelite
    I (2977) system_api: Base MAC address is not set, read default base MAC address from BLK0 of EFUSE
    I (2977) messaging: Uninstall i2c driver from port 1 if needed
    [02:33:10.464973] stream_init:370 init stream
    I (2977) messaging: Initializing driver with config scl=13 sda=14 speed=400000 port=1
    I (2977) messaging: Initializing i2c driver configuration.
       mode = I2C_MODE_MASTER,
    [02:33:10.465917] sb_controls_init:299 initializing audio (buttons/rotary/ir) controls (raw:0)
       scl_pullup_en = GPIO_PULLUP_ENABLE,
       i2c port = 1,
       sda_io_num = 14,
       sda_pullup_en = GPIO_PULLUP_ENABLE,
       scl_io_num = 13,
       scl_pullup_en = GPIO_PULLUP_ENABLE,
       master.clk_speed = 400000
    I (2977) system_api: Base MAC address is not set, read default base MAC address from BLK0 of EFUSE
    [02:33:10.466437] sendSETD:384 sending dimension 128x64
    I (2977) messaging: Initalize success.
    I (2977) messaging: Starting the i2c driver.
    I (2977) messaging: i2c driver successfully started.
    I (2977) messaging: Storing i2c parameters.
    I (2977) services: Updating i2c configuration to scl=13 sda=14 speed=400000 port=1
    [02:33:10.467634] output_init_embedded:70 init device: I2S
    [02:33:10.468770] output_init_common:427 supported rates: 192000 176400 96000 88200 48000 44100 32000 24000 22050 16000 12000 11025 8000
    [02:33:10.469182] output_init_embedded:86 init I2S/SPDIF
    I (2977) config: Setting changed flag config [i2c_config]
    I (2977) config: Updating config [i2c_config]
    I (2977) console: Running command autoexec3 = i2cset -c 72 -r 1 12
    I (2977) messaging: i2c Write OK
    W (2977) config: Value not found for key autoexec4

  7. #637
    Senior Member
    Join Date
    May 2008
    Location
    Canada
    Posts
    5,794
    Next batch of 50 is on its way, so cross fingers. That will probably be the last one as it will be too much load for me to do more
    Last edited by philippe_44; 2020-06-03 at 23:21.
    LMS 7.7, 7.8 and 7.9 - 5xRadio, 3xBoom, 4xDuet, 1xTouch, 1 SB2. Sonos PLAY:3, PLAY:5, Marantz NR1603, JBL OnBeat, XBoxOne, XBMC, Foobar2000, ShairPortW, JRiver 21, 2xChromecast Audio, Chromecast v1 and v2, , Pi B3, B2, Pi B+, 2xPi A+, Odroid-C1, Odroid-C2, Cubie2, Yamaha WX-010, AppleTV 4, Airport Express, GGMM E5

  8. #638
    Junior Member
    Join Date
    May 2020
    Posts
    4

    Yeah !

    Quote Originally Posted by philippe_44 View Post
    next batch of 50 is on its way, so cross fingers. That will probably be the last one as it will be too much load for me to do more

  9. #639
    Quote Originally Posted by philippe_44 View Post
    Next batch of 50 is on its way, so cross fingers. That will probably be the last one as it will be too much load for me to do more


    Thanks very much for doing all this.

  10. #640
    Quote Originally Posted by ElFishi View Post
    I'm no expert with DACs, but would it be a meaningful idea to extract a Master Clock from the ESP32 to drive an I2S DAC?
    Did you ever get an answer to this question?

    Mike

Posting Permissions

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