I took the liberty to make some modifications to the parsing code.
So this new version works fine here.
Thanks, I took a quick look, it looks ok. What name and email should I use for the commit (once the genre issue is dealt with) ? (the email doesn't have to be valid, it's mostly a unique identifier)
In manual search the column "Label" should be changed to "Genre", but I can't find the corresponding part of the code.
It's in the line :
label => { name=> ::_p('Record_label',"Label"), storecol=>2, width=>110, },
'Record_label' is a hint/identifier for the translation, as "label" is used for other stuff in gmb.
Of course the 'label' string is used as identifier in a few places, so it could be better to change them as well.
Any reason you replaced labels by genres ?
Question: Would a unfree api lead to licensing problems? There is an api and it seems free to use after registration of developer... . Thought about givin' it a try in order to rewrite the plugin, because for me it's the ultimate killer feature of gmusicbrowser.
The problem with the free api is that it is limited to 3500 request by day :
3.2 Usage Limitations. You must access the Content through the APIs in a manner that requires you to fully refresh each time a call is made for Content. Currently, you are allowed to make up to 3,500 API calls per day in the aggregate, as calculated by Rovi, during the term of this Agreement, with a maximum of five API calls per second in the aggregate, as calculated by Rovi, for each Key issued to you. Rovi may change such usage limits at any time without notice. In addition to its other rights under this Agreement, Rovi may utilize technical measures to prevent overusage and/or stop usage of the Rovi Property at any time.