I’ve said in many threads that we intent to raise the limit in the future.
If I can, I’d like to get clarification on something, regarding the redundant downloading (or overlapping) of tracks. As a hypothetical example, say I have a playlist with 10 tracks on it, each track coming from a different album. I download the 10 albums that each contain one of the tracks, but I DO NOT download the playlist itself. Do I assume correctly (based on what I think I understand about the way downloads are handled on plexamp) that when I now choose to play the playlist, that the tracks will still be streamed, even though I’ve downloaded them as a part of the albums?
No. That feature looks in any download for each particular track.
In that case I have difficulty understanding the duplicates if I download both the playlist and the albums that contain the tracks that are on the playlist. Wouldn’t the downloader look in the same place before downloading a duplicate?
It’s more complicated than that.
I guess your marketing team didn’t get that internal memo
I’m not sure what you’re looking for here. The offline system is designed in a particular way, for specific reasons. I’m happy to clarify user-facing functionality, but the design itself of the downloader isn’t of particular relevance to an end-user.
You are quite right, because I don’t work with computers or coding, I wouldn’t understand the language. I am, however, as an end user, particularly interested in knowing why the app would EVER download the same track twice
It’s really straightforward: storage efficiency wasn’t a priority when we were designing the offline system. We wanted something which was simple, reliable, and fast.
Why didn’t we design for this particular storage efficiency? Because:
- The majority of scenarios don’t have much, if any duplication.
- Where there is overlap, the storage wasted is almost always too small to be an issue.
There you have it.
@elan I think you may be discovering that more people create multiple playlists that include overlapping tracks than you might have expected when first designing the offline features. I understand your opinion about the small amount of storage required not being an issue, but obviously, to some of us it is. And it can’t possibly be FASTER to download a track an additional time than to verify whether a track has already been downloaded.
So… Is there any plan, going forward, to reconfigure things to prevent duplicate downloads?
1 Like
not specifically, no.
Good to know
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
