Local playlists import results in same release date and cover image for all tracks (ref#8BTLJ4)

What’s happening?

· Something else

How can we help?

· I'm having trouble adding music to my library

Describe the issue

Importing local playlists eg. m3u-files, then all files appears with same release date and cover image. is this a setting i can change but cannot find or is it a bug?

Describe your network setup

problem is independent of network and hw

Roon is Album based. An Album can have only one cover image and only one release date (+ one original release date). According to your screenshot, all the tracks from that Playlist shown are from the same Album – so it is expected that you see the same Album cover image and the same Album release date for all of them.

1 Like

Thanks for replying.
Is there a way for me to change the behaviour?
If I display a playlist from Tidal, then it is showing the right date/year and the right album cover.
In my local files they all have embedded album covers.

What is there to change? Please provide an example.

Again: In your example all the tracks are from the same Album and therefor show the same (the right) album cover and album release date. Create a playlist with tracks from different albums and Roon will show you the various album covers and release dates.

Hi @Bo_Moller,

I’m afraid @BlackJack is correct. The track objects you’ve imported all share common metadata for the Album-related release fields since they were originally imported from the same Album.

You’ll need to import other versions of these tracks to match your desired release taxonomy or edit the metadata outside of Roon to dissociate these tracks from this Compilation album.

Tried to update a shorter local playlist with album title and removed/added the m3u playlist again, and it does not change anything. attached is a screenshot of the metadata tags. am i missing something?

There is no metadata (tag) in a playlist (m3u, pls, …) file. Looks like you put a bunch of tracks in a folder and now expect Roon to interpret them in a way it wasn’t designed to. If this is a bunch of files in a Folder you could just play the folder or if Roon gets fooled and creates a single album, play that. No need for a playlist file. The only reason Roon even imports and shows the playlist is because of your faulty metadata in track 15. Roon is album based. There is no support for individual album cover, album genre, album interpret, … or album release date per track (in a single album) in Roon. Roon usually expects a Folder = Album structure.

If you want to see the result you expect leave the files in their Album / Folder or use other method to make Roon see the tracks as complete albums with only one track available (if you can find one or someone else points out). Using search you may be able to find other threads discussing this mumbojumbo madness approach. I can only see a lot of work and pain going down that route, so I can not support that. Good luck with that approach (and Roon).

1 Like

Thanks for explaining on how Roon deals with this. I will consider how to organize the content.
For some of us (music geeks) it makes sense to have copies of the playlists. As an example - the playlist above contains more than 50 years of music evolution, and for me it requires some of the music to be refactored (compression/normalization/stereo with etc.) by using some mastering tools, so it can be played from a playlist without eg. turning inside out of a speaker due to much compression or bass or missing proper normalization so you can barely hear it.
So for a playlist like this, playback modifications that has to be done manually with mastering tools, that no player can do by itself today (yet), which justifies a separate file/folder and playlist and leaving the original file in the original folder to fit with the original album, and a modified version that fits to the playlist i created.

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.