You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Spotube currently lacks persistent caching for downloaded music.
This leads to many re-download, wasting bandwidth, hindering offline use, and causing playback delays.
This makes offline listening unreliable and inconvenient.
Suggested solution
I propose a comprehensive caching system to address these issues. This system should include the following key features:
1. Configurable Cache Size: Users should be able to define a maximum cache size (e.g., 1GB, adjustable in settings). This allows control over storage usage and caters to different user needs. The default size could be a reasonable starting point, like 500MB, but should be easily changeable.
And a clear button in the settings would allow users to manually clear the cache if they need to free up space or reset their offline library.
2. Intelligent Cache Management: When a song is played, it should be automatically saved to the cache.
The system should prioritize caching songs played more frequently. When the cache reaches its configured limit, the oldest and least frequently played songs should be automatically removed to make space for newer tracks.
Possiblity to pin a track to not be automatically deleted would be nice.
3. Dedicated Offline Browsing: A dedicated menu or section within Spotube should allow users to browse and play only the music currently stored in the cache. This provides a clear and convenient way to access offline content.
4. Manual Download button: A dedicated button or option should be available to manually download a song or album directly to the cache without need to play it.
This enhanced caching system would significantly improve Spotube's offline capabilities, save bandwidth, provide a much smoother user experience.
Thank you for considering this request.
Useful resources
No response
Additional information
No response
Self grab
I'm ready to work on this issue!
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Pain
Spotube currently lacks persistent caching for downloaded music.
This leads to many re-download, wasting bandwidth, hindering offline use, and causing playback delays.
This makes offline listening unreliable and inconvenient.
Suggested solution
I propose a comprehensive caching system to address these issues. This system should include the following key features:
1. Configurable Cache Size: Users should be able to define a maximum cache size (e.g., 1GB, adjustable in settings). This allows control over storage usage and caters to different user needs. The default size could be a reasonable starting point, like 500MB, but should be easily changeable.
And a clear button in the settings would allow users to manually clear the cache if they need to free up space or reset their offline library.
2. Intelligent Cache Management: When a song is played, it should be automatically saved to the cache.
The system should prioritize caching songs played more frequently. When the cache reaches its configured limit, the oldest and least frequently played songs should be automatically removed to make space for newer tracks.
Possiblity to pin a track to not be automatically deleted would be nice.
3. Dedicated Offline Browsing: A dedicated menu or section within Spotube should allow users to browse and play only the music currently stored in the cache. This provides a clear and convenient way to access offline content.
4. Manual Download button: A dedicated button or option should be available to manually download a song or album directly to the cache without need to play it.
This enhanced caching system would significantly improve Spotube's offline capabilities, save bandwidth, provide a much smoother user experience.
Thank you for considering this request.
Useful resources
No response
Additional information
No response
Self grab
The text was updated successfully, but these errors were encountered: