.. |logo| image:: ./logo/namer.png :width: 80 :class: display: inline flow; align: left
############## |logo| Namer ##############
|_ci_badge| |_codecov_badge| |_pypi_badge| |_pypi_download_badge| |_download_badge| |_download_month_badge|
Namer is a powerful web app, folder watchdog and command line tool for renaming video files and tagging mp4 video files in a way that helps plex/jellyfin/emby and related plugins extract that data or lookup data with the PornDB_'s plugins for plex or jellyfin/emby.
Namer is easily installed as a python pip and can:
namer now support perceptual hashes by default and can identify video files that don't have parsable names.
can be run watching a directory for new files to name, tag and move to an output location, possible setting file permissions, writing .nfo files with downloaded images, attempting to grab trailers, and retrying failed files nightly.
python -m namer watchdog
while running watchdog, will also have a webui that can be used to manually match and rename any files that could not be automatically matched. You can set the webroot, port, bound ip, enable/disable in your namer.cfg file.
http://<ip>:6980/
can be used to name and embed tags in individual files with metadata from porndb:
python -m namer rename -f /path/to/file/Site.[YY]YY.MM.DD.MessOfText.XXX.2160.mp4 [-v]
can be used to name and tag files with metadata from a jellyfin/emby/kodi .nfo file (should be named the same as the file except for extension).
python -m namer rename -f /path/to/file/Site.[YY]YY.MM.DD.MessOfText.XXX.2160.mp4 -i [-v]
can be used to rename a tag a file based on the directory name, so if you have a file like /Site.[YY]YY.MM.DD.MessOfText.XXX.2160/abc.mp4
python -m namer rename -d /path/to/dir/Site.[YY]YY.MM.DD.MessOfText.XXX.2160/
can be used to rename a tag a whole mess of dirs and files in a directory (using -m, meaning "many").
python -m namer rename -m -d /path/to/dir/
can be used to just suggest a possible name. The file doesn't need to exist but should have an extension.
python -m namer suggest -f Site.[YY]YY.MM.DD.MessOfText.XXX.2160.mp4
For all of the above it's recommended to have a config file in your home directory (copied from namer/namer.cfg.default in this git repo)
Also provided is a docker file if you prefer.
It is possible to ignore and not need to parse dates for studios added to a list in the configuration file. This is mostly used for studios that do not list dates on videos.
For data pulled from the internet with rss feeds (which are often in the file format listed below) .... very near perfect. The author and others have only experienced two mismatches, and those type of failures can never occur again.
If running in a background watchdog mode, files that were failed to match are retried every 24 hours, letting the PornDB_ scrapers catch up with any metadata they may be missing.
Optionally, a log file can be enabled to show the original file name parts, what options were evaluated, and which match was used to name the file, it will be written next to your video file with the same name as the file (with a _namer.log) suffix rather than an mp4/mkv/avi/mov/flv extension. This is very useful for sanity checking matches, and if ever a mismatch does occur the original file name is available in the log.
Namer assumes that file names exist as in a format like sitename-[YY]YY-MM-DD-Scene.and.or.performer.name.mp4.. A powerful regex tries to determine the various parts of a file's name. Note that the separating dashes and dots above are interchangeable, and spaces may also be used as separators (or any number of any combo of the three.) This regex is overridable, but you really need to know what you're doing and if you don't have all the match groups for the regex, the match from the the PornDB_ will likely not be any where near as robust as it is with a site, a date, and a scene/perform name section.
You'll have to read the code to figure out how to set this. You really shouldn't do it.
When determining a possible queried match from the PornDB_:
Sitename my not need be the full name of the site, as long as a the looked up sitename starts with file's sitename it could be a valid match.
The date may have a four digit or two digit year. If two digit, "20" is assumed as the default century, not "19". A potential match must be with one day plus/minus the file's date to be considered a match.
Finally the looked up scene name and all performers first and last names are combined in to what is called a powerset (every combo of including or not including each artist and/or scene name), and that is compared against the file's 'Scene.and.or.performer.name' section with a tool called rapidfuzz. A name must be 95% similar to a member of the powerset to be considered a match, though all potential matches are evaluated and sorted before selecting the best match. Information about all potential matches are stored in the local log file if it is enabled.
At the same time name based matching is occurring, a perceptual hash is built and queried against the PornDB_.
All matches, regardless of source are made unique with the PornDB_'s UUID (universally unique identifier). If more than one unique match exist, or no match exists but partial name matches exist, all data is available in the web ui for users to select the correct match.
You have two choices. Do you use docker? Pull the docker image, here's docker-compose snippet to help you out.
.. code-block:: yaml
version: "3" services: namer: container_name: namer image: ghcr.io/theporndatabase/namer:latest environment: - PUID=1001 - PGID=1000 - TZ=America/Los_Angeles - NAMER_CONFIG=/config/namer.cfg volumes: - /apps/namer/:/config # <- this will store the namer.cfg file copied by you from the git repo ( namer/namer.cfg.default ) - /media:/data # <- this will have the four folders namer needs to work, referenced in the namer.cfg file you create. healthcheck: # <- if on a qnap nas, the default health check will not work for you, domain name is the container_name test: [ "CMD-SHELL", "curl -f http://namer:6980//api/healthcheck || exit 1" ] interval: 1m timeout: 30s # retries: 3 # start_period: 40s restart: always
Copy namer.cfg to your config location (a path mapped to /config/namer.cfg above), and set values for your setup. The config is well commented and you should only need to add a token for the porndb and change file locations.
Running a service will occur automatically once you call docker-compose up. Now check out the configuration section below.
A detailed install tutorial can be found at Install Instructions_
There is a well documented template of namer.cfg in this git repo, which is broken up in to three sections.
One section is related to command line renaming, the namer section, one related to tagging mp4s metadata section,
and finally one related to the watchdog process watchdog section.
Please note that the namer section section and the watchdog section_
section both have a field to describe the new name of a file based on looked up metadata from the PornDB_.
They differ because when run from the command line namer will keep the file "in place".
If namer is passed a dir on the command line as input it can operate in one of two modes,
the default mode is to look for the largest mp4 file, or other configured movie file extension if no mp4 exists,
and rename and move that file to the root of the folder (if it's in a sub-folder).
In this case, by default the assumption is the name of the folder should be parsed to look for information to
search the PornDB_ for matching rather than the file name. Meaning,
if you pass a file to namer on the commandline it will be renamed but stay in the same directory.
The watchdog process will watch a single folder, configured with watch_dir_ in the namer.cfg file. Any new files and directories that appear in the watch_dir_
will be processed once an mp4/mkv/avi/mov/flv file has been fully copied in to it.
The first step in processing is to more the newly appearing directory or file in to the work_dir_.
Once moved the processing is highly dependant on the namer.cfg file, but in general, the name of video file or the directory file (configured with prefer_dir_name_if_available flag)
is parsed and matched with a scene from the PornDB_. See For the curious, how is a match made?. If a match cannot be made the general assumption is that the PornDB doesn't have metadata for that file yet.
The file is move to the failed dir fail_dir_ to be retried once a day at a time configured with retry_time_,
which by default will be a random selected minute in the 3am hour of your timezone. If enabled_tagging_ flag is set to true then
the metadata (including cover art if enable_poster_ is set) will be embedded in the mp4 file. Please read the comments in the namer.cfg to find out about genres, tags, performers, etc.
Finally, the file is moved to a location defined by dest_dir_ and new_relative_path_name_.
.. code-block:: sh
poetry self add 'poethepoet[poetry_plugin]'
pip add poethepoet
poetry env use 3.11
poetry run poe build_all
poetry run pytest --cov
poetry run coverage html
pip install ./dist/namer-.tar.gz
poetry config pypi-token.pypi
poetry version
poetry publish
./docker_build.sh
Just be sure to pay attention to the tests and any failing pylint results. If you want to vet a pr will be accepted before building code, file an new feature request issue, and 4c0d3r will comment on it and set you up for success. Tests are must.
.. _PornDB: http://theporndb.net/ .. _namer section: https://github.com/ThePornDatabase/namer/blob/main/namer/namer.cfg.default#L1 .. _metadata section: https://github.com/ThePornDatabase/namer/blob/main/namer/namer.cfg.default#L59 .. _watchdog section: https://github.com/ThePornDatabase/namer/blob/main/namer/namer.cfg.default#L89 .. _watch_dir: https://github.com/ThePornDatabase/namer/blob/main/namer/namer.cfg.default#L100 .. _work_dir: https://github.com/ThePornDatabase/namer/blob/main/namer/namer.cfg.default#L104 .. _fail_dir: https://github.com/ThePornDatabase/namer/blob/main/namer/namer.cfg.default#L109 .. _dest_dir: https://github.com/ThePornDatabase/namer/blob/main/namer/namer.cfg.default#L112 .. _retry_time: https://github.com/ThePornDatabase/namer/blob/main/namer/namer.cfg.default#L115 .. _new_relative_path_name: https://github.com/ThePornDatabase/namer/blob/main/namer/namer.cfg.default#L97 .. _enabled_tagging: https://github.com/ThePornDatabase/namer/blob/main/namer/namer.cfg.default#L67 .. _enable_poster: https://github.com/ThePornDatabase/namer/blob/main/namer/namer.cfg.default#L72 .. _Homebrew: https://docs.brew.sh/Installation .. _Chocolatey: https://chocolatey.org/install .. _Install Instructions: https://github.com/ThePornDatabase/namer/blob/main/install_instructions.md
.. |_ci_badge| image:: https://github.com/ThePornDatabase/namer/actions/workflows/ci.yml/badge.svg? :target: https://github.com/ThePornDatabase/namer/actions/workflows/ci.yml/ .. |_codecov_badge| image:: https://codecov.io/gh/ThePornDatabase/namer/branch/main/graph/badge.svg?token=4MQEN2NUKZ :target: https://codecov.io/gh/ThePornDatabase/namer .. |_pypi_badge| image:: https://badge.fury.io/py/namer.svg? :target: https://badge.fury.io/py/namer .. |_pypi_download_badge| image:: https://img.shields.io/pypi/dm/namer?logo=pypi&logoColor=fff :target: https://pypi.org/project/namer .. |_download_badge| image:: https://static.pepy.tech/personalized-badge/namer?period=total&units=international_system&left_color=grey&right_color=yellowgreen&left_text=Downloads :target: https://pepy.tech/project/namer .. |_download_month_badge| image:: https://static.pepy.tech/personalized-badge/namer?period=month&units=international_system&left_color=grey&right_color=yellowgreen&left_text=Downloads/Month :target: https://pepy.tech/project/namer
FAQs
A namer of video files based on metadata from the porndb.
We found that namer demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 2 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
PyPI confirms no security flaws were exploited in the Ultralytics supply chain attack and highlights improvements for safer package publishing.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
