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 Request] Manage/Organize filenames and paths based on existing filenames and tags #55

Open
TedlyTheTalker opened this issue Nov 6, 2020 · 3 comments
Assignees
Labels
enhancement New feature or request
Projects

Comments

@TedlyTheTalker
Copy link

TedlyTheTalker commented Nov 6, 2020

I have a fairly large selection of content. I have manually renamed most of my content so that it’s fairly comprehensible. There are site-to-site inconsistencies with filename schemes, and some sites re-release or distribute to another site. Not only is manually managing file names a PITA, it’s also hard to find duplicates of the content as different files may have different resolutions, file sizes, encodings, or dating. This is further complicated by the fact that sometimes alternates are sometimes desirable (e.g. I may want to keep a VR version and non-VR version of the same scene, or a 5K version and a lower resolution version).

I would prefer to an automatic file managing scheme that I can adjust based on tags, to fit the renaming to my specific preferences.

I have files that are released by a particular site that I would generally like to use one filename scheme: <site> - <yy>.<mm>.<dd> - <optional scene name> - <actress1>, <actress2>, & <actress3>.ext
.\VR\<site> - <yy>.<mm>.<dd> - <optional scene name> - <actress1>, <actress2>, & <actress3>.ext

Whereas some other content that are movies with just a Title, that I would like to add information to the filename: .\Movies\<Title> (<YYYY>) - <actress1>, <actress2>, & <actress3>.ext

Ideally, the organizer could look at a specific folder to find content to organize into my library, and be triggered manually or watch the folder and work completely automatically.

@cooperdk
Copy link
Owner

You mean, a setting so that fx a site named My Dirty Maid is recognized, YAPO should (if any specific naming scheme is entered in that site's settings) use a custom naming convention specifically for that site?

Which also supports that if it recognizes a dvd-rip/blu-ray rip (recognized due to various aliases) it wil fx name the files DVD - - <title> - <actress(es)>

This is a good idea because that would open up for a lot of possibilities. First, I have to figure out how to support a naming convention. The way YAPO works now, all actors (scanned with TpDB) are collected in one string and they are separated with a comma. But TpDB will not recognize movies, and most movies don't have actors in their filename. Maybe I need to find a site to scrape adult movie information from...

@cooperdk cooperdk added the enhancement New feature or request label Dec 25, 2020
@cooperdk cooperdk added this to Incoming changes in To-do list via automation Dec 25, 2020
@cooperdk cooperdk moved this from Incoming changes to Medium priority in To-do list Dec 25, 2020
@jeremymeyers
Copy link

themoviedb.org , while not comprehensive, does have a lot of adult movie content and also has an api

@cooperdk
Copy link
Owner

I just saw your comment.

Yes; YAPO already uses TMDB for actor images (because they are generally the best) and basic information.

But, it only has relatively few adult movies and only the most famous ones. I am thinking about creating a scraper for Adult DVD Empire, and (mostly a reminder for myself) there is xpaths here to get started

https://github.com/adultplexdev/AdultDVDEmpire.bundle/blob/master/Contents/Code/__init__.py

I think I will code it so that YAPO expects a clip over 5976 seconds (1 hour and 20 minutes) to be a movie. Most adult movies are at least that, and only the fewest web clips are that long.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
To-do list
  
Medium priority
Development

No branches or pull requests

3 participants