Skip to content

fix: only treat the documented episode range syntax as a range - #893

Merged
arabcoders merged 2 commits into
arabcoders:devfrom
Jellyfrog:fix/episode-range-year-tag
Sep 21, 2026
Merged

arabcoders merged 2 commits into
arabcoders:devfrom
Jellyfrog:fix/episode-range-year-tag

Conversation

@Jellyfrog

Copy link
Copy Markdown
Contributor

Follow up to #886

See individual commits, the second refactor commit isn't strictly needed and can be removed if you prefer.

@arabcoders

arabcoders commented Sep 19, 2026 •

Copy link
Copy Markdown
Owner

Thanks could you explain why S01E01.02 and S01E01_02 are no longer treated as multi-episode files they seem legitimate, also please target dev not master

@Jellyfrog
Jellyfrog changed the base branch from master to dev September 20, 2026 20:10
Follow up to arabcoders#886. Plex and jellyfin both document a range as sXXeYY-eZZ, so a
bare number is only taken after a hyphen. S01E01.50, S01E01.2.0 and S01E01_02
are release tags now, not ranges. An E prefix is still honoured after any
separator, so S01E01-E02, S01E01.S01E02 and E1001-E1002 keep working.

Fixes names such as s05e07.10.chefs.compete.avi, where the episode title starts
with a number. That parsed as episodes 7-10, which fits under the range limit,
so the importer silently fabricated three episodes that do not exist.
Hoisting the tail shapes stopped one step short. Three things still restated
what the tails had already decided.
@Jellyfrog
Jellyfrog force-pushed the fix/episode-range-year-tag branch from 9ba27e3 to de1bfed Compare September 20, 2026 20:17
@Jellyfrog

Copy link
Copy Markdown
Contributor Author

It’s because there are a lot of episodes named like show.s01e01.10.people.mkv, where the 10 belongs to the episode name.
Neither Jellyfin nor Plex naming conventions for multiepisode supports this format

@arabcoders
arabcoders merged commit 12c72ba into arabcoders:dev Sep 21, 2026
@arabcoders

Copy link
Copy Markdown
Owner

Thanks for the clarification, the only reason we need the parse_episode_range is due to lack of support from plex API afaik. jellyfin/emby provide indexRange directly

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants