Naming parity with Plex

[pudding-breeze]

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...

|

|

\/

If the Plex conventions were supported... MUCH better!..

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.

[lady_whiteadder]

I agree this would be helpful for users moving over from Plex. Perhaps as plugin or option that can be enabled on demand only.

There is another point I'd like to add where naming is slightly different - the extra folder names have lower cases for Jellyfin e.g. "featurette" vs. "Featurette" for Plex.

I did move myself recently and solved both naming differences with a little bash scripting on my linux server - moving everything to Jellyfin naming conventions. That can be a tedious task though.

[Mattaton]

YES! This is exactly the problem I'm having. I want to give Jellyfin a go, but I need Plex to function as well. I can't just start renaming all the files.

Someone suggested symlinks named correctly fro Jellyfin and pointing to the Plex-friendly files, but this would take forever to do manually. If there were a plugin or script that could watch the Plex folder and auto-create symlinks in another directory to make Jellyfin happy, that'd be AWESOME.

Otherwise, I think it's a great idea for Jellyfin to embrace, at least as an option, the Plex naming schemes. I think they'd see a lot more users flocking to Jellyfin if they did.

[thornbill]

Threads in this feature request forum should include links to an existing request on features.jellyfin.org.

This area is meant for additional discussion around requests. Thanks!

[pudding-breeze]

Thanks for the advice - I've now posted it to the correct place...
https://features.jellyfin.org/posts/2560...-with-plex

[Yankees4life]

I'll cosign on this as it'll make many people's Plex setup easier to convert to JF if they want to jump ship...and honestly many people are jumping ship and I'm sure no one wants to mess around with the Metadata for their Libraries again...

[Iacov]

+1
would save me a lot of time in my ongoing move from plex to jellyfin