Minimserver TagFormat is not consistent on Lumin App

[rodrigaj]

I recently purchased a Lumin A1 and have set up Minimserver tagFormat to my preferred format of "AlbumArtist, Conductor, Orchestra".

I get consistency on two locations where this tagFormat is used in the Lumin App and on my Lumin A1 screen. However, the top "AlbumArtist, Conductor, Orchestra" string does not follow the tagFormat rule.

@wklie please advise. Am I doing something wrong?

[joeinid]

Welcome to the forum, thank you for joining.

[Phil A]

Welcome! If there are tags on something that I don't like etiher on a download or CD Rip I use MP3Tag to re-tag it - https://www.mp3tag.de/en/index.html

[rodrigaj]

Welcome! If there are tags on something that I don't like etiher on a download or CD Rip I use MP3Tag to re-tag it - https://www.mp3tag.de/en/index.html

That is not the problem.

The problem is the inconsistency of the display after the tagging has been retagged to my personal satisfaction. It is a MinimServer tagFormat issue and how that format is used by Lumin App.

[nicoff]

Welcome! If there are tags on something that I don't like etiher on a download or CD Rip I use MP3Tag to re-tag it - https://www.mp3tag.de/en/index.html

I use MP3TAG too. Highly recommended.

To the OP:what Phil A is trying to say is that the problem could be the tagging software that you are using. You can try out MP3TAG for free and see if that works.

[rodrigaj]

I use MP3TAG too. Highly recommended.

To the OP:what Phil A is trying to say is that the problem could be the tagging software that you are using. You can try out MP3TAG for free and see if that works.

FWIW, I use jRiver and Metadatics for tagging.

@wklie: My specific question is how does Lumin App treat MinimServer
tagFormat AlbumArtist.displayFormat={$albumartist$conductor$ orchestra}

It appears to use the string as expected with the exception of the top line (see my pict in the original post).

I should also mention that I use
tagOption AlbumArtist.reverseName.display, Composer.reverseName.display, Conductor.reverseName.display
if that matters at all. I use these tagOptions because I prefer indexing with LastName, FirstName and display with FirstName, LastName.

All works well, and displays as it should except for the top section of Lumin App.


If this is a question better answered by Simon at Minimserver, please let me know. I did not think it would be so I came here first.

[Phil A]

If one uses JRiver for tagging, it was my understanding (could be wrong or old info) that the tags in JRiver only are good when using JRiver. So that if you go to use the Lumin App those tags may not display.

[rodrigaj]

If one uses JRiver for tagging, it was my understanding (could be wrong or old info) that the tags in JRiver only are good when using JRiver. So that if you go to use the Lumin App those tags may not display.

Thanks, but that information is incorrect, or old, or both. I've been using JRiver since 2013 and I have never seen that behavior. I've used JRiver tagged music (about 2TB worth) with mConnect, Lumin App, Audirvana, Linn Kinsky, and others and never had a problem with the tagging.

Sometimes JRiver doesn't like a special character but it always fails within the JRiver App itself. I also use Metadactics because it is much easier to use when you are doing batch processing. Years ago I tried MP3TAG but stopped using it for a reason I can't recall. It might have been the UI.

Lumin highly recommends that users of their streamers use Minimserver. It seems odd that there isn't a more in depth users guide to understanding the interplay between Lumin App and Minimserver.

I was hoping I could get support from Lumin in understanding how Lumin interprets Minimserver strings in Properties (i.e., tagFormat and tagOption). That was the purpose of this thread. All of my tags are displaying fine; it's the displayFormat Property that I am trying to understand, and that in only one location.

I'll try over at the Minimserver forums.

[wklie]

Lumin app does not care about tagFormat, i.e. not supported. As for the inconsistency, that needs to be looked at later. On app development we've been busy with complying 64-bit Android requirements from Google.

[rodrigaj]

Lumin app does not care about tagFormat, i.e. not supported. As for the inconsistency, that needs to be looked at later. On app development we've been busy with complying 64-bit Android requirements from Google.

Thank you Peter. That is all I needed to know.

[nicoff]

Thank you Peter. That is all I needed to know.

Looks like your whole issue was you tagging app. You should check with Peter if MP3TAG works with Lumin and then you will be all set.

[rodrigaj]

Looks like your whole issue was you tagging app. You should check with Peter if MP3TAG works with Lumin and then you will be all set.

The tagging app has nothing to do with it. I got the information I needed from Peter.

[nicoff]

The tagging app has nothing to do with it. I got the information I needed from Peter.

Glad you got your answer this time. With that kind of attitude you might not get many folks trying to help you in the future. I know I for one won't try. Good luck!

[rodrigaj]

@nicoff

Sorry if I have offended you. I did not mean to. Honestly.

The interaction between Minimserver and Lumin App is an area that I wish to understand better. This is made somewhat difficult because Minimserver is not a part of the Pixel Magic Systems / Lumin family. As such, much of the flexibility that Minimserver offers in its Properties are not supported or partially supported by Lumin App.

That was why I started this thread and that was what Peter responded to.

No offense was intended.

[rodrigaj]

In the interest of closure, Simon Nash over at Minimserver solved the inconsistency. A screenshot of his reply and my followup response: