Twonky Forum

There's a need for a document that shows how the Twonky database derives upnp values from metadata such as ID3.

For example, the "View configuration TwonkyMedia server" document shows upnp:albumArtist, upnp:artist and upnp:author. What ID3 tags do they map to? The "TPE1" tag seems to map to both upnp:albumArtist and upnp:artist - I get the same results returned from both containers in the following view:

<container name='Album Artist' visibility="test" id='music/albumartist' etc....>
<container buildon='upnp:artist' sortcriteria='+dc:title' class='object.container.genre.musicGenre'
createClass='object.item.audioItem.musicTrack'/>
</container>
<container name='Artist' visibility="test" id='music/album etc....>
<container buildon='upnp:albumArtist' sortcriteria='+dc:title' class='object.container.genre.musicGenre'
createClass='object.item.audioItem.musicTrack'/>
</container>

A list of ID3 and WMA tag mapping to upnp database values would be useful.

Investigating ID3 tags further, it seems that....

- upnp:genre maps to TCON. Implements multi-values using "," as separator.
- upnp:author maps to TCOM; but "/" separator not implemented.
- upnp:artist maps to TPE1; but "/" separator not implemented. If TPE1 not present uses TPE2.
- upnp: albumArtist maps to TPE2.

Lack of multi-value support apart from genre (using a non-ID3.org specified seperator) is a serious limitation. When will Twonky support ID3v2.4 I wonder?

John Glasson

+1
Agreed 100%.

me too, want a compatible way to read my itunes tags properly
tms 5.1.3 displays weird values read from the old tags version.

=:-)f