I just made a persistency test for playlists, and the outcome was a tad worrying...
See if anyone else can reproduce this - I'm using Musicbee 3.0.5918 (with latest MusicBee3_Patched.zip as of 2016/03/16 21:15 UTC+12:00):
- throw a temporary music file (this needs to be deleted later!) somewhere in a library / monitored folder
- add that file to your library (I did a MB restart, it added it to the inbox as expected [neat!], and I send-to library)
- with the file in the library, add it to a playlist (mine are m3u based, as I need to mass export edited playlists afterwards, so this seems to be the only way atm to do so)
- now, with the file added to a playlist, delete that file off disc (or move it, or rename, I assume would work as well)
- restart MB
- upon re-scan it will detect the file missing
- confirm here that you want to remove it from the library
- now look at the playlist where you added it to, in my case it was gone without a trace
I expected that it then would appear as a dead ( ! ) entry in the playlist, but it did not, it was removed without any notice or warning, effectively mutated the content without informing / warning the user.
Can anyone else reproduce this ?