Better video file matching using TPDB (PHASH and Search string)

[dkerr7380]

Is there an existing issue for this?

• [X] I have searched the existing open and closed issues

Is your feature request related to a problem? Please describe

This feature is for have better video file matching when importing, by leveraging features from TPDB like PHASH matching and search string.

Describe the solution you'd like

Better intergration with TPDB to resolve unmatch video files to scenes. In the even that Whisperr cannot match a scene allower for TPDB to resolve via the following methods

1. Generate and send a PHASH to tpdb to get back a match. This is the same way how Namer matches videos to scenes https://github.com/ThePornDatabase/namer

2. As a fallback, allow Interactive resolution with TPDB by via search string and selecting a matching from a list of results (pref with images)

Endpoints (examples)	Type	Example
PHASH	https://api.metadataapi.net/scenes?hash=9d29c6789e457683&hashType=PHASH
Parse	https://api.metadataapi.net/scenes?parse=&limit=25

Describe alternatives you've considered

N/A

Anything else?

No response

[nod44]

As a suggestion / discussion topic:

• Stash already uses the phash system and is designed to do a lot of this type of classification (which is error prone, involves a task queue, is resource intensive, etc).
• Should we consider a simple feedback / webook / api interaction where when a release is tagged with a scene in stash, that scene is automatically added to whisparr, and the file is imported.
• As a followup, if whisparr notified stash of the new location that would be ideal.

The benefits of this approach is that it would be vastly less work to implement, it would allow manual matching and overrides to be easier, and it also allows stash uses to more readily organize files on disk which is something stash doesn't want to do.

CC: @Qstick @dkerr7380 @thezak48