Cache priority: tracks or MB?

Plex Labs
1

Hello guys I have a question about how Plexamp sets the cache priority:

Let’s say I have WiFi caching set to 40 tracks and the cache size to 512 MB. What would happen if I play some albums with long duration but a low number of tracks? For example:

  1. Pink Floyd - “A Saucerful of Secrets”,
  2. Pink Floyd - “Atom Heart Mother”
    and after this
  3. Pink Floyd - “Animals”

These three albums contain just 17 tracks but the (estimated) total play time is around 135 minutes (and I think all the FLAC files together are bigger than 512 MB in total).

Does PlexAmp now remove the oldest played songs until the cache memory is smaller than 512 MB?
Or does it exceed the memory limit until it reaches 40 tracks and the user has to wait until the the app pushes the long Pink Floyd song from the edge of the cache into the digital abyss? :wink:

2

It removes the least recently accessed tracks, with no accounting for individual size of each track beyond keeping track of total size.

3

OK thank you. So that means if the the cache is full and it plays another song it just pushes this one out of the queue (Newest in → latest out)?

In this case if you use a higher pre cache value I guess it makes sense to raise the cache as well to prevent the app from removing played songs too quickly…

Thank you elan for your help! :slight_smile: BTW: I really like this pre-caching feature. It is fast and unlike other apps it makes the streaming much more stable if you are temporarily a area with no WiFi or bad cellular connection. :musical_note: :headphones:

4

Newest in ⇢ least recently played out.

Glad you’re enjoying it. I’ve been wanting to make it more visible in the play queue at some point so you know how many minutes have been pre-cached :sweat_smile:

2 Likes
5

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.