by beg » Sun Oct 03, 2010 7:33 am
Hi,
I understand that, but I have to scroll a lot in the playlist tree (I use > 1000 playlists to organize my music for DJ-ing) and especially for DJ-ing it's important to me that things keep simple. If the album node with >10000 albums is open, the scroll-bar gets tiny (some millimeters) it's difficult to grab for scrolling up and down and scrollspeed is getting slow reacting and jerking. This is maybe not a problem for private use, but if it is a stressfull situation during DJ-ing, or you have to work with this up to 12 hours without a break - this is a no go. These are small reasons, but if you would try to work with that you would understand that it's not possible to be used like that.
Imagine running MM on a mid-sized Laptop in a suboptiomal environment (club, bad light, no place,..) in a live DJ-ing situation where you have to be able to work safe, fast and easy - having 10000 entries in your list you do not need making your scroll bar a small dott and the tree reacting slow so you can't scroll properly through your playlists and you have to do that for >6 hours,...
The thing is - it is simply not necessary and gives no additional information at all to open the whole album list just because the tracks of one album are displayed! For me this should be done within the track viewing/track browser area not changeing the tree list at all! I was looking for 1 CD, I don't kare about the >10000 other albums and would not be able to find anything in this giant list anyway. So what's the point in displaying that.. Maybe ok for small to mid-sized collections, but a no go for big collections which MM is so good for in many other situations.
For another support case (unstable playback) I send the dev-team my MM.db. I'd suggest to work a bit with really huge databases having >150.000 tracks in order to get a feeling for these kind of problems.
Still I want to add that I chose MM because it was able to deal best with this amount of tracks! So this is just to make it even better!
cheers,
Bernhard
Hi,
I understand that, but I have to scroll a lot in the playlist tree (I use > 1000 playlists to organize my music for DJ-ing) and especially for DJ-ing it's important to me that things keep simple. If the album node with >10000 albums is open, the scroll-bar gets tiny (some millimeters) it's difficult to grab for scrolling up and down and scrollspeed is getting slow reacting and jerking. This is maybe not a problem for private use, but if it is a stressfull situation during DJ-ing, or you have to work with this up to 12 hours without a break - this is a no go. These are small reasons, but if you would try to work with that you would understand that it's not possible to be used like that.
Imagine running MM on a mid-sized Laptop in a suboptiomal environment (club, bad light, no place,..) in a live DJ-ing situation where you have to be able to work safe, fast and easy - having 10000 entries in your list you do not need making your scroll bar a small dott and the tree reacting slow so you can't scroll properly through your playlists and you have to do that for >6 hours,...
The thing is - it is simply not necessary and gives no additional information at all to open the whole album list just because the tracks of one album are displayed! For me this should be done within the track viewing/track browser area not changeing the tree list at all! I was looking for 1 CD, I don't kare about the >10000 other albums and would not be able to find anything in this giant list anyway. So what's the point in displaying that.. Maybe ok for small to mid-sized collections, but a no go for big collections which MM is so good for in many other situations.
For another support case (unstable playback) I send the dev-team my MM.db. I'd suggest to work a bit with really huge databases having >150.000 tracks in order to get a feeling for these kind of problems.
Still I want to add that I chose MM because it was able to deal best with this amount of tracks! So this is just to make it even better!
cheers,
Bernhard
