Ok, I'll do my best! What I can't understand is how Noise manages libraries, and I think that there must be some bug around there.  I've got 8 songs in an album. The very first time I put 'em in the library, Noise could find 'em all. Now (some days later) it finds just 7 of them, while file browser tells me that the one not-found file stands still (and I can play it launching it directly from there...and curiously in the panel Noise seems to recognise it as a part of that album, since the icon shows the album's cover). But I think that this bug is related to another one: I had a .wav format sogs' album. Noise could not manage that format (for esample, it did not recognise it was an album, also modifying infos...Noise would not save anything). So I tried to convert these songs into mp3 format.  Now Noise can save infos and find the album. But It does not remove from library the .wav files (while they are not a part of my SSD anymore, since I removed them before). I've tried many times to update the library and to remove them manually, but nothing seems to happen. Also, Noise recognize some files too much later (for example, I inserted a new song in my music folder, and I asked Noise to update the library to find it, but it tooks some days to make it understand that the song was in the library...I think an important role was played by the fact that I played that song many times - by the file browser).  So I've encountered some troubles in the way Noise manages the library.   Leaving out the .wav format matter (which is not the problem of this bug notification), I think Noise can't deal well with the library: - it could not update it; - it could not read from it well; - it could not operate on it well. I hope my description is as precise as you need! Thanks :) Il dom, mag 19, 2013 at 2:44 ,Cameron Norman