When I go to File > Add/Rescan Files To The Library, MediaMonkey keeps adding another path to scan instead of what I want it to scan.
I normally have MediaMonkey set to scan D:\Music\, but every time I open the Add/Rescan Files To The Library dialog, it has added and selected another path. I have tried to delete it and save it, but the next time I open Add/Rescan Files To The Library it is back. I have also tried manually editing MediaMonkey.ini, but I still have the same problem.
I think it may have something to do with the last track played, although my playing list is empty.
Hi dypsis, I think I'm able to replicate something similar to what you're reporting:
The latest build always scans the directory containing the currently selected track. BUT:
- if the currently selected track is from the Playing list, the directory from the tracklist is scanned
- if the tracklist displays a view in which no track is selected [Browser view, Grid by X, List by album] then the directory that MM scans is based on some invisibly selected track
dypsis wrote: ↑Mon Oct 21, 2024 5:55 pm
I'm not sure why anyone would want that behaviour.
I am for example very grateful for current implementation and use it daily eg. when do backups from Radio stations and/or organize their libraries I:
1. double click on track in Explorer -> opens MM and play
2. Select track -> press INSERT -> Dialog Opens with that folder selected (others unselected as some contain 100k+ tracks that can scan for hours) -> OK
3. Previously I would need to manually add folder with track and then scan it, so current implementation saves me 10+ clicks
dypsis wrote: ↑Mon Oct 21, 2024 5:55 pm
I liked it how it was where I was in control of what it scans.
There were bug(s) where desired behavior was not correctly executed in some cases (your included and in some rare cases when I use it), 3066 should fix those and both of us will be satisfied. Or we will further tweak things.
@Peke
I'll wait to see if 3066 addresses my issues. 3064 is unacceptable to me. I have no use for such a thing. It's also a bit deceptive when saving the setting doesn't actually save the setting that the user wants. Maybe it could be included as an option that could be turned on or off.
Also, if Add/Rescan Files To The Library was enabled at startup, it could add stuff that someone doesn't want added.
I use Add/Rescan on a regular basis, not to bring in tracks but to bring in m3u files. There aren't any tracks that could be clicked and played, and so I'm missing out on the convenience that Peke mentioned. I suspect that that is not a core use case and I'm not expecting any design fix. So I'm stuck with multiple mouse clicks; it could probably be better but it is an acceptable overhead for me.
What I do note is that the dialog box routinely offers me one to several folder paths that I have used previously, and not necessarily recently. Presumably this is the behaviour that Rusty is tracking. I delete these additional folder paths when I see them so that there is NO chance that Add/Rescan will go off on an unnecessary file hunt, and that is a few more clicks. I would be happier if the file paths offered were a little more consistent with my recent selections.
Cheers
Matt
Last edited by MattTown on Wed Oct 23, 2024 6:19 pm, edited 1 time in total.
MM 2024.1.0.3162 debug (WEF 4 Jun 2025, Portable Mode), Gold lifetime license, user since 2009.
Currently 29K files. Library and music files are on a separate partition (E:\) on external USB drive.
Windows Surface Book (Original), i5, 8GB RAM, 250GB SSD.
Win10 Pro 64 bit, update: 22H2 19045.5131
MMA 2.0.6.1251, Android 14 on Nokia XR20, music files on SD card.
It's frustrating if you don't want this behavior. I only want the minimum number of folders in Scan/Rescan. But, no matter how many times I delete the ones I don't want there, they just keep coming back. One example is a folder for one album that is already within the music folder. If I delete a path, I want it to stay that way
TheEmpathicEar wrote: ↑Tue Oct 22, 2024 8:33 am
If I delete a path, I want it to stay that way
I agree, but from y tests and usage when I scan (not save) folder using my steps then file -> Add tracks do not have last scanned folder listed but only those that were manually set or I missed something.
MattTown wrote: ↑Tue Oct 22, 2024 7:06 am
I use Add/Rescan on a regular basis, but to bring in tracks but to bring in m3u files.
Can you give steps you use to add M3Us?
Finally if This is option that needs to be revised or redesigned then this is the great time, cause we will be prioritizing Features/Bugs/Tweaks for next mayor build.
dypsis wrote: ↑Tue Oct 22, 2024 12:55 am
@Peke
I'll wait to see if 3066 addresses my issues. 3064 is unacceptable to me. I have no use for such a thing. It's also a bit deceptive when saving the setting doesn't actually save the setting that the user wants. Maybe it could be included as an option that could be turned on or off.
Can you elaborate a bit, I am not sure what you actually want to have ON/OFF for.
dypsis wrote: ↑Tue Oct 22, 2024 12:55 amAlso, if Add/Rescan Files To The Library was enabled at startup, it could add stuff that someone doesn't want added.
Ok, I am confused, it was never ever recommended to have main Root Media folder set to scan on startup or I again do not understand something. And I want to understand
[Attempt to simplify] Look at the diagram at the top of this thread. In my build, latest MM5, there are little trashcans to the right of each path/folder. I click on this and it goes away. After doing another Scan/Rescan, it comes back?
TheEmpathicEar wrote: ↑Tue Oct 22, 2024 12:59 pm
[Attempt to simplify] Look at the diagram at the top of this thread. In my build, latest MM5, there are little trashcans to the right of each path/folder. I click on this and it goes away. After doing another Scan/Rescan, it comes back?
Not for me unless I initiated Add/Rescan on INS and selected track, that should be fixed in 3066 where single track not in MM library folder is presented for scan using INS key.
If we missed something else we can do further tweaks in 3067. I am also curious how it will work in 3066 as it is hard to guess atm.
TheEmpathicEar wrote: ↑Tue Oct 22, 2024 12:59 pm
[Attempt to simplify] Look at the diagram at the top of this thread. In my build, latest MM5, there are little trashcans to the right of each path/folder. I click on this and it goes away. After doing another Scan/Rescan, it comes back?
TheEmpathicEar wrote: ↑Tue Oct 22, 2024 3:50 pm
@Peke Is a new build going to fix this? And, what got this started in the first place? It still makes no sense to me.
What got it started? Good question. It seems like they fixed something that wasn't broken until they broke it.
dypsis wrote: ↑Tue Oct 22, 2024 4:08 pm
What got it started? Good question. It seems like they fixed something that wasn't broken until they broke it.
TheEmpathicEar wrote: ↑Tue Oct 22, 2024 3:50 pm
@Peke Is a new build going to fix this? And, what got this started in the first place? It still makes no sense to me.
It will be simpler to answer both at same time. The main reason for change is that many users complain about not being able to scan Shared folders on their NAS or other PC or DAS or RAS or WEBDAV or ... Th reason is Actually in Windows which phased out several Networking discovery features worked for decades in favor of MS introduced features that are not fully implemented or missing in many many unix structure based PCs/Devices (Android Included) Some of them are SMBv1, NETBios, Network neighborhood, Workgroups, WINS. Local Master Browser, ... topically available on Linux based PCs, ... That said problem is that after Win 7 phased out in EOL and Win 10 took over many many of our users complained that they do not see Shared folders. Not to blame Windows only WD named some of their devices as NAS which were not NAS and phased them as EOL 2021 which lead many users stranded. If you are lucky one not have seen that issue they feel really lucky, but most of us did. MM5 changed add/rescan dialog and only after some time better Shared folder access is implemented which involved 15+ clicks to add shared folder to MM. Finally it was resolved by adding current behavior, which like pointed in bug introduced negative behavior that we target to fix in 3066. Which if it is not fully solved will be worked on in 3067 till all cases work correctly/accessible.
P.S. Shortest answer for above is that I was somewhat to blame as My MM was completely unusable and I (and few other users ) lost access to 155k+ of tracks I collected over 30+ years, by not being able to recognize NAS.
