Post Reply 
Bubbleupnp's work display behavior - suitable minimserver tagging
09-10-2025, 09:59
Post: #1
Bubbleupnp's work display behavior - suitable minimserver tagging
Bubbleupnp increasingly displays "work" data when accessing music albums provided online by qobuz (cf. picture attached) und uses the musical work data as headline when displaying movements of a musical work. I tried to achieve the same Bubbleupnp behavior displaying classical albums sent provided with minimsever. My classical music collection uses a tag "work" for compositions and "title for composition parts, but Buppleupnp does not show any "work" when displaying albums oder applying "show metadata". Is anybody able to tell me, which tagging might be suitable for minimserver to display work data just like qobuz?


Attached File(s) Thumbnail(s)
   
Find all posts by this user
Quote this message in a reply
09-10-2025, 11:04
Post: #2
RE: Bubbleupnp's work display behavior - suitable minimserver tagging
For showing the movements of a piano quartet (etc.) grouped together as a single item when browsing, you need to use the Group tag. If you want to browse your library by musical work name, you should use the Work tag.

The Group and Work tags will often be the same but in some cases they will not (for example, when a work has only a single movement).
Find all posts by this user
Quote this message in a reply
09-10-2025, 13:46
Post: #3
RE: Bubbleupnp's work display behavior - suitable minimserver tagging
(09-10-2025 11:04)simoncn Wrote:  For showing the movements of a piano quartet (etc.) grouped together as a single item when browsing, you need to use the Group tag. If you want to browse your library by musical work name, you should use the Work tag.

The Group and Work tags will often be the same but in some cases they will not (for example, when a work has only a single movement).

Dear Simon, thx a lot for your quick reply. The general meaning and usage of group and work tag is well known, but this is not what I was asking for. Please have a closer look at the picture sent with my first post. Looking at it you see Bubbleupnp displaying work information as headline in front of movements listed in a playlist Furthermore, after activating Bubbleupnp function "show metadata", Bubbleupnp shows "work" metadata in case of several album directly played from my qobuz account. I expected to get the same behavior with minimserver by using the work tag. However, work does not appear with "show metadata" as it does directly accessing qobuz albums (e.g. all newer Deutsche Grammophon albums. for instance album last Schummn album with Maurizio Pollini).
Find all posts by this user
Quote this message in a reply
09-10-2025, 20:38
Post: #4
RE: Bubbleupnp's work display behavior - suitable minimserver tagging
The UPnP protocol doesn't allow a UPnP control point (such as BubbleUPnP) to read Work information from a UPnP server (such as MinimServer). You can browse by Work but nothing more.

Qobuz doesn't use the UPnP protocol and it seems that Qobuz does provide the ability for a Qobuz control point to read Work information from the Qobuz online repository.

I will contact the author of BubbleUPnP to see if any solution for this is possible.
Find all posts by this user
Quote this message in a reply
Yesterday, 09:43 (This post was last modified: Yesterday 09:44 by simbun.)
Post: #5
RE: Bubbleupnp's work display behavior - suitable minimserver tagging
(09-10-2025 13:46)ruckmann Wrote:  However, work does not appear with "show metadata" as it does directly accessing qobuz albums (e.g. all newer Deutsche Grammophon albums. for instance album last Schummn album with Maurizio Pollini).

Whilst the tags that BubbleUPnP presents are limited by the UPnP specification, the contents of the Comment tag are displayed as HTML (under Desc in the metadata window) so you can use/abuse the Booklet/Information files functionality to add your own e.g.

Code:
tagFormat: Comment.displayFormat={$work^Work: ^<br><br>^$conductor^Conductor: ^<br><br>^$Orchestra^Orchestra: ^<br><br>^$performer^Performers: ^^, $comment}

   
Find all posts by this user
Quote this message in a reply
Today, 13:45
Post: #6
RE: Bubbleupnp's work display behavior - suitable minimserver tagging
After discussion with Simon, the next BubbleUPnP update will be able to display these tags in the 'Show metadata' dialog (those that are added to indexTags or itemTags MinimServer properties):

BPM, Conductor, Movement, Lyricist, Lyrics, Mood, Performer, Publisher, Rating, Remixer, Work
Find all posts by this user
Quote this message in a reply
Today, 14:29
Post: #7
RE: Bubbleupnp's work display behavior - suitable minimserver tagging
Many thanks, this looks good. Lyrics seems like it could be quite large, so perhaps best to put this after the others?
Find all posts by this user
Quote this message in a reply
Today, 15:22 (This post was last modified: Today 15:27 by bubbleguuum.)
Post: #8
RE: Bubbleupnp's work display behavior - suitable minimserver tagging
(Today 14:29)simoncn Wrote:  Many thanks, this looks good. Lyrics seems like it could be quite large, so perhaps best to put this after the others?


Yes, Lyrics will be displayed after `Desc.` [Comment tag], which itself could be large.
Other tags are placed where they make most sense [Conductor and Performer with other artists, etc].

As a side note that is not related to MinimServer, most of these tags will also be extracted by BubbleUPnP from the music files it manages ['Local and Cloud' library] using FFmpeg and if present in file [http streams] tags displayed the same in the 'Show metadata' dialog.


EDIT: forum software was tripping with a 403 on stuff within parenthesis and had to use square brackets.
Find all posts by this user
Quote this message in a reply
Today, 16:49
Post: #9
RE: Bubbleupnp's work display behavior - suitable minimserver tagging
The 403 thing is annoying. Disabling this is possible but this would leave the forum open to possible attacks of an unspecified nature (according to my hosting provider).

My workaround when this happens is to put the left parenthesis causing the issue in the Verdana font as described in this post. It looks the same but doesn't trigger the 403.
Find all posts by this user
Quote this message in a reply
Post Reply 


Forum Jump:


User(s) browsing this thread: 1 Guest(s)