Is any body else having the problem that Roon won’t allow you to choose genres?
For example, this is what I see when I open Pink Floyd’s artist page. I don’t remember if I’ve tweaked this one before or if I’m seeing as it was before any edits.
I try to remove a couple of the genres assigned to Pink Floyd that I don’t like: Pop/Rock, mixed media and pyschedelic/garage. All I do is click edit, scroll down to genres and unmark those. This is what I get:
In the Artist Editor we have two separate sections under Genres. The top section, next to the Roon logo, you can see all of the genres that Roon has automatically applied to the artist. Below that, next to the pencil icon, are any genres that have been manually added. See screenshot below for an example:
If you click on one of these genre tags the check mark will disappear and that genre should no longer be applied.
Is “Album Rock” checked in the Artist Editor? If you make changes here and click Save are all of the changes applied correctly? Are you experiencing this with any other artists?
I understand how genres work, at least as far as your explanation goes. But something weird happens at times where unmarking a genre will add other genres for some reason. I’ve seen this a lot with “Pop/Rock” and “Album rock”.
To show continue with my previous example, these are the genres that show in my Pink Floyd’s artist page:
The expected happens: album rock is no longer there.
But unexpected things happen too: “Mixed media” and “Pop/rock” are now showing up
Let me underline that I did not add “mixed media” and “pop/rock”. I merely unchecked “Album rock”
EDIT: To answer the questions at the end of your post. I am applying changes as you explain, but when I unmark specific genres, aside from those being removed, others are added. And yes, I am experiencing this with many other artists. If it helps, I included an example with the Beatles on this thread.
Thanks for the additional information here — I have passed your report over to our technical team for further review. I’ll be sure to update here when I’ve heard back from them.
I wanted to touch base with some good news, we were able to reproduce this behavior and we’ve opened up a bug report with our developers.
While I can’t say for certain when this bug will be fixed, getting things reproduced in-house is a critical first step, and we will keep this thread up to date as the team passes along feedback and work begins to get this resolved. Thanks again for the report!