4 votesWalt shared this idea ·
An error occurred while saving the commentWalt commented
My biggest issue with this otherwise excellent software is UI responsiveness, and this user's suggestion really hit the nail on the head for me. I know this thread is old, but I'd still like to chime in. Dan, in response to your question, I think the distinction lies in WHEN the work is performed by bliss. If I approve a suggested change, like a genre update, does bliss immediately go off and work on storing that change and rescanning that album? Or does it file that instruction away for processing in the background and continue to pay attention to me? I might also want to choose new album art, for instance. If I do, I have to wait 30 seconds or more, or I can go off and work on some other album and try to remember the other change I wanted to make, even though this album may no longer show up in the non-compliant queue after the genre fix.
I don't know if James's idea is the perfect solution, but I definitely think he's onto something here. Decoupling the performing of the tasks (by bliss) from the foreground UI would make the user's workflow less dependent upon the time it takes to apply a change, rescan the album, and update the page.
Just to keep things in perspective, I want to mention that bliss is already better than anything I'd hoped for just a few weeks ago. You're doing some great work here, and I'm telling everyone I know about it!