I understand. But capping the bandwidth forces Plexamp to spread the load more evenly over time instead of trying to trying to grab it all in one bite. So instead of it potentially saturating a 150 Mbps Wi-Fi connection for a few seconds it can consume an average of 50 Mbps over several seconds.
Also, the caching of a new track takes beginning at the start of the current track. What you’ll see when you watch the bandwidth graph in the dashboard is that when Plexamp moves from one track to the next, it will pull down the next track; after that is complete, the graph basically shows no activity (except that used to show the graph itself).
This also impacts the storage I/O as well since it’s not trying to write a bunch of data all at once.
All of this is in an effort to mitigate some of the bursty-ness of the transaction. But ultimately you likely do need faster storage. Hopefully the NVMe drive will address this.
Probably, in the Feature Suggestions section of the forums. I’d recommend doing a search first to ensure that someone else hasn’t already suggested it.
I don’t know, I’ve not experienced this myself. But our setups are completely different. I have human-level hearing and so don’t bother with super-high bitrate music. So I’m likely not stressing my Pis the way you might be.
I’d start another thread and provide a detailed description and provide Plexamp logs. If you try to lump another problem into this thread it’s likely to get lost.
