• Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Displaying multi-value Artist tags with a configurable separator

    Scheduled Pinned Locked Moved
    Feature Suggestions
    1
    1
    15
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • P
      piedivide
      last edited by

      Hi! I'd like to request a configuration option for the separator that's used when displaying multi-value metadata tags. I use MusicBrainz Picard to write multiple values to the Artist tag when a song has multiple contributing artists for my collection, rather than storing them as a single string (for varying reasons). Strawberry currently appears to display these values separated by a space. An example, where you have Artist A and Artist B stored as separate values in the Artist tag, it's displayed as:

      Artist A Artist B

      whereas I think it might be desirable to display as the following options:

      Artist A, Artist B

      Artist A • Artist B (similar to how Navidrome or Symfonium separate multi-value tags)

      It's by no means an issue with functionality but I think it would be a nice QoL improvement, allowing users to customise the separator to their cosmetic preference. This extends beyond the Artist tag and could apply to Genre, Composer, etc.

      It would also contribute to consistency across implementations/applications. Discord's Rich Presence for example uses the parsed metadata strings from Strawberry directly so multi-value tags currently appear separated by a space exactly as they are in Strawberry. Many other music players instead display multi-value tags using a comma or bullet point, so allowing users to change separator characters could open that door for more visual consistency should it be desired.

      Thanks for your consideration!!! Lmk if screenshots or further clarification is needed 🙂

      1 Reply Last reply Reply Quote 0
      • First post
        Last post
      Powered by NodeBB | Contributors