Role Tagger

Unfortunately, I have again performance problems because of the plugin. It‘s only when clicking to show the performers overview, edge displays a message of memory lack. and mini-browser (as lightweighted alternative) simply refuses to show anything. Despite of 32 GB RAM.

Is it still possible to optimize something in the plugin?

Can it be used without Python if I don‘t need the scrapers?

I use Windows natively. Could the reason be that I installed Python from the org. site and not from the Microsoft store as you recommended on your plugin website?

Hey @zelpi

It’s hard for me to reproduce, so I’m kind of stabbing in the dark with this next release. I’ve made the plugin do nothing per card in the performer overview list. It still runs there, but now exits immediately instead of doing some preloading in preparation of a card click, which would have added up fast with the 120 or more performers option selected. Hopefully that fixes this issue.

I’ve also stopped the roles pop-up within scenes from holding onto data after exiting. Previously, that data just sat in memory for the rest of the session. (Probably unrelated to the bug you’re experiencing, but still nice nonetheless for a long browsing session)

I pushed these two optimizations in 2.2.6, out now.

On Python: part of it is used in the scrapers, and other functions like Apply always-role, Apply role to selected items, Clear all role assignments, Clean up stored role tags, etc. It’s unlikely that Python is causing this issue though, because that happens server-side, not browser-side.

Edit: I don’t think .org vs MS Store should make a difference, both work the same way :grin: I just recommended MS Store for the easiest way to install it.

Tested it and it seems to work better after your update. Performer grid loaded faster. I have still some loading seconds from time to time (in general), but I can live with that.

Thanks for the efforts.

1 Like

Feature Request: I think this is probably outside the scope of your Plugins, but would you considering adding support for Performer:Performer? Currently it is Scene:Performer

I kinda want to build relationship between two Performer, for example: Sister:Sister

Just trying my luck! PS: good job with the push for StashDB Box

Hey @sashi ! Yeah, definitely a new plugin because this plugin’s scope is Scene:Performer.

A pretty simple plugin though, testing now, but it confirming it would be something outside of a scene, yeah? Like IRL:

  • Performer A is brother/sister of Performer B (directionality doesn’t matter),
  • Performer C is husband of Performer D / Performer D is wife of Performer C (gender directionality matters, and should a marriage date be in scope?)
  • Performer E is mother of Performer F / Performer F is son of Performer E (directionality matters + gender inference on parent/offspring).

Birth year inference could be brought into the mix too with Performer A is older sister of Performer B / Performer B is younger sister of Performer A.

If that sounds good, I’ll get something together in a new thread.

Edit: In the meantime, first version is up in this thread: Performer Relationships

1 Like

Important Announcement: The plugin source is changing

As I get more comfortable with making more plugins, a single index is now available of all the plugins from one source. This one will distribute updates in future. The old source under Available Plugins can be replaced with this URL using the edit function: https://heman.codeberg.page/stash-plugins/index.yml

1 Like