Bugs & Thoughts about Amarok 1.4.4

[Rich]

Niklas Nylund wrote:
> Hi,
> 
> First of all, thank you for the best music player on Linux! I am a  
> longtime lurker on this mailing list and finally got around to write  
> this mail, Amarok is good but it could definitely be better. First  
> off I got a few bugs, if these are unknown maybe someone could give  
> me advice on how to debug them and give you more useful information.  
> Using 1.4.4 (Ubuntu packages) I've found the following,
> 
> 1) Items are not removed from playlist when removed from the collection

they should be marked as unavailable (greyed out). is that happening ?

> 2) The UI is unresponsive when,
> 	- updating collection
> 	- editing tags (in any fashion)

this has been made a background task (but probably after 1.4.4 ?)

> I suppose these actions are taken care of in a "worker thread" but  
> still there are noticeable effects (completely unresponsive UI,  
> equalizer stutters etc) on the UI when you edit tags, update the  
> collection or add files to the collection ("move files to collection"  
> from filetab).
> 
> 3) The filelist does not always refresh after a delete, sometimes I  
> get a blank row and it doesn't disappear before I do a manual refresh
> 
> 4) I got an album in my collection folder that isn't picked up by the  
> collection scanner. Restarting Amarok or rescanning the collection  
> doesn't help. How do I debug this?

what filesystem ? does amarok pick it up if you 'touch' it ? what 
filetype are the files within ?

> 
> 5) It would be nice if Amarok saved the main playlist and other  
> options (especially "Group by" setting in collection browser) every  
> now and then. I never close Amarok, I use it until it crashes and  
> thus also loses my playlist.

main playlist can be automatically saved whenever a track advances by a 
script now. that is not automated because of performance reasons (might 
change if playlists are moved into the db)
...
-- 
  Rich