Questions about Synchronized Playlists, and Relative Paths

[lucidBrot]

I am in the process of migrating away from Google Play Music to a self-hosted solution and was happy to find that BlackPlayer supports the following options (if I understand those correctly). I love the amount of customization!

• Settings > Advanced > Playlist Save Changes To save any changes directly to the filesystem
• Playlist Menu > Synchronized Playlist To load the Playlist from sdcard every time the the files are modified (?) That seems to be working as I understand it.
• Settings > Metadata > Black Player Library Settings > Scan on Launch To notice newly added music files on Launch.

I synchronize a folder Music between my devices, using syncthing and my own script that generated relative playlists. That Music folder also contains these playlist files in m3u format, using relative Paths. Playing them after import works well! However, It seems like modifying a playlist does not modify the m3u file used to import the playlist originally. Hence my first question:

1. How can I enable write-back to the playlist file? Shouldn't the setting "Playlist Save Changes" already have done that? (It seems like this is related to the duplicate issue https://github.com/KodarKooperativet/BlackPlayer/issues/20 )

The FAQ states

Playlists are exported to .m3u format. The absolute paths arecurrently used in the resulting playlist and may not work on other devices than your phone.

2. As long as absolute paths are used, it is effectifely not advisable to modify playlists using BlackPlayer, because it will break usage on my other devices. I would like to help implementing this feature if you think it fits to your vision of BlackPlayer. How can I offer my assistance? I am a developer myself - do you have a repository I could create a pull request to?

For me, it would be sufficient to have a global setting that all songs added to playlists are in relative paths, relative to one user-determined folder.

Please let me know how I can help.

[lucidBrot]

If you for some reason are agains relative paths (2.) I could probably still achieve my goal of syncable playlists by setting up a cron job that turns the absolute paths in the playlists into relative ones. But that will only work if (1.) is given. So if you don't have the time currently to consider relative paths, I'd still very much appreciate an explanation on the behaviour of that setting. I have tested it - when I add a song to a playlist, the m3u file from where I originally imported the playlist remains unmodified. (E.g. PowerAMP handles that differently). Did I misunderstand this setting?