+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: General Questions (https://forum.jellyfin.org/f-general-questions)
+--- Thread: Playlists and File Paths (/t-playlists-and-file-paths)
Playlists and File Paths - Jracon - 2024-04-07
I am just wondering if it is at all possible to create a playlist without using the absolute file path of the media file. My concern is just with changing media files (Sonarr/Radarr upgrades, retags, etc.) I have not found a way to do this, as wildcards are not supported. Thanks in advance!
RE: Playlists and File Paths - TheDreadPirate - 2024-04-07
I believe you can use relative paths, but they have to be relative to wherever the m3u file is located. Which may or may not work for you.
RE: Playlists and File Paths - rigrig - 2024-04-07
Relative paths work for me, something like this:
<somewhere>/Music
├── Albums
│ └── Artist One
│ └── Some Album
│ └── 1 - First Song.opus
└── Playlists
└── Playlist.m3u
with
Playlist.m3u containing
#EXTM3U
../Albums/Artist One/Some Album/1 - First Song.opus
RE: Playlists and File Paths - Jracon - 2024-04-10
While relative paths do work, they are not exactly what I am looking for. Rather than the other part of the file path, I am actually concerned about the file name. With a new download of a file comes a new release group or set of tags or whatever, and I would like playlists to be persistent through these file changes.
RE: Playlists and File Paths - TheDreadPirate - 2024-04-10
That is not possible with the way that Jellyfin works. Even if Jellyfin allowed the use of UUIDs in playlists (it doesn't AFAIK) I'd imagine that changing the file name would result in a new UUID in this hypothetical scenario.