I need MediaMonkey to be faster.
With now 6532 files, MediaMonkey gets slow with certain procedures, like analyzing and so on.
In addition, it would be nice, if MediaMonkey would be more flexible with filenames in different character sets. I have quite some problems with my Hebrew songs or Spanish characters in the filenames.
Thank you! It is still a very nice program!
Speeeeeeed!
Moderator: Gurus
-
Sine Culpa
Speed
Well, you are right, I should have been more precise.
There are three comments I have to make:
1) The library update takes quite some time. That's understandable, but it isn't so nice that MediaMonkey can't be used while it is updating the library. If library update is set on startup (file monitor), I have to wait several minutes after starting the program. I would prefer a solution, where MediaMonkey makes those updates 'in idle' or when processor usage is low as some kind of background process.
2) Same with the volume analysing.
3) When MediaMonkey analyses the volume and gets on a track with, for example, a file name it can't read, it waits for my OK to continue. I think it should just continue with processing the volume and in the end give a list of unreadable tracks.
This was more precise?
Thank you!
There are three comments I have to make:
1) The library update takes quite some time. That's understandable, but it isn't so nice that MediaMonkey can't be used while it is updating the library. If library update is set on startup (file monitor), I have to wait several minutes after starting the program. I would prefer a solution, where MediaMonkey makes those updates 'in idle' or when processor usage is low as some kind of background process.
2) Same with the volume analysing.
3) When MediaMonkey analyses the volume and gets on a track with, for example, a file name it can't read, it waits for my OK to continue. I think it should just continue with processing the volume and in the end give a list of unreadable tracks.
This was more precise?
Thank you!
Ok, that's better. 
1&2) Try options dialog - 'Priority for background tasks', you can even set it to 'idle' which would allow to work easily in foreground. Usually it works well even even for 'normal' prioriry, but it may e.g. depend on the OS used (in my opinion NTs don't manage threads as well as it could).
3) We plan to change reporting of errors for some actions, it will come in some future version.
Jiri
1&2) Try options dialog - 'Priority for background tasks', you can even set it to 'idle' which would allow to work easily in foreground. Usually it works well even even for 'normal' prioriry, but it may e.g. depend on the OS used (in my opinion NTs don't manage threads as well as it could).
3) We plan to change reporting of errors for some actions, it will come in some future version.
Jiri