Is it possible to have an option to prevent explicit songs being played?
Yeah, just learned this in another post, which of course I canât find.
Double click the heart symbol next to the track you donât like. I will turn grey and never bother you again.
Wait, you mean explicit as in âdirtyâ, so to speak? Sorry, misunderstood.
You were making a feature request, right?
Still you could do it one by one, if you were so inclined.
1 Like
Yes, Iâm putting it up as a feature request. Iâm aware of the heart clicking option but I would prefer a global setting to disable explicit songs with vulgar words to prevent children from listening to it.
As a workaround you can use the âcontains explicit lyricsâ option in the album editor, and hide the album in âalbum optionsâ.
1 Like
Is this album specific setting or can be applied to all albums? I was hoping to select a disabled option and it will applied to all music that contains explicit lyrics including Tidal.
It really depends on whether the albums gets labelled correctly. Some albums carry the âEâ but I often have no idea why as I donât hear anything that would cause that. So, false positives to any automated option is a risk
Personally, I think if it is a real issue in a household then the library owner/parent (i.e. the one who probably purchased the filth in the first place {joke}) should take responsibility and edit the albums or tracks to not play.
I think the problem there is that the tracks can be re-selected to play by anyone, no?
Whatâs really needed, in addition to tagging, is some sort of âparentalâ lock.
The Contains Explicit Lyrics flag is only set for TIDAL material where the labels have marked the album as containing explicit lyrics. We apply this flag verbatim and apply no editorialization whatsoever.
At present we have no reliable means of detecting differences between explicit and clean versions for local material, so you would have to set the flags on album or tracks yourself. In any case, the definition of âexplicitâ is in the eye of the beholder.
In terms of features acting on the flag, thatâs something for us to consider along with the myriad other features requested.
True but if that is really a risk then put all the explicit stuff in a folder and only enable that folder when you explicitly (sorry) want to play it.
What is the risk that your 5 year-old will play March of the Pigs rather than Pepper Pig 
I donât have any rugrats, so in the above example I donât know which is the banned substance.
So I stopped Bjork, Debut to play thatâŚ
Quite a contrast! 
https://i.imgur.com/l3UbSVp.png
Itâs on here and this album is a good example of why expecting Roon to code this for you will never work.
This album is fully identified in Roon and is full of quite potent vocabulary in much of the lyric. Yet it is NOT classified as explicit.
The library owner must take some responsibility and action here.
Great album though 
Iâd vote for this, too. While I donât care about my kids listening to explicit music, I do have outdoor speakers I leverage. Donât want my roon radio dropping f-bombs on my neighborsâ kids.
We do have option in Roon Radio now, but keep in mind that the quality of the filtering will be dependent on the quality of the underlying metadata.
For streaming content, the data will be dependent on the labels and the services, and theyâre usually pretty good but not infallible.
For local files, itâs considerably harder for Roon to know what content is explicit since it will be based on a number of factors (from what fields are populated in the files, how the files were ripped or generated, etc).
1 Like
Whoa. Awesome! Thanks for pointing that out 
1 Like
I came here to make a suggestion for something like this so I can stop getting side eye from my wife. Glad I searched first and found your answer!
1 Like