Home of the Squeezebox™ & Transporter® network music players.
Page 32 of 32 FirstFirst ... 22303132
Results 311 to 316 of 316
  1. #311
    Senior Member
    Join Date
    Dec 2009
    Location
    Quebec City, Canada
    Posts
    167
    Quote Originally Posted by chill View Post
    Yes, that's right of course, I was complaining about how slow it was

    Of course, that lengthy wait can't all be blamed on the SqueezeAMP. Even after Squeezelite starts running, LMS has to detect it and start streaming to it, and then my DAC has to lock on to the S/PDIF signal on the Toslink cable. My timing stopped the moment I heard output from the speakers.

    Admittedly, this 'chain' was working moments earlier when I first flipped the switch to off, but nevertheless, I was genuinely surprised how quickly everything came back when I turned it on again.
    There's a new build of you are willing to try it.

    The most important change is a decoupling of configuration values and the NVS (non volatile storage) throughout all the subsystems. Using the NVS all over the place resulted in competing for flash resources. Going forward, configuration values will be stored in PSRAM using the cJSON library, which is pretty much an efficient linked list implementation. I'm going to spare all the technical details and just say that the system should run more smoothly. For example, hitting the HTTP server during playback shouldn't result in stuttering. OTA, at least in theory, should be more responsive.

    I tried some benchmark of boot to playback, and I think some milliseconds might have been shaved too (1500ms or so) compared to your non scientific measurements.

    Give it a try if you feel like it, but be aware that a full boring TTL recovery flash is required. We're nearing the end of that cycle; as we approach the reception of the first boards from PCB way, recovery mechanisms (including WiFi profile management) will need to be locked down.
    LMS 7.9 - 1xRadio, 1xBoom, 5xDuet,3xTouch, 1 SB2. Sony PlayStation, Emby, Chromecast v1 and v2 and...
    SqueezeAmp!

  2. #312
    Senior Member chill's Avatar
    Join Date
    Mar 2007
    Posts
    1,335
    I've just loaded v0.3.173 - the web interface does seem a little snappier. I used the TTL adapter to load the new recovery partition, then updated the squeezelite partition OTA. It all went very smoothly. The only glitch I noticed was that after the first boot into the recovery partition the list of available firmware was empty and the 'Check for updates' button didn't populate the list. I hit the Reboot button and it came back with a populated list.

    My completely unscientific boot speed testing is not reliable - after my earlier post I found that it could take anywhere between 7.5 and 9.5 seconds for music to start playing from my speakers. Too many variables I think - boot, connect to wifi, let LMS find the player and start streaming, let DAC lock onto Toslink signal. But I've just done a single test with the latest version, and it measured 7 seconds dead. I never saw one that quick previously.

  3. #313
    Senior Member
    Join Date
    Dec 2009
    Location
    Quebec City, Canada
    Posts
    167
    Quote Originally Posted by chill View Post
    I've just loaded v0.3.173 - the web interface does seem a little snappier. I used the TTL adapter to load the new recovery partition, then updated the squeezelite partition OTA. It all went very smoothly. The only glitch I noticed was that after the first boot into the recovery partition the list of available firmware was empty and the 'Check for updates' button didn't populate the list. I hit the Reboot button and it came back with a populated list.

    My completely unscientific boot speed testing is not reliable - after my earlier post I found that it could take anywhere between 7.5 and 9.5 seconds for music to start playing from my speakers. Too many variables I think - boot, connect to wifi, let LMS find the player and start streaming, let DAC lock onto Toslink signal. But I've just done a single test with the latest version, and it measured 7 seconds dead. I never saw one that quick previously.
    This corroborates my observations. All things being relative, my estimate of 1500 comes from looking at the TTL logs timestamps from "before" and "after". It is worth noting that log time stamps before changes were very close to your observations.

    As for the release list, this is rather strange. Clicking on the button to refresh actually doesn't hit the esp32 at all. The button runs Java code that calls the GitHub API. If this happens again, you could open your browser's developer mode and look for errors in the console.

    I did sneak a small bonus in this release: the credits page now has a toggle button to enable the configuration editor while in squeezelite mode. The config editor now also has a reboot button that doesn't toggle between recovery and squeezelite. All in all, this allows you to change config values and reboot in the same page.

    That version also implemented a feature that will make some names more unique. For example, network host name, squeezebox player name, configuration access point name, etc. These will now have a few characters from the mac address at the end, making it easier to single out units when they get powered up.
    LMS 7.9 - 1xRadio, 1xBoom, 5xDuet,3xTouch, 1 SB2. Sony PlayStation, Emby, Chromecast v1 and v2 and...
    SqueezeAmp!

  4. #314
    Senior Member chill's Avatar
    Join Date
    Mar 2007
    Posts
    1,335
    Quote Originally Posted by sle118 View Post
    As for the release list, this is rather strange. Clicking on the button to refresh actually doesn't hit the esp32 at all. The button runs Java code that calls the GitHub API. If this happens again, you could open your browser's developer mode and look for errors in the console.
    Ah, ok, so rebooting the SqueezeAMP probably did nothing more than refresh the page in my browser. If it happens again I'll see what I can learn from the developer mode.

  5. #315
    Senior Member
    Join Date
    Dec 2009
    Location
    Quebec City, Canada
    Posts
    167
    Quote Originally Posted by chill View Post
    Ah, ok, so rebooting the SqueezeAMP probably did nothing more than refresh the page in my browser. If it happens again I'll see what I can learn from the developer mode.
    One thing that comes to mind is the sensitivity of some browsers to cross site "scripting". In this case, the esp32 sends a page with code that tells the browser to get data from a different site. I had to implement some HTTP headers in the response from the ESP to allow that to happen, but it might not be bullet proof!
    LMS 7.9 - 1xRadio, 1xBoom, 5xDuet,3xTouch, 1 SB2. Sony PlayStation, Emby, Chromecast v1 and v2 and...
    SqueezeAmp!

  6. #316
    Senior Member chill's Avatar
    Join Date
    Mar 2007
    Posts
    1,335
    Quote Originally Posted by sle118 View Post
    One thing that comes to mind is the sensitivity of some browsers to cross site "scripting". In this case, the esp32 sends a page with code that tells the browser to get data from a different site. I had to implement some HTTP headers in the response from the ESP to allow that to happen, but it might not be bullet proof!
    Ok, thanks, something for me to look out for. I'm using Chrome on a Macbook.

Posting Permissions

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