Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] Handling multi-part scenes, "part X" field and/or UI indicator? #2276

Open
Tracked by #3065
KptnKMan opened this issue Feb 2, 2022 · 1 comment
Open
Tracked by #3065
Labels
feature Pull requests that add a new feature

Comments

@KptnKMan
Copy link

KptnKMan commented Feb 2, 2022

Is your feature request related to a problem? Please describe.
Hi, I have been using stash for a few months and really appreciating the file-scene-movie workflow, but the absence of multi-part scene handling is difficult with the workflow. I have content that is split into 2-part scenes, rather than being "scene 1" and "scene 2" it is "scene part 1" and "scene part 2".
This is very popular within JAV/Asian content and other common use cases like ripped movies, where the single scene is 2 files.

This becomes most obvious when tagging and scraping metadata, which I've been using recently a lot more.
When in the tagging view, multi-part scenes need to be tagged as duplicates of the same scene.

Describe the solution you'd like
Thinking about this, I wonder if its feasible to add an additional optional field in the scene tagger view would be possibly the best method I can think of, so the scenes can be marked at the time of scraping/tagging with a signifier of "Part 1" or "Part A" (Or similar) that can then be used to indicate that the files are part of a multi-part scene (See screenshot 1 at bottom with idea).

Additionally, if this field is set, a small UI indicator can be set on the main "Scenes" UI, indicating that this particular scene is part of a multi-part or multi-file scene (See screenshot 2 at bottom for idea of possible UI placement idea).

This would appear to be a method that will not disrupt other workflows already being used by existing users, like the aforementioned file-scene-movie workflow.
Additionally, it would mean that the scraped metadata would not need to be altered, preserving the consistency of metadata that would potentially be synced to stashdb or another sources, as I would like to eventually contribute my manual metadata for community use. When submitting metadata, it will be easy to discard or keep "Part" details at ingestion.

Describe alternatives you've considered
One way I've been looking to resolve this is by manually editing each scene with a "This Scene A" or "This Scene Part-1" identifier so it is cleanly clear in the main scene view that this is a multi-part scene, and not a duplicate.

Another is by creating a movie in the "Movies" UI, and adding each scene as a scene in that movie, but the issue is that these are not strictly "scenes" and are actually "parts". Each part can also contain "scenes", and is inconsistent with a file-scene-movie workflow. Additionally, this creates a lot of extra manual edit work (To do this for hundreds of multi-part scenes), and I'm lazy so I'd rather personally rather stay within the "Scenes" UI for my uses (I cannot speak for other stash users however).

Additional context
Screenshot 1:
Stash_Scene_Issue_1

Screenshot 2:
Stash_Scene_Issue_2

@kermieisinthehouse kermieisinthehouse added the feature Pull requests that add a new feature label Feb 2, 2022
@justwjx
Copy link

justwjx commented Jul 4, 2023

totally agree, a essential request!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Pull requests that add a new feature
Projects
None yet
Development

No branches or pull requests

3 participants