[go: up one dir, main page]

Menu

#301 albumartist is shown as artist

v1.0 (example)
open
nobody
None
5
2022-02-22
2017-03-30
buhtz
No

It looks like that minidlna always use the "albumartist" tag and offer this as "Interpret" for the client. Right?

It means when I connect to minidlna with my client there is "Interpret". But it should be names as "Album Interpret" or "Album Artist".

Discussion

  • buhtz

    buhtz - 2017-03-30

    I checked the database. The "albumartist" tag is stored in the "ARTIST" column of the "DETAILS" table.
    The "artist" tag itself is used in the "CREATOR" column of the "DETAILS" table.

    Interesting. But "CREATOR" is not offered to my client.

    But I have to say that I don't understand the UPnP protocal exactly. So I don't know who (client or server) is repsonsible for what I see on the client menu.

     
  • Shrimpkin

    Shrimpkin - 2017-04-23

    Database names do not have to correspond to the tag names. The client requests and the server responds with the requested info. Although, some clients will do additional processing that can change results. Look online for a pdf file "UPnP-av-ContentDirectory". Get the latest version and read up.

     
  • buhtz

    buhtz - 2017-04-28

    I think I didn't understand you or I wasn't good in formulating my report.

    An mp3-file has two tags %albumartist% and %artist%. But my clients only see %albumartist% which is names as "Interpret". But htat is wrong.
    The "Interpret" is %artist%. The "Album Interpret" ist %albumartist%.
    Both should be offered. But I thinky they are not.

    This worked fine when using e.g. Twonky.

     
  • Shrimpkin

    Shrimpkin - 2017-04-28

    If you are talking about upnp:albumArtist, I don't think it's part of upnp specifications. Check out the "UPnP-av-ContentDirectory" pdf.

     
    👍
    1
  • Maximilian Bräutigam

    The attached patch solves this problem quick and dirty. Simply store creator in metadata and not artist.

     

Log in to post a comment.