Upcoming moOde 7 series

[bitlab]

Ya, I think kinda rare scenario so what I think I'll do is display the comment tag and if in the future there is demand for having it be an option to display either the comment tag or the albumid part then deal with it at that point.

Some posts agog @TheOldPresbyope states: This assumes that a user isn't already using the comment field for a different purpose.
And here we have that user ;-)

I'm afraid my comment value varies from empty to very multi line comments. 

In advanceof the albumid/comment information final implementation, I did give the current git impl a try:
After adding the comment field to the library cache the load library json increased more then 25% in my case.  Even with a toggle to show or not to show, the loading and memory use will be there. And knowning what is inside my comments I really don't like to see it.

There is and prob will never be a satisfactory solution to handle all cases out of the box. I would prefer that the user could supply only one field (default none) that should be extracted and shown here. If empty no penality for others.

And if the user then really would like to see something usefull here; with Picard or Foobar scripting you can then makeup a new field based one (parts of) multiple other fields.
For example if I would I could go for a combination of the media source, published label and country.

Regards,
Marcel