Explicit Tag Support

[mista_j]

Feature description:

There are a number of “Explicit” tags fields that exist, the “rtng” & “ITUNESADVISORY” fields exist to denote tracks that are explicit.

I think the support to read a tag like this & then show the infamous 🅴 (negative square E) within the UI of the app Along side those tracks would prove useful. This could even be further utilized by denoting tracks that are radio edits or “cleaned up versions” with a 🅲 (negative squared C)

Problem solved:

Quickly Identifying music content that is deemed Explicit

Brought benefits:

Many streaming services implement this feature on their platforms. Bringing this feature to offline music players would be practical & convenient while also keeping those who play offline music from losing a feature by not using a streaming service.

Other application solutions:

 
Some applications grab the rating information for tracks from online sources & these “explicit” denotations can be removed by altering a setting. I think a simpler approach would be to read this information from music metadata. This way there is no need to scrub the web for this information.
 

Additional description and context:

 
rtng in MP4 files is the most widely used tag field for explicit ratings
ITUNESADVISORY is the most known pre existing tag field associated with explicit ratings
Vorbis Comments tags have no official tag field however, creating custom tags in Vorbis Comments has never been an issue

For this reason I think piggybacking off the ITUNESADVISORY or rtng mappings may be the easiest approach.
Field Values could be as follows
0 = Not Explicit / No Rating
1 = Explicit 🅴
2 = Clean / Censored 🅲

The negative square characters could then be added in the UI in front of Track Titles or Artist names as can be seen on other streaming platforms.

I think this could be useful as well but the main focus is on the options above
3 = Instrumental 🅸
 

Screenshots / Mockup:

 

 

 

 

[Tolriq]

@mista_j

ITUNESADVISORY or rtng

The problem is that people abuse and do not really understand those tags.

Typically the official rtng values are:

rtng = 2 → Clean
rtng = 4 → Explicit
rtng = 0 → None

So not the 0/1/2 of the itunes one, and quite a few people use it even differently and mixes the 2.

[mista_j]

I do not disagree, I think much of this comes from a lack of understanding & possibly a lack of consistency amongst varying platforms. To even find what explicit tags exist & how they may function I had to scour the internet…the sea of misinformation.

I think if this were implemented there should firstly be an option for on or off & then to combat the abuse of the tags users simply need documentation on how the app officially handles these tags.

Now if a user is confused…“look at the documentation”

Maybe the user thinks “you’re wrong that’s not how these tags are supposed to work”

…you don’t have to use the feature, it can be turned off, furthermore alterations to rating or explicit tags can be very quickly changed in batch across even massive libraries with very little sweat.

Now if there is merit to their complaint that’s another story, for another day.

If you tell us how it works we can utilize it just like any other tag field