• 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 Development Feature Requests Naming parity with Plex

     
    • 3 Vote(s) - 4.33 Average

    Naming parity with Plex

    Allowing Plex's naming conventions will improve adoption.
    pudding-breeze
    Offline

    Junior Member

    Posts: 2
    Threads: 1
    Joined: 2023 Jul
    Reputation: 2
    Country:United Kingdom
    #1
    2023-07-19, 10:29 AM
    I'm not suggesting the existing naming conventions are removed, only that Plex's naming conventions be added in as a supported format.

    This would improve adoption and make it easier for Plex users to migrate over to Jellyfin as it would allow the two to run in parallel rather than having to do a hard-change of file naming.

    For example, if I take the way movie editions are handled as "versions";
    • Jellyfin requires the file name to match the folder name, but with a [space]hyphen[space] separator followed by the version/edition name.  Works fine, but not recognised in Plex.
    • Plex handles this different by dropping the [space]hyphen[space] separate in favour of a curly bracket wrapper with a "tag" inside = {edition-Edition Name Here}.  Again, works fine, but not recognised by Jellyfin.

    I currently do the following, which works for me;

      Movies
      ├───Blade Runner (1982)
      │  ├───Blade Runner (1982) {edition-International Theatrical Cut}.mp4
      │  ├───Blade Runner (1982) {edition-The Final Cut}.mp4
      │  ├───movie.nfo
      │  ├───tmdb.url

    The works for Plex's automated edition matching, and lets me manually "Merge Versions" within Jellyfin (I wish Jellyfin automatically merged based of matching IDs).

    Currently... Not pretty, but functional...
    [Image: 1PUgdwG.png]
    |
    |
    \/
    If the Plex conventions were supported... MUCH better!..
    [Image: UWvhabf.png]


    Having Jellyfin recognise "{edition-...} (as well as the current convention) as a version would make it slick.

    So - keeping things the way Jellyfin wants is fine, but I think adding in support for Plex conventions would greatly improve adoption.  Much like other services - "not-Spotify" services like Navidrome would have better take up if it flat-out copied Spotify as default to easy any move over, but still doing things "their own way" in the configs.
    « Next Oldest | Next Newest »

    Users browsing this thread: 1 Guest(s)


    Messages In This Thread
    Naming parity with Plex - by pudding-breeze - 2023-07-19, 10:29 AM
    RE: Naming parity with Plex - by lady_whiteadder - 2023-09-01, 07:10 AM
    RE: Naming parity with Plex - by Mattaton - 2023-09-21, 11:11 PM
    RE: Naming parity with Plex - by thornbill - 2023-09-22, 02:13 AM
    RE: Naming parity with Plex - by pudding-breeze - 2024-01-28, 10:20 AM
    RE: Naming parity with Plex - by Yankees4life - 2024-01-29, 03:03 PM
    RE: Naming parity with Plex - by Iacov - 2024-02-18, 09:47 PM

    • 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