![]() ![]() Following your advice, I tried an alternative fake path and second time around, the trick worked. (17-12-2022 22:00)simoncn Wrote: I tried the "fake path" trick and it does work. This might not be exactly correct but it should be fairly close. MinimServer would then go back before and show files based on their "last modified" dates. For example, if the batch editing was done on, setting the "fake path" to would ensure the batch edited files don't appear in your "recently added" list. This would be tedious and error-prone.Īnother option is to use the "fake path" trick to eliminate all your batch edited files from the "recently added" list. ![]() You could try to recreate the added-dates.txt file based on your knowledge of when you added files to your library. This is why the User guide page describing this feature tells you that the added-dates.txt file contains essential information and should be backed up regularly. If you have deleted the added-dates.txt files, your "recently added" information is lost and cannot be retrieved. Also, it would do exactly the same as the "fake path" trick which hasn't solved your issue. My reference to a "new property setting" was about something that might possibly be added to MinimServer in the future, not something that is available now. I tried the "fake path" trick and it does work. I've tried serverOptions and tagOptions but the latter resulted in a red icon, so I decided to stop flailing again before I do any more damage. I'd like to try this, but I am uncertian which field in properties to use. (14-12-2022 23:11)simoncn Wrote: A nicer solution could be to have a new property setting instead of this "fake" entry, something like addedStartDate=. I tried this without success - but that's probably because of my above flailing. I will try this tomorrow and post back here. 00:00:00.000 /share/Music/Fake/Path.flacĪnd this would eliminate any files retagged after 1st October. For example the fake entry could be something like: I think it would be OK for this "fake" entry to have a file path that doesn't correspond to any real files in your library, as long as it is a valid path. This would make all the bulk retagged files disappear after the next rescan. (14-12-2022 23:11)simoncn Wrote: You could add a "fake" entry at the start of added-dates.txt that is older than the date when you did the bulk retagging. Unfortunately, I think that this may have already happened while I was flailing about trying to remove the unwanted entries. If you do this, the entire contents of the "recently added" list would be recreated based on "last modified" dates including files that were modified by bulk retagging. (14-12-2022 23:11)simoncn Wrote: Deleting added-dates.txt would make things worse, not better. There must be more users noticing this behaviour? ![]() This is not only related to changes made after, but to all changes I made since I started using MinimServer (2013). It seems that Recent Added is largely affected by renaming Folders. I have been able to redate files using this program: Attribute Changer There is no need for you to run the rescan debug logging now. Renaming a folder does not change the "last modified" date of the folder but does cause MinimServer to detect the album as having been added. I am sure this is the reason for the added-dates.txt entries for this album. However related to changes made (making artwork visible in folderview- started at ) this seems not very plausible (15-12-2022 20:46)simoncn Wrote: (15-12-2022 19:57)Peter StreamMagic Wrote: Comparing the folders on my NAS and PC I found a change was made in the folder name: Jimmy Aldridg e&Sid Goldsmith was changed to Jimmy Aldridge & Sid Goldsmith I don't no for sure when this change was made.This could have been at, but latest folder change date is set to. This file will return to a smaller size the next time you stop and start MinimServer from the App Center to do another rescan. After this, contact me by PM and I will send you instructions for getting these files to me.Ĥ) If everything looks normal, be aware that running MinimServer with the logging level set to Debug will make the minimserver.log file grow very large. At the same time, copy the added-dates.txt and added-files.txt files. This automatically does a rescan.ģ) If you see something unexpected in Recently added, use File Station on the QNAP to copy the minimserver.log file from the MinimServer shared folder to another location or filename. Ii) Using the MinimWatch Properties window, check that the startupScan property is set to true (the default setting).Ģ) From App Center, start MinimServer. This is a permanent setting while you are testing. I) Using the MinimWatch Log window, set the logging level to Debug, then close the logging window. The following is the simplest way to do this on QNAP. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |