ALL:
I asked in today’s meeting.
At present,
-
When anything about the media item changes (like a new path), it’s going to rerun the detection. ( It wasn’t written to be smart about that )
-
The team agrees it should be smart enough to track the item by its ID/Hash code in the DB just as metadata does.
-
At their suggestion, this has been written up as a Feature Request and accepted.
I don’t know which release cycle the work will be done in but it will be done.
For now, the workaround is to manually edit the DB (carefully).