In reference to this thread :
Automatically export playlist to user specific folder
Thank your for showing me the add-on.
I would like to mention this from the addon's tread - Export M3Us/Playlists for Child Nodes 3.5
monkeyfan1970 wrote:nynaevelan wrote:These are being imported by MM because you have this folder being monitored by MM. First why are you exporting the playlists out of MM and then using MM to watch and import them back into the db?? If they are already in the db why do you want them as a part of your monitored folders??
Thanks for your reply.
Why would I want to do that? Simple. I always want to have the latest physical [not really physical ] .m3u version of my playlist in the folder E:/Music/Playlist exported automatically. And I also want MM to watch that playlist folder to load from.
I understand that MM keeps the playlist in it's DB and I also realise how MM treats it's playlists. I don't really like the way it treats music files and playlist files differently in the watch folder. Example : I configure MM to watch E:/Music and E:/Music/Playlist. If there are 10 songs in E:/Music/ MM loads them and if I delete them, the songs also are removed from MM. But for Playlist it is different. I placed 10 playlist in E:/Music/Playlist and MM lists them in "Imported Playlists" sub-node [I am fine with that] but when I delete the playlist from E:/Music/Playlist , the playlist are still listed in the "Imported Playlists" sub-node. I believe that there should be an option for this for users who want playlist not stored in DB permanently. MM also ignores the unique filename/playlist name of .m3u files. It should technically overwrite the playlist with the same name. I will request this in the wish list section. I think if this behavior is implemented, there will not be any duplicates.
Please share your thoughts.
Will it be possible to add an option for MM to handle playlist storing in DB differently. At the moment, MM stores them in DB regardless of them being in the folder or not. The option would be for MM not to store the "imported playlist" permanently. It is treated almost like the way it treats music files. Every time it scans the playlist folder, Ii will load them under the playlist, if it is not there, they will not be loaded. In this way, if the playlist are renamed/modified/deleted they will be listed relative to the E:/Music/Playlist.
If if set "Export M3Us/Playlists for Child Nodes 3.5" to export the playlist automatically to E:/Music/Playlist at shutdown, at launch of MM I will always have the latest version of my playlist without any multiple of multiple duplicates.
There are number of advantages for this behavior. 1. If I clear my DB, I will always have the latest version of playlist to load. 2. If I am on a network, other user of MM will always have the latest version of the playlist loaded. 3. Any who ever creates/modifies are always exported automatically to E:/Music/Playlist and everyone has the same playlist to watch from MM.