CommunityScrapers icon indicating copy to clipboard operation
CommunityScrapers copied to clipboard

fix studio code parsing

Open nrg101 opened this issue 7 months ago • 4 comments

Scraper type(s)

  • [x] sceneByURL

Examples to test

  • https://porncornvr.com/scene/neighborly-beauties-rosalyn-sphinx/

Short description

The find-replace regex currently finds the studio code after /scenes/ in the video source URL. In the scene example above, that part of the URL is /scenes2/735/ so the regex just needs updating to allow for digits in the scenes path segment.

nrg101 avatar Jun 09 '25 16:06 nrg101

actually, the studio code may not simply be "735" for this scene as the most recently scraped studio scene with a code is https://stashdb.org/scenes/2d91573d-86cb-438e-8f8d-70908af9770c with "54136"...

so either the scene IDs got reset, or "scenes2" and "735" somehow gets combined (where scenes 2 is like 53305 or something... even though that's a really janky bad guess) to give 54140 or something

this assumes the studio codes ascend numerically over time and have not "reset" recently

nrg101 avatar Jun 09 '25 16:06 nrg101

converted to draft for further investigation

nrg101 avatar Jun 09 '25 16:06 nrg101

https://realjamvr.com/scene/realjamcasting-kayla-kayden/

  • scrapes 51399 for studio code
  • has URL at SLR: https://www.sexlikereal.com/scenes/realjamcasting-kayla-kayden-51399

that is the newest scene listed at SLR, and was published on realjamvr on Feb. 4, 2025, so SLR is several months behind (possibly that is an exclusivity stipulation or something of the studio before redistributing to partners like SLR)

nrg101 avatar Jun 09 '25 16:06 nrg101

Maybe they have two seperate code conventions for redistribution like bellesa does? https://github.com/stashapp/CommunityScrapers/pull/1893

feederbox826 avatar Jun 11 '25 16:06 feederbox826

So just remove studio code parsing?

feederbox826 avatar Jul 04 '25 22:07 feederbox826