by sdaughtry » Fri Nov 28, 2025 4:33 am
[note: my previous reply was mangled by Notepad; below is the correct reply. I couldn't edit the previous post to correct the mistake]
Hi Peke,
Thank you for your reply. Here are my replies to your queries:
1. I've not disabled the Column Filter feature, as I won't use a MP3 collection manager that lacks that functionality (e.g. Helium). For me, it is the most logical means of drilling down into a collection (especially one as large as mine).
2. No other MM fragments are floating in Task Manager
To better define my "speed" question - when the primary grid control which lists the individual MP3 songs is forced to redraw the entire collection, after the first database read it then picks up steam to then grab batches of 100,000 records to populate the grid. After the grid is fully populated, the three filter grids (Genre, Artist, Album is how mine is configured) are then displayed from left to right above the list of MP3 files. The bottom grid control takes about 6 seconds to display, then the top three grid controls then appear from left to right; first the genre, about .5 second wait, then the artist, another .5 second wait, then the album grid.
An open source MP3 collection manager app (written in VB.NET) that I also use is configured identically (i.e. the classic iTunes layout). Accessing the same files off the same drive, its grid control population time is near instantaneous. I have a handful of identical auto-playlists configured in both applications - in the open source app, when I switch between playlists the grids load within .5 seconds - even when I load the entire list of files (446,388 files). It is incredibly fast - I have no idea how their developers achieved this feat, but it spoiled me as I often toggle between artists/playlists and am accustomed to its near instantaneous response.
In MM, when I switch between specific simple filter conditions (typically possessing around 8k records apiece), it is quick to rebuild the grids. However, when I switch back to the "everything" playlist (446,388 files) it takes about 8 seconds before its read for use. This is what my initial question pertained to regarding speed.
Please do not view my query as demeaning towards MM - I bought my Gold license a LONG time ago and have enjoyed the many changes to it over the years. I am undoubtedly an outlier in regard to collection size.. my mother always stated it never hurts to ask a question, which is why I created this thread <lol>.
Warm Regards,
Scott
[note: my previous reply was mangled by Notepad; below is the correct reply. I couldn't edit the previous post to correct the mistake]
Hi Peke,
Thank you for your reply. Here are my replies to your queries:
1. I've not disabled the Column Filter feature, as I won't use a MP3 collection manager that lacks that functionality (e.g. Helium). For me, it is the most logical means of drilling down into a collection (especially one as large as mine).
2. No other MM fragments are floating in Task Manager
To better define my "speed" question - when the primary grid control which lists the individual MP3 songs is forced to redraw the entire collection, after the first database read it then picks up steam to then grab batches of 100,000 records to populate the grid. After the grid is fully populated, the three filter grids (Genre, Artist, Album is how mine is configured) are then displayed from left to right above the list of MP3 files. The bottom grid control takes about 6 seconds to display, then the top three grid controls then appear from left to right; first the genre, about .5 second wait, then the artist, another .5 second wait, then the album grid.
An open source MP3 collection manager app (written in VB.NET) that I also use is configured identically (i.e. the classic iTunes layout). Accessing the same files off the same drive, its grid control population time is near instantaneous. I have a handful of identical auto-playlists configured in both applications - in the open source app, when I switch between playlists the grids load within .5 seconds - even when I load the entire list of files (446,388 files). It is incredibly fast - I have no idea how their developers achieved this feat, but it spoiled me as I often toggle between artists/playlists and am accustomed to its near instantaneous response.
In MM, when I switch between specific simple filter conditions (typically possessing around 8k records apiece), it is quick to rebuild the grids. However, when I switch back to the "everything" playlist (446,388 files) it takes about 8 seconds before its read for use. This is what my initial question pertained to regarding speed.
Please do not view my query as demeaning towards MM - I bought my Gold license a LONG time ago and have enjoyed the many changes to it over the years. I am undoubtedly an outlier in regard to collection size.. my mother always stated it never hurts to ask a question, which is why I created this thread <lol>.
Warm Regards,
Scott