Feature description:
Instead of removing based on first cached, an option to remove based on last played. So if a song cached on May 4th has been played 7 times and was last played today, and a song from July 4th was played only 1 time that on that orginal day, the July 4th song will be removed from cache when a new song gets added, instead of the May 4th song.
Problem solved:
Currently rolling cache removes the oldest cached song. This can be less then ideal as sometimes it will cause frequently played tracks to be removed in replacement to possibly those that might get played once.
Brought benefits:
As mentioned, it would prioritize removing cached songs that don’t get played as much. This gives the bonus of songs you cached and wanna play more often staying in rolling cache, while older songs you might’ve just shuffled randomly eventually get trimmed out.
This benefits a lot if you set a decent size rolling cache and mainly focus on a few albums or somg for a few months at a time, as you can keep them cached while those not getting as many plays anymore get trimmed out for newer caching.
Other application solutions:
Additional description and context:
I have a 10gb rolling cache I use to keep all my music that i currently listen to. I tend to go through obsessions with an album for a few months, as well as keep some in rotation for years. it can be a bit annoying to have an album i listen to get trimmed out either partially or fully (my navidrone server isnt accessible outside the home, so im just kinda outta luck in these cases)
Screenshots / Mockup: