When multiple artists collaborate on a song, Tidal-DL stores artist information in the metadata within the song file, but it saves the list of artists using commas (",") but it should be using semicolons (";") instead. It is standard practice to use semicolons as a delimiter when multiple records are being stored in a metadata field. Using a comma can lead to music software interpreting the stored artist information as the literal name of one artist, instead of as multiple artists.
For example, the song "Hooked On A Feeling" by Blue Swede has the contributing artist "Björn Skifs". Tidal-DL saves the artist information as "Blue Swede, Björn Skifs" where it should be "Blue Swede; Björn Skifs". This causes music players to display the song under the artist "Blue Swede, Björn Skifs" instead of the correct artist ("Blue Swede").
It is of course possible to fix the metatags using software such as Picard or Foobar2000, but it would be nice to not have to fix the issue to begin with.
Which tool
tidal-dl
Version
v2022-08-29
Platform
Linux x64
Describe the bug
When multiple artists collaborate on a song, Tidal-DL stores artist information in the metadata within the song file, but it saves the list of artists using commas (",") but it should be using semicolons (";") instead. It is standard practice to use semicolons as a delimiter when multiple records are being stored in a metadata field. Using a comma can lead to music software interpreting the stored artist information as the literal name of one artist, instead of as multiple artists.
For example, the song "Hooked On A Feeling" by Blue Swede has the contributing artist "Björn Skifs". Tidal-DL saves the artist information as "Blue Swede, Björn Skifs" where it should be "Blue Swede; Björn Skifs". This causes music players to display the song under the artist "Blue Swede, Björn Skifs" instead of the correct artist ("Blue Swede").
It is of course possible to fix the metatags using software such as Picard or Foobar2000, but it would be nice to not have to fix the issue to begin with.
Relevant log output
No response
Add screenshots