Hi, I'm running from git 2884f9543db17901439a18051ede56b4b5957341, but this has been the same ever since I've been using Picard (several years).

My workflow is something like this:

• Rip CDs to flac with asunder
• Open Picard, open my ripped folder
• Let fpcalc finish the fingerprinting
• Sort out a few bits in the right pane
• Select a few hundred songs in the right pane, and hit Ctrl-S

At this point, the moving (from my "ripped" to my "ordered" folder) and saving starts. My SATA hard disk is active, the CPU barely. top and iotop confirm this. Sadly, Picard slows to a crawl, and if I try to perform an operation in the right pane (on files not being moved / saved), it's a few seconds before I see the results, making it somewhere between frustrating and impossible to work during that time.

It seems that the moving and saving (which I would see as a background activity) meaningfully impinges on the user interface. Is this a feature or bug? Can anything be done to improve it?