does serviio actually send all tag fields for a flac?

[n3mmr]

looking at flac streams with AV MEdia Controller, it seems serviio sends very few tags along.

Is this true, or am I doing something wrong???

Mind you, there could be problems with ill-formed tags and stuff, or the Media Controller app installation could be missing something. I'm open-minded.

[zip]

It sends as many as it has and are part of the UPnP standard. Which ones are you missing?

[n3mmr]

It sends as many as it has and are part of the UPnP standard. Which ones are you missing?

Is there actually a UPnP standard for media tags???

What on eartn for?? Why not just send any tags as name:value pairs... never mind me.

Point me to the standard, please.

[zip]

http://upnp.org/specs/av/UPnP-av-Conten ... ervice.pdf

[n3mmr]

thank you

[n3mmr]

http://upnp.org/specs/av/UPnP-av-ContentDirectory-v1-Service.pdf

Does this actually address the serving/sending of, say, MP3 ID3 tags and FLAC VorbisComments??

[zip]

It includes what upnp elements are available for different content classes, e.g.: upnp:artist, upnp:album, dc:title, etc Internally Serviio parses FLAC/ID3 tags and mapps them to UPnP tags, where appropriate. And then the playback device decides what UPnP tags it will use.

[n3mmr]

It includes what upnp elements are available for different content classes, e.g.: upnp:artist, upnp:album, dc:title, etc Internally Serviio parses FLAC/ID3 tags and mapps them to UPnP tags, where appropriate. And then the playback device decides what UPnP tags it will use.

I suppose that m,eans there is NO way to get all FLAC Vorbiscomments across to the renderer, then?
Or is there some sort of provision for rendering tags that weren't foreseen when UPnP was specified?

I'm just interested in things like a "Now Playing" screen on a Control Point app in an iPod Touch..

I'm not considering the contents browsing.

[zip]

No, only what's in the spec. And as I said, the device even picks which of the provided metadata it will use / show.

[n3mmr]

No, only what's in the spec. And as I said, the device even picks which of the provided metadata it will use / show.

ACTUALLY I have tried to identify what ID3 tags will be sent on down to the rendering device, trying to identify this from that spec paper....

And: I just can't!

There's something I'm missing, or else I need to read one or several more papers.


Or maybe I'm too ......ing old.
Geriatrics, here I come...

[zip]

on page 69 is a table listing all possible properties of a media resource. On page 79 starts a description of various media classes and what properties they can or should use for description.

Actual mapping of e.g. ID3 tags is not there, but obviously we can guess. have a look at your media files with AV Media Controller to see what tags Serviio uses.

[n3mmr]

on page 69 is a table listing all possible properties of a media resource. On page 79 starts a description of various media classes and what properties they can or should use for description.

Actual mapping of e.g. ID3 tags is not there, but obviously we can guess. have a look at your media files with AV Media Controller to see what tags Serviio uses.

OK.

And did you say that there is no mechanism for serving any metadata not listed as possible beforehand?
Nothing like a way to hand off an xml or json stream containing any name:value pairs one might fancy?

[zip]

No, not possible. The client would not even understand those.

[n3mmr]

No, not possible. The client would not even understand those.

Now, THAT could depend on the client..... and, there are two client types: renderers and control point. Such info transfer extensions would only be for the benefit of control point apps.

Never mind.

How about a transcoding-like field-filler spec file, serviio side, to enable a user with a specific need to map tag fields to UPnP fields?

[zip]

How about a transcoding-like field-filler spec file, serviio side, to enable a user with a specific need to map tag fields to UPnP fields?

Sorry, no. If you're missing some fields, let me know and I'll add them if they fit the spec.

[n3mmr]

How about a transcoding-like field-filler spec file, serviio side, to enable a user with a specific need to map tag fields to UPnP fields?

Sorry, no. If you're missing some fields, let me know and I'll add them if they fit the spec.

Is this for lack of time or a design decision?

[zip]

both

[n3mmr]

I'm getting more and more convinced that:

standards claiming to exist to facilitate music listening are invariably designed by people who have no idea what music really is.

Sigh.

[n3mmr]

for a flac file at least, serviio sends the file name incl extension part as the title, even if there is a title tag defined.

[zip]

for a flac file at least, serviio sends the file name incl extension part as the title, even if there is a title tag defined.

Only in the Folder view, right?