Recognize folder scope

ℹ️ Support
1

Hi,
At first, I didn’t have a Memories folder configured (indexing all media). Then I switched to indexing relative paths (/Photos).

So, now I have a user with an empty Photos folder, the Photos app shows nothing (correct), Memories shows nothing (correct), the People section of Memories shows nothing (correct), but the People section of Photos shows many people from directories other than Photos. Is this correct?
Could I limit the scope of Recognize to just the Photos directory (for all users)?

Using .nomedia (or similar) isn’t an option, I think, since for each new folder, the user would have to intentionally remember to create this file…

Many thanks!

2

Hi @RXS

This is currently not possible. We may implement this for the revamped version of recognize, though.

3

Hi @marcelklehr, thanks for the reply.

So, how can I work around this? How can I prevent face recognition outside the photos folder?

  1. Should I add the .nomedia files to the unwanted folders?
  2. What command should I use: delete index/reindex/force/clear? Per user or all?

Thanks!

4

Just adding the .nomedia file to the unwanted folders should be enough

5

Sorry, I misspoke. If I have a directory currently scanned (with faces), what would be the procedure to (a) stop it from recognizing that directory and (b) delete the faces found within it?

a- using .nomedia
b- ???

6

Putting in place the .nomedia file should be enough, recognize has a listener in place that removes detections for files that are covered by newly added .nomedia files

1 Like
7

This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.