Update Mindgeek API (Local + Marker support)

[Belleyy]

• Copy official marker. (You will need to have the main tag)
  It could lead to incorrect marker because sometimes the time is off. (File with different duration that the official, official marker are just incorrect 🤷‍♂️ ). I have a file that is 20min off than the official 🤔

• Use local json if you have them and the scene url fail

[bnkai]

I think (haven't verified that) that all scenes that have timeTags also have the scene duration in seconds mediabook.length
You could check for existence of the timeTags (like you do now) and then compare the duration from the official mediabook file to the one in the stash db. If the duration is off by a fixed amount then dont apply any markers

[Belleyy]

I think (haven't verified that) that all scenes that have timeTags also have the scene duration in seconds mediabook.length You could check for existence of the timeTags (like you do now) and then compare the duration from the official mediabook file to the one in the stash db. If the duration is off by a fixed amount then dont apply any markers

Oh yea, i thought that this length was the trailer because the other info below is for trailer. But i checked and it's probably the real length.
Some scene have this set to 0/1 😞 What i should when this happens, create the marker or ignore it, or create a new variable to allow create marker without caring about mediabook.length.
Since marker is a specific moment, the difference need to be real close ? (5 sec maybe ?)

[bnkai]

Yeah i am not sure either.
If the length is close enough or equal marker should be ok. If the difference is too much i dont think the scraped markers would be useful. As for 0/1 it could be either way. Imo anything you choose is fine

[Belleyy]

Updated with different variable to control Marker creating, the difference is 10sec (Between MindGeek vs Stash) should be good enough i think.

[bnkai]

Merging with minimal testing though as not many scenes seem to have timetags..