by mcow » Mon Feb 25, 2013 2:30 pm
Lowlander wrote:captainmcl wrote:But if the tracks were grouped by album, or if the interface showed the albums with count of tracks for deletion
Except it wouldn't tell the user which tracks are being deleted. The user should always be able to know this.
First of all, the use case of having sync'd all or some tracks from a particular album, and then removing a subset of those tracks, is relatively rare. Selection of tracks for syncing is by album (or by some other grouping: playlist, artist, rating); I don't see a way to select for sync by individual tracks, altho there may be one that's not part of my configuration.
My proposal was primarily about the sync-by-album case (which I select from Album nodes under Album Artist nodes); I wasn't considering other node types. Take playlists: If the playlist contents change, or if the playlist is removed from the synclist, then various individual tracks probably will be removed. The way to handle this is to use a playlist icon rather than an album icon, with some indicative text: "6 tracks of 15 in this playlist". Similarly, tracks that were sync'd onto the device via Artist or Rating could be presented in the list under Artist or Rating groupings.
Yes, there is more complexity to this: these different types of nodes may overlap with others. Playlists may contain tracks that are redundant with other playlists and with albums; but if a track that's part of a removed album or playlist isn't being removed because it's in use elsewhere, that doesn't really affect this issue because those tracks are not being removed, and so they don't show up in the list anyway.
Second of all, in the case that I'm trying to improve, where there are a large number of tracks being removed, the existing solution does not address your concern any better: a very long list of tracks, sorted alphabetically, does not give the user visibility into which tracks are being removed.
Third, my idea could be improved upon by making the individual tracks visible on demand, by tapping the album or playlist entry.
Finally: suppose some tracks do get accidentally sync'd off the device? It's not the end of the world. When I sync, I do want to know that tracks are being removed and have a general idea of which ones, in case something catastrophic has happened in the sync-list. But I don't need every track listed out, because I'm always syncing entire albums off, and usually six or ten albums at a time. The existing list does not help me.
[quote="Lowlander"][quote="captainmcl"]But if the tracks were grouped by album, or if the interface showed the albums with count of tracks for deletion[/quote]Except it wouldn't tell the user which tracks are being deleted. The user should always be able to know this.[/quote]
First of all, the use case of having sync'd all or some tracks from a particular album, and then removing a subset of those tracks, is relatively rare. Selection of tracks for syncing is by album (or by some other grouping: playlist, artist, rating); I don't see a way to select for sync by individual tracks, altho there may be one that's not part of my configuration.
My proposal was primarily about the sync-by-album case (which I select from Album nodes under Album Artist nodes); I wasn't considering other node types. Take playlists: If the playlist contents change, or if the playlist is removed from the synclist, then various individual tracks probably will be removed. The way to handle this is to use a playlist icon rather than an album icon, with some indicative text: "6 tracks of 15 in this playlist". Similarly, tracks that were sync'd onto the device via Artist or Rating could be presented in the list under Artist or Rating groupings.
Yes, there is more complexity to this: these different types of nodes may overlap with others. Playlists may contain tracks that are redundant with other playlists and with albums; but if a track that's part of a removed album or playlist isn't being removed because it's in use elsewhere, that doesn't really affect this issue because those tracks are not being removed, and so they don't show up in the list anyway.
Second of all, in the case that I'm trying to improve, where there are a large number of tracks being removed, the existing solution does not address your concern any better: a very long list of tracks, sorted alphabetically, does not give the user visibility into which tracks are being removed.
Third, my idea could be improved upon by making the individual tracks visible on demand, by tapping the album or playlist entry.
Finally: suppose some tracks do get accidentally sync'd off the device? It's not the end of the world. When I sync, I do want to know that tracks are being removed and have a general idea of which ones, in case something catastrophic has happened in the sync-list. But I don't need every track listed out, because I'm always syncing entire albums off, and usually six or ten albums at a time. The existing list does not help me.