by cmx » Thu Dec 24, 2009 11:46 am
Could there be node selection for Playlists as there is for phone, mp3, or main library itself?
I use playlists to build the selections for several players and phones. It would be very handy to be able to navigate the playlist in the same manner we navigate everything else in MM.
It is very easy to add things to the playlists...but incredibly tedious to find or remove specific tracks, albums, or artists.
It would follow logically and intuitivly that the Playlist should have the same "node" and "tree" navigation capability. Additions and deletions could be accomplished easily.
We don't really follow the original idea of simply syncing all music between the desktop and a single portable device...and then making playlists that can be ported to either device. We have a huge library that could not be contained on a single portable device AND many different portable devices being managed from a single MM DB. Off the top I guess it means creating yet another db file....but isn't that what computers are good for?
If anyone has a simple strategy for managing multiple playlist content or managing library subset/multiple device syncs, any ideas would be appreciated.
Possibly there needs to be a NEW programming object....such as "Saved Sync" or "<User's> Sync" or "Custom Library" or "Mobile Library".....a "wing"....that represents a specific DB for an individual device...
Thanks for any help on this.
Could there be node selection for Playlists as there is for phone, mp3, or main library itself?
I use playlists to build the selections for several players and phones. It would be very handy to be able to navigate the playlist in the same manner we navigate everything else in MM.
It is very easy to add things to the playlists...but incredibly tedious to find or remove specific tracks, albums, or artists.
It would follow logically and intuitivly that the Playlist should have the same "node" and "tree" navigation capability. Additions and deletions could be accomplished easily.
We don't really follow the original idea of simply syncing all music between the desktop and a single portable device...and then making playlists that can be ported to either device. We have a huge library that could not be contained on a single portable device AND many different portable devices being managed from a single MM DB. Off the top I guess it means creating yet another db file....but isn't that what computers are good for?
If anyone has a simple strategy for managing multiple playlist content or managing library subset/multiple device syncs, any ideas would be appreciated.
Possibly there needs to be a NEW programming object....such as "Saved Sync" or "<User's> Sync" or "Custom Library" or "Mobile Library".....a "wing"....that represents a specific DB for an individual device...
Thanks for any help on this.