• Login
  • Register
  • Login Register
    Login
    Username/Email:
    Password:
    Or login with a social network below
  • Forum
  • Website
  • GitHub
  • Status
  • Translation
  • Features
  • Team
  • Rules
  • Help
  • Feeds
User Links
  • Login
  • Register
  • Login Register
    Login
    Username/Email:
    Password:
    Or login with a social network below

    Useful Links Forum Website GitHub Status Translation Features Team Rules Help Feeds
    Jellyfin Forum Support Troubleshooting Media Scanning & Identification Incorrect metadata collected from filenames

     
    • 0 Vote(s) - 0 Average

    Incorrect metadata collected from filenames

    When a video filename ends with " - [1904x1040].mp4" Jellyfin assumes the year is 1904 instead of treating it as part of the label
    helamonster
    Offline

    Junior Member

    Posts: 3
    Threads: 1
    Joined: 2024 Sep
    Reputation: 0
    Country:United States
    #1
    2024-09-24, 09:05 PM (This post was last modified: 2024-09-24, 09:10 PM by helamonster.)
    When a video filename ends with " - [1904x1040].mp4" Jellyfin assumes the year is 1904 instead of treating it as part of the label.

    For example, with a directory named:

    "My Movie (1972)"

    And the following video files in that directory:

    "My Movie (1972) - [1080p].mp4"
    "My Movie (1972) - [1904x1040].mp4"

    A metadata scan / library rescan does not work as expected. Instead of the files being treated as different versions of the same movie with different labels, the second file is treated as a second movie with year 1904 and contains no valid movie metadata. In my example, the correct metadata is retrieved for the first file. I am not sure whether that affects this misbehavior or not.

    Jellyfin version: 10.9.10

    Is this a bug? It seems like it.

    Update: This misbehavior does not happen if the labels are not enclosed with brackets, e.g. the filenames are:

    "My Movie (1972) - 1080p.mp4"
    "My Movie (1972) - 1904x1040.mp4"
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,374
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #2
    2024-09-24, 09:41 PM
    I'm having trouble finding the thread I'm thinking about (or maybe it was in our Matrix chat?), but someone else encountered this problem. IIRC, the solution was to only use the vertical resolution in the "version" portion of the file name.

    Something about having two numbers tripping up Jellyfin's file name parser.
    Jellyfin 10.10.7 (Docker)
    Ubuntu 24.04.2 LTS w/HWE
    Intel i3 12100
    Intel Arc A380
    OS drive - SK Hynix P41 1TB
    Storage
        4x WD Red Pro 6TB CMR in RAIDZ1
    [Image: GitHub%20Sponsors-grey?logo=github]
    helamonster
    Offline

    Junior Member

    Posts: 3
    Threads: 1
    Joined: 2024 Sep
    Reputation: 0
    Country:United States
    #3
    2024-09-28, 06:06 AM
    I was able to avoid the problem by doing something similar, but I would consider that a workaround and not an actual solution.

    The way I see it, there must be a bug in the parsing logic. I would imagine that anything within the brackets should not be parsed for the year or anything else since its specifically used as the label.

    Thoughts?
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,374
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #4
    2024-09-28, 04:53 PM
    It is a bug in the parsing logic. The problem is that the parsing logic is a nightmare that few are brave enough to attempt to modify and risk potentially breaking it even further.
    Jellyfin 10.10.7 (Docker)
    Ubuntu 24.04.2 LTS w/HWE
    Intel i3 12100
    Intel Arc A380
    OS drive - SK Hynix P41 1TB
    Storage
        4x WD Red Pro 6TB CMR in RAIDZ1
    [Image: GitHub%20Sponsors-grey?logo=github]
    2
    helamonster
    Offline

    Junior Member

    Posts: 3
    Threads: 1
    Joined: 2024 Sep
    Reputation: 0
    Country:United States
    #5
    2024-10-02, 07:53 AM
    lol, I can relate to that. I'll take a peek at it myself to see if I can help, but no promises.

    Anyone more familiar with the parsing logic want to point me in that direction?
    « Next Oldest | Next Newest »

    Users browsing this thread: 1 Guest(s)


    • View a Printable Version
    • Subscribe to this thread
    Forum Jump:

    Home · Team · Help · Contact
    © Designed by D&D - Powered by MyBB
    L


    Jellyfin

    The Free Software Media System

    Linear Mode
    Threaded Mode