by AnthonyM1229 » Fri Feb 24, 2017 10:37 am
Hello. I've been testing 1829, offered to me as a debug build after I reported an OS validation bug (which is now fixed).
This being my first debug build I've used, I don't know if the behavior I'm about to describe is typical for debug builds, or unique to this one. I'm guessing it'll be the former.
Before I went to bed, I set MM to add 1,148 OGG files to my library via drag and drop from a Windows Explorer window. Estimating that would take maybe an hour or so, and since I had another unrelated operation in a different program to go on overnight, I figured MM would do its thing overnight, and when I got back on my computer in the morning, the files will have finished adding to the library.
Here's some background before I continue. I used to use the File Monitor to watch my current working folders, until I got frustrated by it often missing 1-10 songs or more, out of expected additions of 500+ songs. Although sometimes, I've had issues with far fewer additions. My folder structure is "<music source>/yyyy/mm" (where "yyyy" is year digits and "mm" is month digits), which typically leads to 1,000+ (sometimes several thousand files) in each of those monthly folders. Because I deal with such a large volume of music, and I'm hypersensitive to things being correct, I have a Windows file indexer program with an on-demand setting to check the number of music files I have on my HDD, and a PowerShell script that runs automatically as part of a command line batch I run after I finish tagging (using an external tagging program) a set of music to be migrated to my library. That script too counts the number of music files I have.
When my MediaMonkey library total and program and script numbers don't agree, though, I would get highly irritated, as that'd mean I'd have to manually re-scan the affected folder, which would mean re-scanning hundreds or thousands of files already in my library, just to get the stubborn few that didn't get added correctly.
I hated that "Add/Rescan Tracks to the Library" seems only folder-based, and doesn't permit selecting individual files. That itself is an issue I would love to see addressed, perhaps in MM5?
Anyway, sometimes the File Monitor would have to take 30 minutes to an hour or even occasionally longer, only to miss a few files.
That's another issue, the fact that it would often miss one or a few files. And then rescanning the affected folder via Add/Rescan Tracks to the Library would usually take even longer, because it'd have to rescan the existing tracks too, but usually, all was correct by the end.
A few months ago, however, I discovered that it's possible to add files to the library by dragging and dropping them onto the Entire Library node from Windows Explorer. Yes! That's turned out to be a big help for me, as that lets me add exactly the files I want to add, and I've not seen MM missing any of them after I verify the library total at the end.
However, adding files this way makes the whole MediaMonkey window unresponsive until it's done adding the files. I estimate that it processes about 30-35 files a minute on my HDD (which seems slow--"Add/Rescan Tracks to the Library" can do ~60 a minute, or ~100 when it's scanning already added files), so, 1,000+ files would definitely take time.
When I got back to my computer this morning, I saw that MediaMonkey had stopped overnight with an error reporting window claiming it was frozen! Ugh! I guess that happened since I was running a debug build. Having never seen that window before, I examined its details, playing around with the tabs, but then I wanted to go back to where I could input my contact info, and I either couldn't, or didn't do it correctly, because the error report all of a sudden sent itself. Great.
But then I saw in my process manager, MediaMonkey ramping up CPU and I/O usage once again, as if it were working normally. Hmm... So, I let it do its thing a little while, thinking it may have still been adding my files from last night. Then 5 minutes later, I got the error window again, claiming MM is frozen! Aha! So it looks like there's a debug routine that fires every 5 minutes. That's good and all, but it interferes with long-running drag-and-drop library adding operations.
After having to dismiss that window at least five times (while typing up this message too), my 1,148 OGG files finally finished adding successfully.
Okay, here's a TL;DR:
- It would be awesome if Add/Rescan Tracks to the Library could let us choose individual files to add to the library, instead of just folders. Maybe something to consider for MM5?
- File Monitor, my previous method of adding files to the library, would often miss 1-10 files (and sometimes more) after I've migrated a few hundred, or sometimes over a thousand files to the folder being watched.
- File Monitor is also only about half as fast at indexing as Add/Rescan Tracks to the Library in my experience. Is there any way to speed that up? Maybe for MM5? (I haven't tried MM5 yet, but would like to much later on.)
- Dragging and dropping via Windows Explorer, the exact files I want added onto the Entire Library node, works properly, but is also only about half as fast as Add/Rescan Tracks to the Library.
- Dragging and dropping files in this way makes MediaMonkey totally unresponsive until the files finish adding. Is there any way to keep the window responsive?
- As a result of the above item, dragging and dropping files in this way while running a debug build results in MM thinking it's frozen every 5 minutes, when it isn't. I actually don't know if this is a "bug" per se, but it definitely seems like sub-optimal behavior. Then again, this could be me just having pushed a debug build beyond a typical usage pattern? I don't know. I don't even know if 1829 has been formally released yet as a regular build. Doesn't look like it, judging from the homepage download links.
Hello. I've been testing 1829, offered to me as a debug build after I reported an OS validation bug (which is now fixed).
This being my first debug build I've used, I don't know if the behavior I'm about to describe is typical for debug builds, or unique to this one. I'm guessing it'll be the former.
Before I went to bed, I set MM to add 1,148 OGG files to my library via drag and drop from a Windows Explorer window. Estimating that would take maybe an hour or so, and since I had another unrelated operation in a different program to go on overnight, I figured MM would do its thing overnight, and when I got back on my computer in the morning, the files will have finished adding to the library.
Here's some background before I continue. I used to use the File Monitor to watch my current working folders, until I got frustrated by it often missing 1-10 songs or more, out of expected additions of 500+ songs. Although sometimes, I've had issues with far fewer additions. My folder structure is "<music source>/yyyy/mm" (where "yyyy" is year digits and "mm" is month digits), which typically leads to 1,000+ (sometimes several thousand files) in each of those monthly folders. Because I deal with such a large volume of music, and I'm hypersensitive to things being correct, I have a Windows file indexer program with an on-demand setting to check the number of music files I have on my HDD, and a PowerShell script that runs automatically as part of a command line batch I run after I finish tagging (using an external tagging program) a set of music to be migrated to my library. That script too counts the number of music files I have.
When my MediaMonkey library total and program and script numbers don't agree, though, I would get highly irritated, as that'd mean I'd have to manually re-scan the affected folder, which would mean re-scanning hundreds or thousands of files already in my library, just to get the stubborn few that didn't get added correctly. [b]I hated that "Add/Rescan Tracks to the Library" seems only folder-based, and doesn't permit selecting individual files. That itself is an issue I would love to see addressed, perhaps in MM5?[/b]
Anyway, sometimes the File Monitor would have to take 30 minutes to an hour or even occasionally longer, only to miss a few files. [b]That's another issue, the fact that it would often miss one or a few files.[/b] And then rescanning the affected folder via Add/Rescan Tracks to the Library would usually take even longer, because it'd have to rescan the existing tracks too, but usually, all was correct by the end.
A few months ago, however, I discovered that it's possible to add files to the library by dragging and dropping them onto the Entire Library node from Windows Explorer. Yes! That's turned out to be a big help for me, as that lets me add exactly the files I want to add, and I've not seen MM missing any of them after I verify the library total at the end. [b]However, adding files this way makes the whole MediaMonkey window unresponsive until it's done adding the files. I estimate that it processes about 30-35 files a minute on my HDD (which seems slow--"Add/Rescan Tracks to the Library" can do ~60 a minute, or ~100 when it's scanning already added files), so, 1,000+ files would definitely take time.[/b]
[b]When I got back to my computer this morning, I saw that MediaMonkey had stopped overnight with an error reporting window claiming it was frozen! Ugh! I guess that happened since I was running a debug build. Having never seen that window before, I examined its details, playing around with the tabs, but then I wanted to go back to where I could input my contact info, and I either couldn't, or didn't do it correctly, because the error report all of a sudden sent itself. Great.
But then I saw in my process manager, MediaMonkey ramping up CPU and I/O usage once again, as if it were working normally. Hmm... So, I let it do its thing a little while, thinking it may have still been adding my files from last night. Then 5 minutes later, I got the error window again, claiming MM is frozen! Aha! So it looks like there's a debug routine that fires every 5 minutes. That's good and all, but it interferes with long-running drag-and-drop library adding operations.[/b]
After having to dismiss that window at least five times (while typing up this message too), my 1,148 OGG files finally finished adding successfully.
[b]Okay, here's a TL;DR:[/b]
[list]
[*]It would be awesome if Add/Rescan Tracks to the Library could let us choose individual files to add to the library, instead of just folders. Maybe something to consider for MM5?
[*]File Monitor, my previous method of adding files to the library, would often miss 1-10 files (and sometimes more) after I've migrated a few hundred, or sometimes over a thousand files to the folder being watched.
[*]File Monitor is also only about half as fast at indexing as Add/Rescan Tracks to the Library in my experience. Is there any way to speed that up? Maybe for MM5? (I haven't tried MM5 yet, but would like to much later on.)
[*]Dragging and dropping via Windows Explorer, the exact files I want added onto the Entire Library node, works properly, but is also only about half as fast as Add/Rescan Tracks to the Library.
[*]Dragging and dropping files in this way makes MediaMonkey totally unresponsive until the files finish adding. Is there any way to keep the window responsive?
[*]As a result of the above item, dragging and dropping files in this way while running a debug build results in MM thinking it's frozen every 5 minutes, when it isn't. I actually don't know if this is a "bug" per se, but it definitely seems like sub-optimal behavior. Then again, this could be me just having pushed a debug build beyond a typical usage pattern? I don't know. I don't even know if 1829 has been formally released yet as a regular build. Doesn't look like it, judging from the homepage download links.[/list]