Re-tagged items appearing in Recently Added

[paulM]

(14-12-2022 23:11)simoncn Wrote:  Deleting added-dates.txt would make things worse, not better. 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.

Unfortunately, I think that this may have already happened while I was flailing about trying to remove the unwanted entries.

(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. This would make all the bulk retagged files disappear after the next rescan. 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. For example the fake entry could be something like:

2022-10-01 00:00:00.000 /share/Music/Fake/Path.flac

and this would eliminate any files retagged after 1st October. I will try this tomorrow and post back here.

I tried this without success - but that's probably because of my above flailing.

(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=2022-10-01.

I'd like to try this, but I am uncertian which field in properties to use. 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. Any suggestions?