Is it possible to have a naming convention that supports both Plex and Jellyfin/Emby?

[obi]

I've read the support sites of both as well as the topics here. Is it possible to have a naming scheme that would work with both?

- Plex suggests curly braces like {tmdb-id}, JF/Emby use [tmdb-id]
- there are some differences in naming of extras/trailers etc

Does anyone know if these are strict requirements, or any scheme that would work with all of them?

[rednoah]

If you need one single format that works for Plex / Emby / Jellyfin then I would ask each of these community about supported ID patterns. The docs specify one, but there's a good chance other patterns are supported even if undocumented. FileBot itselfs supports all known patterns. Nothing prevents Plex / Emby / Jellyfin from doing the same.


Alternatively, could auto-generate multiple structures, one for Plex, one for Jellyfin, another one for human browsing via DLNA, etc. Read Re-process previously organized files using local xattr metadata for details.


You CAN have the same file at more than one file paths, and so you can rather instantly create mirror structures with different formats without using disk space:

e.g. mirror file structures for different naming schemes:

Console Output: Select all

$ filebot -rename -r Plex --db xattr --action hardlink --output Kodi --format "{kodi}"
[HARDLINK] from [Plex/Movies/Avatar (2009)/Avatar (2009).mp4] to [Kodi/Movies/Avatar (2009)/Avatar (2009).mp4]
[HARDLINK] from [Plex/TV Shows/Alias/Season 01/Alias - S01E01 - Truth Be Told.mp4] to [Kodi/TV Shows/Alias/Season 1/Alias - 1x01 - Truth Be Told.mp4]
$ filebot -rename -r Plex --db xattr --action hardlink --output Emby --format "{emby}"
[HARDLINK] from [Plex/Movies/Avatar (2009)/Avatar (2009).mp4] to [Emby/Movies/Avatar (2009)/Avatar (2009).mp4]
[HARDLINK] from [Plex/TV Shows/Alias/Season 01/Alias - S01E01 - Truth Be Told.mp4] to [Emby/TV Shows/Alias (2001)/Season 01/Alias (2001) - S01E01 - Truth Be Told.mp4]

We use hardlinks because that will allow us to have 2 or more files that share the same data on disk, thus we can have the same file multiple times at different file paths. We get all the benefits of copying files without any of the disadvantages such as wasting disk space or having to physically copy bits on disk.

[obi]

If you need one single format that works for Plex / Emby / Jellyfin then I would ask each of these community about supported ID patterns. The docs specify one, but there's a good chance other patterns are supported even if undocumented. FileBot itselfs supports all known patterns. Nothing prevents Plex / Emby / Jellyfin from doing the same.


Alternatively, could auto-generate multiple structures, one for Plex, one for Jellyfin, another one for human browsing via DLNA, etc. Read Re-process previously organized files using local xattr metadata for details.


You CAN have the same file at more than one file paths, and so you can rather instantly create mirror structures with different formats without using disk space:

e.g. mirror file structures for different naming schemes:

Console Output: Select all

$ filebot -rename -r Plex --db xattr --action hardlink --output Kodi --format "{kodi}"
[HARDLINK] from [Plex/Movies/Avatar (2009)/Avatar (2009).mp4] to [Kodi/Movies/Avatar (2009)/Avatar (2009).mp4]
[HARDLINK] from [Plex/TV Shows/Alias/Season 01/Alias - S01E01 - Truth Be Told.mp4] to [Kodi/TV Shows/Alias/Season 1/Alias - 1x01 - Truth Be Told.mp4]
$ filebot -rename -r Plex --db xattr --action hardlink --output Emby --format "{emby}"
[HARDLINK] from [Plex/Movies/Avatar (2009)/Avatar (2009).mp4] to [Emby/Movies/Avatar (2009)/Avatar (2009).mp4]
[HARDLINK] from [Plex/TV Shows/Alias/Season 01/Alias - S01E01 - Truth Be Told.mp4] to [Emby/TV Shows/Alias (2001)/Season 01/Alias (2001) - S01E01 - Truth Be Told.mp4]

We use hardlinks because that will allow us to have 2 or more files that share the same data on disk, thus we can have the same file multiple times at different file paths. We get all the benefits of copying files without any of the disadvantages such as wasting disk space or having to physically copy bits on disk.

Ah, uing hardlinks to create a mirror structure, I never thought of that. That sounds like a great idea, thanks.

[rednoah]

Yep, just keep one primary structure, and then generate disposable secondary structures on demand, i.e. whenever the primary structure changes, you just delete all secondary structures and then re-generate them.