I could not find a request or any else about it apart from this string.
It would be fantastic if this is something that you could work on.
UPDATE.
My problem with incorrect album view displays has now more or less been sorted. It looks like all of the odd tracks showing as albums with no artwork (loads of them) appear to have been picked up from my recycle bin on the hard drive where my music library is stored. i emptied the bin, did a re-scan of library and all of the odd files went. The files were generated while I was doing a lot of changes to my music collection while the hard drive was connected to my Win. 10 PC
I would add it to My Music plugin 
Thanks for your help on that, but I fear it will be complicated for you if it’s the first time you develop on Volumio. However I’ll be happy to support and eventually integrate in the feature I will develop for it .
Sound very complicated to a beginner like me, but really looking forward to watching developments on this one.
I’ve been playing with it at it is indeed more challenging that I had expected. I’ve got the UI part working fine but the command handling has me puzzled. It appears the websocket code is designed to call a method on a plugin. This is pretty easy to do and my prototype server code is getting called as expected. Ideally I would have the update done by the musiclibrary.js code however the architecture appears to have the musiclibrary as a core component so I don’t see a way to route the update message to it without altering the websocket implementation.
Alternatively I could have the mpd plugin )for instance) handle this update call. This would mean mpd would write the config file and musiclibrary would read it. But that violates separation of concerns; a big red-flag for me. Also confuses the mpd with the music library and they should be independent. It would seem to me the musiclibrary should really be a plugin, especially if something as fundamental as mpd is.
So, dealing with a lot of scope creep. I’m putting a halt to any further work until I better understand why these components were architected as they are and what the correct approach is.
@michelangelo, any guidance?
I’ve built some code that does this and have been running for a couple of weeks without issue.
I put in pull request to get it into the next dev branch. You can see the some screenshots in the pull request:
github.com/volumio/Volumio2/pull/1656
That looks great. Just what I need. Many thanks for all of the work and time that you have put in.
Any idea on when it will appear as a plugin?
Hi. Any updated news on the plugin?
Sorry, for the late response, have not been doing much work with volumio since I now have it working well for me. The code I wrote makes changes to some for the volumio core code so it’s not a plugin and so far as I can tell cannot be done as a plugin. It will require the change to be integrated into the volumio release by the core team. I did issue a pull request to get this feature integrated but have not seen and evidence of activity yet.
So it’s out of my hands, perhaps @michaelangelo can provide a status update.
Hi.
Yes, I did PM Michaelangelo and he has said that there are still some issues to be dealt with.
Thanks again for your work.