In the end, all it took was a single perl command to change the paths in
all my playlists. It no longer seems worth the bother of making my
playlists future-proof if it's only going to save me another similar
command whenever that future arrives.
chill wrote:
> Sure, but would that work on a Mac or Windows server? On my Mac mini,
> the paths all start with ///Volumes/Audio. On a Windows system they'd
> all start with a drive letter.
Hmmm, that's true. I've left the world of windows quite some time ago
for file storage and LMS and this
Sure, but would that work on a Mac or Windows server? On my Mac mini,
the paths all start with ///Volumes/Audio. On a Windows system they'd
all start with a drive letter.
chill's Profile: http://forums.slimdevices.com/mem
I solved that issue by making mount points identical :) Whnever I do a
hardware migration my music will always be on /mnt/music and playlists
on /mnt/playlists.
Main System: Touch; Marantz SR-5004 + TMA Premium 905 + TMA Premium 901
+ Teufel Ultima 20 Mk 2 + BK Monolith+ FF + Lenovo T460 + Kodi
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
