starred/jellyfin
1
0
Fork 0
mirror of https://github.com/jellyfin/jellyfin.git synced 2026-07-16 05:43:54 +03:00
Code Issues 822 Packages Projects Releases 17 Wiki Activity

[Bug] Wrong season assignment when importing metadata from TubeArchivist due to filename parsing error in jellyfin #7824

New Issue
Open
opened 2026-02-07 05:25:34 +03:00 by OVERLORD · 0 comments
OVERLORD commented 2026-02-07 05:25:34 +03:00
Owner
Copy Link

Originally created by @AlexAlex777 on GitHub (Nov 23, 2025).

Description of the bug

Jellyfin seems to incorrectly extract the season (which should be its release year) for TubeArchivist files. No NFOs are involved in the intermediation of data between TA and jellyfin.
For example, for the file with the following name rbu7Zu5X1zI.mp4, jellyfin incorrectly assigns it Season 5 instead of 2024 when it was published on YT.
Inside jellyfin's reported metadata for the file, the release date is 12/10/2024 (which is correct) and it's year is also correct (2024).
As someone else on TA's page reported in April, https://github.com/tubearchivist/tubearchivist-jf-plugin/issues/30, this seems to be a naming parsing error in Jellyfin when processing filenames (some sort of regex-based exception maybe?). Basically if there's an "x/X" or "-" in the file's name, it gets assigned as season the number before the "x" instead of the year.

Reproduction steps

  1. Run TA and download mp4 files
  2. If the name of the file contains a number followed by an "x", "X" or "-", then the year is ignored and the number before "x/X/-" becomes the season saved by jellyfin for that particular file
  3. This can also be reproduced manually by changing the name of a file which doesn't satisfy the rule above and triggering a "show" level metadata replace scan - the file will be moved from the Season "Year" to Season "any number you placed before x/X/-" in the filename
  4. Same behaviour with TA 0.5.7/0.5.8, or plugging version 1.4.2/1.4.3, same issue across jellyfin version 10.10.7/10.11.0 and 10.11.3

What is the current bug behavior?

Jellyfin seems to incorrectly extract the season (which should be its release year) for TubeArchivist files. No NFOs are involved in the intermediation of data between TA and jellyfin.
For example, for the file with the following name rbu7Zu5X1zI.mp4, jellyfin incorrectly assigns it Season 5 instead of 2024 when it was published on YT.
Inside jellyfin's reported metadata for the file, the release date is 12/10/2024 (which is correct) and it's year is also correct (2024).
As someone else on TA's page reported in April, https://github.com/tubearchivist/tubearchivist-jf-plugin/issues/30, this seems to be a naming parsing error in Jellyfin when processing filenames (some sort of regex-based exception maybe?). Basically if there's an "x/X" or "-" in the file's name, it gets assigned as season the number before the "x" instead of the year.

What is the expected correct behavior?

Release year of the mp4 should be the Season number for the specific file.

Jellyfin Server version

10.11.3

Specify commit id

No response

Specify unstable release number

No response

Specify version number

No response

Specify the build version

10.11.3

Environment

- OS: UGOS Pro
- Linux Kernel: Linux 6.12.30
- Virtualization: Docker
- Clients: -
- Browser: -
- FFmpeg Version: -
- Playback Method: -
- Hardware Acceleration: -
- GPU Model: - 
- Plugins: TA 1.4.3
- Reverse Proxy: -
- Base URL: -
- Networking: -
- Jellyfin Data Storage: -
- Media Storage: - 
- External Integrations: -

Jellyfin logs

No relevant logs are produced. Jellyfin thinks is parsing the files correctly so no relevant logs are generated.

FFmpeg logs

Client / Browser logs

No response

Relevant screenshots or videos

No response

Additional information

This seems to be related to https://github.com/jellyfin/jellyfin/issues/13197, but in my current configuration of TA, there are no NFO objects involved, the plugin should get the metadata directly from TA's DB.

Originally created by @AlexAlex777 on GitHub (Nov 23, 2025). ### Description of the bug Jellyfin seems to incorrectly extract the season (which should be its release year) for TubeArchivist files. No NFOs are involved in the intermediation of data between TA and jellyfin. For example, for the file with the following name rbu7Zu**5**X1zI.mp4, jellyfin incorrectly assigns it Season 5 instead of 2024 when it was published on YT. Inside jellyfin's reported metadata for the file, the release date is 12/10/2024 (which is correct) and it's year is also correct (2024). As someone else on TA's page reported in April, https://github.com/tubearchivist/tubearchivist-jf-plugin/issues/30, this seems to be a naming parsing error in Jellyfin when processing filenames (some sort of regex-based exception maybe?). Basically if there's an "x/X" or "-" in the file's name, it gets assigned as season the number before the "x" instead of the year. ### Reproduction steps 1. Run TA and download mp4 files 2. If the name of the file contains a number followed by an "x", "X" or "-", then the year is ignored and the number before "x/X/-" becomes the season saved by jellyfin for that particular file 3. This can also be reproduced manually by changing the name of a file which doesn't satisfy the rule above and triggering a "show" level metadata replace scan - the file will be moved from the Season "Year" to Season "any number you placed before x/X/-" in the filename 4. Same behaviour with TA 0.5.7/0.5.8, or plugging version 1.4.2/1.4.3, same issue across jellyfin version 10.10.7/10.11.0 and 10.11.3 ### What is the current _bug_ behavior? Jellyfin seems to incorrectly extract the season (which should be its release year) for TubeArchivist files. No NFOs are involved in the intermediation of data between TA and jellyfin. For example, for the file with the following name rbu7Zu**5**X1zI.mp4, jellyfin incorrectly assigns it Season 5 instead of 2024 when it was published on YT. Inside jellyfin's reported metadata for the file, the release date is 12/10/2024 (which is correct) and it's year is also correct (2024). As someone else on TA's page reported in April, https://github.com/tubearchivist/tubearchivist-jf-plugin/issues/30, this seems to be a naming parsing error in Jellyfin when processing filenames (some sort of regex-based exception maybe?). Basically if there's an "x/X" or "-" in the file's name, it gets assigned as season the number before the "x" instead of the year. ### What is the expected _correct_ behavior? Release year of the mp4 should be the Season number for the specific file. ### Jellyfin Server version 10.11.3 ### Specify commit id _No response_ ### Specify unstable release number _No response_ ### Specify version number _No response_ ### Specify the build version 10.11.3 ### Environment ```markdown - OS: UGOS Pro - Linux Kernel: Linux 6.12.30 - Virtualization: Docker - Clients: - - Browser: - - FFmpeg Version: - - Playback Method: - - Hardware Acceleration: - - GPU Model: - - Plugins: TA 1.4.3 - Reverse Proxy: - - Base URL: - - Networking: - - Jellyfin Data Storage: - - Media Storage: - - External Integrations: - ``` ### Jellyfin logs ```shell No relevant logs are produced. Jellyfin thinks is parsing the files correctly so no relevant logs are generated. ``` ### FFmpeg logs ```shell ``` ### Client / Browser logs _No response_ ### Relevant screenshots or videos _No response_ ### Additional information This seems to be related to https://github.com/jellyfin/jellyfin/issues/13197, but in my current configuration of TA, there are no NFO objects involved, the plugin should get the metadata directly from TA's DB.
OVERLORD added the bug label 2026-02-07 05:25:34 +03:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
EFjellyfin.db
area:database
awaiting-feedback
backend
blocked
breaking change: web api
bug
build
ci
confirmed
discussion needed
dotnet future
downstream
duplicate
enhancement
feature
future
github-actions
good first issue
hdr
help wanted
invalid
investigation
librarydb
live-tv
lyrics
media playback
music
needs testing
nuget
performance
platform
pull-request
Mirrored from GitHub Pull Request
 question
regression
release critical
requires-web
roadmap
security
security
stale
support
syncplay
ui & ux
upstream
wontfix
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/jellyfin#7824
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?