Is it possible to force LMS to create playlists that use 'relative'
paths rather than 'absolute' paths?

As a consequence of moving from the Synology NAS LMS 'package' to the
Docker based image I can now not share my playlists with the Synology DS
Audio application. 

On my Synology NAS, music is stored in '/volume1/Music/<artist>'

The LMS Package for Synology would create playlists like:

Code:
--------------------
    #CURTRACK 0
  #EXTM3U
  
#EXTURL:file:///volume1/Music/The%20Angels/Beyond%20Salvation/01%20The%20Angels%20-%20Dogs%20Are%20Talking.mp3
  #EXTINF:205,Dogs Are Talking
  /volume1/Music/The Angels/Beyond Salvation/01 The Angels - Dogs Are 
Talking.mp3
--------------------


These playlists could be used as-is by both LMS and the Synology DS
Audio application.

But, now with the move to the Docker LMS image on the NAS, and the
mapping of /volume1/Music to the container mount of /music, the
playlists now get created as:

Code:
--------------------
    #CURTRACK 0
  #EXTM3U
  
#EXTURL:file:///music/The%20Angels/Beyond%20Salvation/01%20The%20Angels%20-%20Dogs%20Are%20Talking.mp3
  #EXTINF:205,Dogs Are Talking
  /music/The Angels/Beyond Salvation/01 The Angels - Dogs Are Talking.mp3
--------------------



This works OK for LMS (in Docker) - but the native Audio player on the
Synology - DS Audio (which I use for external NAS Music access) can no
longer use these playlists as "/music" doesn't exist on the NAS as it's
the container mount point.
If the playlists are created in relative path format (eg. ../The Angels)
DS Audio all works fine.

Is there a way to force LMS to create playlists using relative paths? 

Thanks.


------------------------------------------------------------------------
kidhazy's Profile: http://forums.slimdevices.com/member.php?userid=42259
View this thread: http://forums.slimdevices.com/showthread.php?t=114064

_______________________________________________
Squeezecenter mailing list
Squeezecenter@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/squeezecenter

Reply via email to