Releascenify
Parse Scene and P2P release names into structured metadata and compare release quality automatically. Built with a rule/regex engine.
Live Demo: https://dmachard.github.io/releascenify/docs/
Why?
Release names follow a strict grammar inherited from the Scene and P2P groups. Once decoded, you can predict the quality, source, language, and release group just from the filename. This library is an alternative to PTN (Parse Torrent Name).
Installation
pip install releascenify
Usage
from releascenify import parse_filename
from releascenify.comparator import get_quality_score, is_better_release
filename = "Gladiator.II.2024.MULTi.2160p.WEB-DL.DV.HDR.H265-GROUP"
parsed = parse_filename(filename)
print(parsed)
# {
# "title": "Gladiator II",
# "year": 2024,
# "resolution": "2160P",
# "quality": "WEB-DL",
# "v_quality": "HDR DV",
# "codec": "H265",
# "languages": ["MULTI"]
# ...
# }
# Calculate quality score
score = get_quality_score(parsed)
print(f"Quality Score: {score}")
# Compare two releases
rel_a = parse_filename("Gladiator.II.2024.1080p.BluRay.x264-GROUP")
rel_b = parse_filename("Gladiator.II.2024.2160p.WEB-DL.x265-GROUP")
if is_better_release(rel_b, rel_a):
print("Release B is better than Release A")
Quality Scoring
For details on how files are rated, scoring weights, and priority factors, see SCORING.md.
Expected Tags & Normalization
Here are the metadata fields extracted by releascenify and how their values are normalized:
Video Codecs (codec)
To make release metadata processing and quality comparison consistent, the parser normalizes various representations of codecs:
H265: Normalized from inputs containingH265,x265,HEVC(including variants with dots or hyphens likeH.265orH-265).H264: Normalized from inputs containingH264,x264,AVC(including variants with dots or hyphens likeH.264orH-264).VC-1: Normalized from inputs containingVC1orVC-1.
Resolutions (resolution)
To keep resolution metadata consistent, they are normalized to standard keys:
2160P: Normalized from inputs containing2160p,2160P,4K, orUHD.1080P: Normalized from inputs containing1080por1080P.720P: Normalized from inputs containing720por720P.4KLIGHT: Extracted from inputs containing4KLIGHT.
Source Quality (quality)
The source tags are normalized to standard quality keys:
WEB-DL: Normalized from inputs containingWEB-DL,WEBDL, orWEB.WEBRIP: Extracted from inputs containingWEBRiporWEBRIP.BLURAY: Extracted fromBLURAY,BDRIP, orBRRIP.REMUX/DVDRIP/HDTV/WEBLIGHT
Audio Codecs (audio)
To keep audio metadata consistent, standard audio codecs are normalized as follows:
EAC3: Normalized from inputs containingEAC3,E-AC3,DDP,DDP2.0,DDP5.1,DDP7.1, etc. (Dolby Digital Plus).DTS-HD MA: Normalized from inputs containingDTS-HD MA,DTSHDMA,DTS-HD.MA,DTS-HD-MA,DTS-HD_MA, etc. (DTS-HD Master Audio).DTS-HD: Normalized from inputs containingDTS-HD,DTS.HD,DTS_HD,DTS HD,DTSHD, etc. when the Master Audio suffix is not present.- Other standard codecs extracted:
TRUEHD/DTS/AC3/AAC/FLAC/MP3. - Note: If
ATMOSis present, it is appended to the base codec (e.g.,EAC3 ATMOS,TRUEHD ATMOS,DTS-HD MA ATMOS). If only Atmos is present, it will beATMOS.
Audio Channels (channels)
- Standard channel counts:
7.1/5.1/2.1/2.0/1.0(mono).
Video Enhancements (v_quality)
HDR/HDR10/HDR10+/DV(Dolby Vision) /HLG/SDR/10BIT/12BIT
Languages (languages)
- Lists of extracted language tags:
VFF(TrueFrench) /FRENCH/VF/VF2/VFI/VFQ/VOSTFR/FASTSUB/EN/VO/MULTI
Network/Platform (network)
- Stream/broadcast platform names normalized:
Netflix(fromNF)Amazon Prime(fromAMZN,AMAZON STUDIOS,AMAZON PRIME)Disney+(fromDSNP,DSNY,DISNEY PLUS)Apple TV+(fromATV,APPLE TV PLUS)HBO Max/HBO(fromHMAX,HBO MAX,HBO)Hulu(fromHULU)Paramount+(fromPARAMOUNT PLUS)
Special Tags (extra)
- Extracted modifiers:
REPACK/PROPER/FINAL/INTERNAL/CUSTOM.
Development & Tests
Setup Local Virtual Environment
To set up the development environment, create a virtual environment and install the package in editable mode with development dependencies:
virtualenv .venv
source .venv/bin/activate
Run Tests
Run the test suite using pytest:
pytest tests/ -v
Run Website Locally
You need to run a local web server from the repository root:
# Start a local HTTP server
python3 -m http.server 8000
Then navigate to: http://localhost:8000/ (which redirects to /docs/) or directly to http://localhost:8000/docs/.
Metadata
Release files for releascenify 0.21.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| releascenify-0.21.0.tar.gz | 47.7 kB | With provenance | Details for releascenify-0.21.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| releascenify-0.21.0-py3-none-any.whl | Python 3 | none | any | Details for releascenify-0.21.0-py3-none-any.whl |
Total release size: 64.2 kB
Release files / releascenify-0.21.0.tar.gz
| Download URL | releascenify-0.21.0.tar.gz |
|---|---|
| Size | 47.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
048f46e2064692c89c248e947e71557f162759cfb5689c40ea2d4ccd912be462
|
|
BLAKE2b-256 checksum How to use checksums |
68773ec07f63f45f7dc6203ed4b5fa6237beae5c25784cae6c2a6144be9da77c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 30, 2026.
Transparency logRelease files / releascenify-0.21.0-py3-none-any.whl
| Download URL | releascenify-0.21.0-py3-none-any.whl |
|---|---|
| Size | 16.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
37fa1b11e62849cceb780690fc1081c9c2feb7868aa9464066e6c87669c9e0a8
|
|
BLAKE2b-256 checksum How to use checksums |
3c1f3bd8715fe208ec6022b30ed1bdfcca5523b0c241390e1572d8f4587b004f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 30, 2026.
Transparency logSecurity for releascenify 0.21.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for releascenify-0.21.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 30, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.