I've recently switched LMS from my old Mac mini to a Raspberry Pi 3B+. None of my playlists work, because the paths are different between the Mac and the Rpi. I'm quite happy working my way through the playlist files to do a global find and replace. But I'm wondering if I can future-proof this a little bit by making the paths relative rather than absolute.
If I have a disk mounted as /mnt/Audio, and on that disk I have a folder called 'Music' and a folder called 'Playlists', then can any playlists in the Playlists folder refer to music files in the Music folder as file:../Music ? I can't seem to make this work, but referring to file:///mnt/Audio/Music works fine. What do those three slashes in front of 'mnt' do, and how many of them should I have before '../Music'?
Supplementary question - if it IS possible to get LMS to *understand* relative paths somehow, is it also possible to make LMS *write* relative paths when it creates or modifies playlists? If not, there wouldn't really be much point in moving my old playlists to relative paths because new playlists would always be absolute, and I'd get in a right mess.
If I have a disk mounted as /mnt/Audio, and on that disk I have a folder called 'Music' and a folder called 'Playlists', then can any playlists in the Playlists folder refer to music files in the Music folder as file:../Music ? I can't seem to make this work, but referring to file:///mnt/Audio/Music works fine. What do those three slashes in front of 'mnt' do, and how many of them should I have before '../Music'?
Supplementary question - if it IS possible to get LMS to *understand* relative paths somehow, is it also possible to make LMS *write* relative paths when it creates or modifies playlists? If not, there wouldn't really be much point in moving my old playlists to relative paths because new playlists would always be absolute, and I'd get in a right mess.