[X] Mp3tag unnecessary wakes up inactive drives


#1

I have Mp3tag pinned down to Taskbar of Windows 7. Under its icon I have shortcuts to playlists- those playlists save me a lot of time, because with as little as only two clicks and minimal pointer movement I can load up all my files to Mp3tag

And here is the bug: even thought my playlists have only locations listed on drive M, Mp3tag deems it necessary to start up my drive X, which is turned off most of the time [to save energy and avoid noise], when I click those shortcuts

Although it may be not a Mp3tag bug but just a regular Windows behavior, as the same happens when I run Corel DRAW from pinned down shortcut- with no settings of any kind stored on or leading to drive X, that drive X starts to spins. But then again- maybe it is the same kind of bug that exists in both Mp3tag and Corel DRAW; or a default Windows behavior that could be removed from Mp3tag [and thus should be into a request instead of labeling it as a bug]?


#2

You could use a process monitor first (e.g. by sysinternals) to see which processes access your sleepy drive.

BTW: didn't you ask in this thread
/t/19546/1
for a solution to wake up a drive? To me that looks like the exact opposite of this "bug" report.


#3

I doubt it. Because it is probably like that: an useless request is send from either directly Mp3tag or from some Windows sub-process, probably already being run by the OS. In the first case scenario it is the fault of Mp3tag. In the second case scenario I will most likely not be able to pint point the process [because there are already running all over my system]

And it is kind of like when I was trying to figure out why sometimes my inactive drive wakes up on its own: when I heard it start to spin I quickly went to the Resource Monitor, to see what process accessing now drive X. Of course no process was ever accessing it- I had whole bunch of them with pathways leading to drive C and some number to other active drives, but I never got to see what was requesting drive X. Maybe if I would stare without blinking at Resource Monitor for a couple of hours, then I could catch that process at the very moment. [My guess is it is my antivirus software doing some brief check of hardware availability / readiness]

This bug report of mine [or a request if it is a fault of Windows] is valid. This current behavior described by me not only has no purpose but it is also counter-productive for anyone who turns off drives on purpose [as we lose time when we wait for them to wake up]

And that solution for waking up is also exactly what I am looking for: even If smeone would write me a file that will step by step:
1] Close MP3tag if it is opened
2] Open Mp3tag [thus start to wake drive X because of this bug]
3] Close Mp3tag
4] Start closing of the Windows, not waiting for the drive X to start spinning with full speed
then my search would be over only until some hypothetical Mp3tag and / or Windows update would stop waking up inactive drives upon opening of software [Mp3tag, CorelDRAW and possible countless others]; because then such file would be rendered useless


#4

The Windows built-in resource monitor is no process monitor as supplied by e.g. sysinternals - see here: https://docs.microsoft.com/en-us/sysinterna...rocess-explorer

This program allows you to add some more substance to your claim of MP3tag bugginess as it would allow you to see whether MP3tag accesses drives that are not included in the playlists.

Edit: on the problem of waking up drives for shutdown:
Some motherboards allow to set SATA ports to a mode in which you can eject the connected drives (i.e. logically disconnect the drives from the OS). Perhaps this is a solution if you do not want to let them run all the time.


#5

OK, I will try out this software for monitoring of the OS

No, that is not a solution. That is asking for a mechanical failure at some point, coming out from constant inserting / pulling out of whatever few times a days, 365 days a year. It would be a real solution if I had like a switchboard under my desk, so that I could plug / unplug a given device [like a specific hard drive] with just a push of a button. [I wish I had such thing- to be able to turn of drives, Internet, lighting with a set of buttons on a control panel of some sort- I bet it is doable but also nobody makes and sell stuff like this]


#6

As I wrote: logically disconnect the drives from the OS. This does not mean to unplug it.


#7

I did finally check out that ProcessExplorer [16.21]

It is a very powerful tool- but I cannot see how I could use it to pint point that mysterious / buggy process. I did not find in it some kind of a list of disks, that would tell me what is accessing them. I only found system Information > I /O > Disk which shown the current overall run numbers for all disks, if I am not mistaken. Other than that, I can click Mp3tag icon to access its Properties > Disk and Network - and see how much reads / writes in terms of quantity and volume was performed so far [and that data does not change if I reload files in Mp3tag]


Although recently this waking up of a wrong drive by Mp3tag has kind of stopped, in spite of me not doing anything to the hardware or operating system. And I checked if this still occurs with for e.g. CorelDRAW. Maybe this unnecessary disk check was somehow fixed with newer releases of Mp3tag?


#8

Then a (perhaps portable) installation of an earlier version for test purposes should recall the behaviour.


#9

I was wrong: that behavior still happens. To be precise it happened once [that I noticed]

It was a case when exceptionally I did not opened Mp3tag somewhere after a boot up, but dozens of minutes later- but I was not loading a playlist of any kind, and my Mp3tag "Favorite directory" is set on the drive where I keep all my music files [which my scarce numbers of playlist evoke]. So that manifestation clearly showed me that it was not a fault of playlist and suggested that it has something to do with the first run of Mp3tag after reboot. Since then I am trying to repeat that by extending the time between a boot up and the [first] opening of Mp3tag, bu to no [un]luck

That access to inactive and irrelevant drive is either something that Mp3tag does on its own [as it has such instruction, but with some additional conditions]; or Mp3tag does it by following some Windows 7 instructions or Windows 7 on its own is making the access, regardless of the fact that Mp3tag does not. I'll bet it is the last one and this will never be figured out