Smaller increments for selecting (rolling) cache storage sizes or a slider to be able to set the exact desired size.
Problem solved:
The jump between 64Gb and 128Gb is rather large. I have 128Gb internal storage and some is obviously taken up by other apps. Would like to be able to allow 100Gb for rolling offline cache.
Brought benefits:
More cache space, without over shooting size of storage
It maybe more practical to simply allow custom cache sizes to be entered via text entry rather than redesigning the UI entirely. In fact, that may be the best solution, as sliders do make it difficult to select a precise value.
An alternative would be to allow the user to set a total cache allowance for the app, with the option to use the remaining allowed space for rolling cache. Just let Symfonium fill up all the allowed space and if it’s full, and the user adds something to the permanent cache, make space by clearing some of the rolling cache.
issues:
Symfonium has no way to control / make sure the allowed space is actually available and not used by other apps, this may be the reason why the setting is presented as it currently is; let the user select a portion of space for rolling cache, and permanent cache is determined by the space currently available on the SD card at the time. Maybe another way to think about it would be have Symfonium preserve a set amount of space on the SD card. That way, if the user preserves 10GB, other apps can use that space freely and Symfomium would remove rolling cache to maintain that space as it is used up.
Sorry, I don’t mean to keep bumping this thread… just adding more info as I think about it more / refine the use-case I’m actually desiring with the request. (The primary player app on a dedicated music player device that automatically caches my library for offline playback as I stream it online so when I am offline, I have the music actually been listening to available without having to manage / think about it)
I think this may also extend to caching songs in the playback cache. With the way I use the app (playing albums rather than playlists), it doesn’t make much sense to me to select a playback cache size as well as the number of tracks to cache. If I have 256MB selected and the entire album fits into that space, I think it should load the entire album from the get go rather than just up to 9 tracks. This way one could just hit play and walk out of wifi range and keep listening to the entire album without interruption or needing to remember to manually add the album to the rolling cache.
A limit on the number of tracks does make more sense for those who listen to playlists… But even then, it could just fill the cache as I have described and I don’t think that would cause issues.
Perhaps my feature request should be retitled to something along the lines of a revamping of how the cache settings are presented
that’s fair enough. I obviously don’t know the inner workings. Would you consider allowing an arbitrary number of cached songs? If I can increase that number to 12 or 15 it would allow probably 95% of albums to be cached up front
Just installed the beta. Thanks for making those changes. I noticed that the max value for the rolling cache is 512gb, is that because I have a 512gb SD card selected as the storage device or is that a hard coded limit?
You’ll def be getting a 5 star review as soon as I have a chance to do so. Thanks again!
