This seems better to me, but still not ideal. If I had a say, I would request the following:
In the first overview only show the list of works in the album:
Beethoven Symphony Nr 6
Beethoven Symphony Nr 2
A click on one of the works then shows the content of that work
Beethoven Symphony Nr 6
Movement 1
Movement 2
Movement 3
ā¦
With a back button one can go back to the overview. Any chance something like this could be implemented?
I agree that the metadata display in Mosaic for classical works could be improved, at least in conceptual terms. However Mosaic has physical limitations in various areas . I posted some years ago on the subject when Qobuz added work details at the heading of each piece. Concatenating this with the track details was the solution which is acceptable to me. This area forms a major issue where multiple composers are concerned and where, for just about all music playing apps, it was limited to an artist/album/track format.
Anyway I think it great that you have raised the issue though how this may be treated within Mosaic is difficult to imagine.
As for your more specific request in the final paragraphs of the post you donāt ask for any listing of the artist(s) performing which I see as a major omission. Incidentally as Qobuz give a date of release in the album view page this would e a good addition considering that in classical music the same artist may record different versions of the same piece over the years. However I doubt it could be catered for (?).
The problem with the current layout of dCS Mosaic, it is impossible to distinguish the different movements when the name of the work is long, such as in the example I attached in my OP.
I donāt know what the limitations of Mosaic are, but it seems to me that it should be possible to use a similar display scheme as the Qobuz app or Logitech Media Server use. This would be to list the work as a āchapter headingā and then list the movements below.
Thanks, I had forgotten about that 2019 post. I have difficulties imagining that this is the way airable is forwarding the metadata in 2023. Apps containing Qobuz need to be certified by airable AND Qobuz and I cannot believe that both those parties will certify an app that does not correctly present the metadata to the end user. This would give Qobuz a bad name.
Certainly Qobuz in its API gives access to the two parts of the metadata separately. Otherwise Michael Herger would not be able to do what he does in Logitech Media Server (see screenshot in my OP). Michael has even described to me which API parameters he needs to call to get the metadata parts separately.
I could remotely imagine that airable does not forward the data correctly, but given airableās quasi monopoly as content aggregator, a nudge by dCS to Qobuz should suffice to get airable to fix this.
But maybe this is to small an issue for anyone to care.
@jacobacci@PAR
To Rudi and Pete:
I certainly donāt consider the labeling of classical works to be too small of an issue for anyone to care. Take a look at the thoughtfulness placed into Howard Rogersā considerations of practical detail of what most music players present vs. database normalization to create metadata tags in FLAC files at https://absolutelybaching.com/ or Paul Taylorās long discussion on how SongKong uses MinimServer to tag with the Vorbis/FLAC or the ID3vN labeling. These people really care and are frustrated as well. They are focused on at least providing sense to oneās āin-houseā collection. Regarding whichā¦
My inquiry to dCS is: What fields of MinimServer (recommended by dCS) are presented and searchable by dCS Mosiac. Iām pretty comfortable with MinimServer itself so that I would like to know what information is presented from the fields that are mapped, concatenated, and/or parsed by dCS Mosaic and well as what information in the database is searched so that I may determine how best to manipulate and index the metadata for my on-site, classical music collection when controlling a BartĆ³k streamer.
If there is a reference document providing the fields used and the expected settings of the indexing in MinimServer, please just point me to the reference. My searches did not uncover that information.
I will try to be brief . When using licensed MinimServer you may configure it to display what you wish. Once configured Mosaic displays your amendments as it will reflect the NAS server software. However there are inevitably limitations.
So this is basically not a dCS question but one for MinimServer. Have a read ( or pose a question) at the MinimServer online forum.
You do this configuring via Minim Watch which you download to your computer. This also simplifies rescans.ID3 editing software can also help with purchased downloads if you wish to amend the metadata you were supplied with .
Of course you need to populate the MS fields correctly in the first place and Song Kong may help but good ripping software such as dbpoweramp can be of great help.
Mosaic can only display the data streamed by Qobuz and which fits the Qobuz API used within. So you are stuck with this. The API does not allow for the additional text information that can be found via their own players. However full track information can be found in Mosaic using the three dots.
Thank you for the quick reply. I clearly have misunderstood. So, allow me to ask a my question a different way before closing the thread.
Letās say I have dCS Mosaic on an iPad, a BartĆ³k as my player, and a networked PC with MinimServer and local music files. In the Mosaic app Iāve set the Source to Network.
Starting at the Mosaic Control, I select UPnP so that I may access my local music collection. What do I see? Might you have any screen shots for this scenario similar to those shown in the Mosaic v1.42 release notes for Radio sources? (https://dcsaudio.com/edit/mosaic-_1_4_2)
I know how to populate MinimServerās fields. What I donāt know is what Mosaic will display when using the UPnP connection.
Itās slightly more complicated than that actually Pete, if you recall.
When browsing Qobuz from Mosaic, the catalog/information displayed is streamed from airables not Qobuz directly.
Airable accesses the catalogues via Qobuz APIs, normalises the data returned, and streams them to Mosaic when weāre browsing. Once an album/track is selected, mosaic then instructs the dCS component to directly pull streams down from Qobuzā caching servers (AWS Cloudfront).
Thanks Anup but I was referring to the additional text information that Qobuz provides via its own players. That is distinct from metadata and is not provided via Mosaic. Or airable. For example the magazine, label stories , articles about musical genres etc. Of course you may add associated playlists to your account and Mosaic will play them.
I guess I should add CD booklets to this which are there for many releases when using Qobuz players.
Sticking to Mosaic exclusively does not give you all that a subscription provides. Good restricted to repertoire navigation and listening though.
When Qobuz used to make their API documentation publicly available, one of things they declared was that there were no private APIs exclusively available to only their App. Meaning, all information thatās available via the Qobuz App (including additional text information about artists etc), could technically be available to 3rd party Apps (and partners like airables).
Their exact verbiage was;
We will always refer to the Qobuz for iOS app and Qobuz Desktop app in this document as example of integration. As of today, Qobuz isnāt using any private API methods and you should have access to the exact same tools our apps developers have access to.
However, Iām not sure if this still holds true today. They no longer make their API documentation publicly available so itās hard to verify without signing NDAs.
I remember querying the absence of these items here some years ago and was told by dCS that the API did not cater for their inclusion. Anyway, whatever the reason, they are not there.
So I continue to use a Qobuz desktop player on my laptop to access these additional items. It is also needed to configure oneās account and I find it preferable to Mosaic for building playlists or simply searching.
