by chrisjj » Mon May 18, 2009 10:24 am
> I think it is quite impossible to have this feature for users with large DBs
> and many playlists nested to a one playlist. Due to this performance restriction...
Why impossible Ludek? I see no restriction - the processing is a background process. As to the performance itself, well, would totalling for Playlists be much slower than for Music? For Music is fast enough - ~1s here for ~10,000 files in ~1,000 folders.
> the consistency issue is quite disputative, when you select a parent playlist in
> Main explorer tree you also don't see tracks of the children playlists
My consistency issue is /internal/ consistency, and the tree does have that (you don't see children when you select a music location). I think equal consistency in device profile would avoid confusion.
And surely at least the misleading No tracks should be removed. Since recently, no-where else does MM show "No tracks" where there are tracks within.
> I think it is quite impossible to have this feature for users with large DBs
> and many playlists nested to a one playlist. Due to this performance restriction...
Why impossible Ludek? I see no restriction - the processing is a background process. As to the performance itself, well, would totalling for Playlists be much slower than for Music? For Music is fast enough - ~1s here for ~10,000 files in ~1,000 folders.
> the consistency issue is quite disputative, when you select a parent playlist in
> Main explorer tree you also don't see tracks of the children playlists
My consistency issue is /internal/ consistency, and the tree does have that (you don't see children when you select a [i]music [/i]location). I think equal consistency in device profile would avoid confusion.
And surely at least the misleading [b]No tracks[/b] should be removed. Since recently, no-where else does MM show "No tracks" where there are tracks within.