Upgrade on Synology smooth with one small hitch

[magister]

I haven't been around this forum for a long time -- MinimServer just keeps working as it should, so I haven't needed any help. That certainly reflects of the quality of Simon's work! (Also, my stereo was packed up for several months due to house construction.) I was pleased to learn about MinimServer 2. I particularly look forward to being able to configure everything from my tablet without needing my Windows PC with MinimWatch.

I have multiple content directories and have been using MinimStreamer. I'm committed to staying with MinimServer and wanted to get all my music and settings back ASAP, so I downloaded MinimWatch 2 and bought my license in advance. This worked well. I also recorded all my settings from the MinimWatch Properties, which turned out to be a good idea. (I notice that now we can export a profile, so I won't ever need to backup settings manually again -- very nice!)

I encountered only one issue. I had set a tagCustom entry AlbumArtist.displayRole={artist}, Composer.displayRole={artist}‎. This setting was not brought over. I didn't think I could install MinimStreamer until I had activated the license, and of course my settings had been applied earlier when I registered the license in the web page.

This was not a big deal since I had recorded all my settings. I hesitated for a little bit since I could not find tagCustom in MinimWatch 2, but I decided that tagFormat was probably its replacement. MinimWatch did not complain after I pasted in my setting, so I guess I was right.

[simoncn]

The equivalent to tagCustom in MinimServer 2 is upnpCustom. Unlike tagCustom which required this strange default and was hard to explain and understand, the equivalent default for upnpCustom is nothing (empty). For the small number of users who have needed to change the default tagCustom setting to something else, MinimServer 2 automatically migrates this setting to the equivalent setting in upnpCustom. For an example of this, see this post.

[magister]

Thanks, Simon. I looked at the other post you linked. If I have understood correctly, I should leave upnpCustom entry blank, and the default will be the same as what I used for tagCustom (AlbumArtist.displayRole={artist}, Composer.displayRole={artist}) in the previous version. Is that right?

[DavidHB]

(27-04-2020 22:11)magister Wrote:  If I have understood correctly, I should leave upnpCustom entry blank, and the default will be the same as what I used for tagCustom (AlbumArtist.displayRole={artist}, Composer.displayRole={artist}) in the previous version. Is that right?

Sort of. From this help page:

"The upnpCustom property can be used to enable MinimServer to work correctly with some control points that don't implement the UPnP protocol according to commonly accepted industry standards. At the time of writing (February 2020) there are very few such control points still in use. This means that only a very small number of users will need to set this property.

If MinimServer is displaying unexpected information in your control point, please post to the MinimServer forum for advice. It is possible that you might be asked to set this property to a suggested value to see if this solves the problem. In all other cases, you should not set this property,"

David

[simoncn]

(27-04-2020 22:11)magister Wrote:  Thanks, Simon. I looked at the other post you linked. If I have understood correctly, I should leave upnpCustom entry blank, and the default will be the same as what I used for tagCustom (AlbumArtist.displayRole={artist}, Composer.displayRole={artist}) in the previous version. Is that right?

Yes, that is right.