Library does not update

[raphial]

When music files are updated or moved into different folders, the Museeks library doesn't reflect the changes and does not update its content :(

I have to reset the library every time.

[martpie]

Updates are not automatically picked (yet). There is no need to reset the library, just re-import the same folder and only new songs will be added :)

[raphial]

Updates are not automatically picked (yet). There is no need to reset the library, just re-import the same folder and only new songs will be added :)

Unfortunately when I add the library, it only duplicates rather than skip/replace any songs :(
That's why I have to reset the library.

Technically the music is mounted from a SAMBA network folder on my network NAS server, but is seen as a regular folder in my /home/user/Music directory. I don't know why it duplicates songs :(

I'm not sure if it helps.. but here is my /etc/fstab entry for that specific server. It has to be mounted differently since it is a network server. (User creds redacted)

//barge-backup.local/business   	    /media/raphial/Business	    cifs	user,password=########,username=USERNAME,domain=WORKGROUP,uid=1000,gid=1000	0	0
/media/raphial/Business/Music	        /home/raphial/Music/Music	none bind,ro 0 0

[raphial]

Did we possibly find a fix for this? :(

It makes updating playlists a real pain....

[martpie]

So there are two things here:

• when your files move is not something we can actually detect and then import the new ones
• better imports (like not duplicating playlists) is definitely something we can do

To not duplicate playlists, we need one bit of data to be stable though, to know when we should replace or create a playlist, either the:

• path of the playlist: my personal favorite. If you reimport a playlist whose path is already imported as a playlist, we recreate and replace the existing playlist
• filename name of the playlist: this would be more resilient to folder changes, but you cannot have two playlist with the same name

In both cases, changes not persisted via export will be lost :/

There is no perfect solution, but as I work towards #753, those are improvements I can easily bring now, because the whole DB will be reset in the next version anyway.