Several features within Roon and Arc are not wanted by me.
Ban
Folders
I ask for votes on the option to hide these for users who don’t want them.
I understand they’re only visible if you access the menus where they are, which I do a lot, but I don’t want them there.
Happy voting
roonlabs has begun adding new entries to menus that have been stable for years. With version 2.0 (build 1455), a new menu item has been added to the bottom of the album labeled “Ban this album” or, for example, “Ban 2 albums”.
Giving the user the ability to alter this (and other menus), like uses can alter many other menus via Settings, would allow users to remove unwanted new “features”.
The new ‘Ban this album’ feature may come in handy, but I use the ‘Edit…’ feature MUCH more often.
The ‘Edit…’ button used to be at the bottom of the dropdown in the Play Screen context menu, but has been replaced by the ‘Ban this album’ button. And now I keep ‘banning’ and subsequently ‘unbanning’ albums every time I just want to edit them.
For the next update, I would appreciate (not ‘demanding’ but simply requesting…) if the ‘Ban this album’ button could please be be moved to the top of the dropdown, above ‘Share’? For me, and maybe for others, that may be a much better position.
@Roon_Moderators possibly merge?
And
A merge of topics would be fine by me. I did see the two posts by @DDPS and @Suedkiez but I was not sure if the option to make the menu structure user-adjustable would be as easy to build. Simply putting the new menu item further away from the ‘Edit…’ button seemed easier.
Also glad it’s not just me who gets confused by the new menu structure 
It’s for Roon to decide anyway, I just wanted to add the context 
Since the “Ban” option is available under the tri-state “Like” (heart) icon in the Album Details view, and the “Like” (heart) icon is already on this menu at the top right corner, it would have been more consistent to make the “Like” (heart) icon on this menu toggle between “normal”, “like”, and “ban”.
See comment and screenshot in my support request here: Change in Album Menu Behavior after Roon Server 2.0 Update (ref#W14QR0) - #5 by ezman
FWIW I personally hate the tri-state because every time I end up banning something when I just wanted to un-favorite it, and going from normal to ban or from favorite to normal takes two clicks.
And because the tri-state can’t be used in a multi-selection (now this would be progress) it takes a lot of clicking just to ban or un-ban a bunch of bonus tracks.
Maybe it’s just me but just sayin‘
For me, there is only Heart/No-Heart the Banned indicator is only viewable there if enacted via drop down menu, so, banning is no longer select-able by just clicking the heart icon.
I suspect the reason is that this is meant to be for both IN and OUT of library content. As such, OUT of library content do not get the heart icon to click. So making banning only available via the menu was trying to standardize options.
The bi-state (!) heart on this menu will like/un-favorite all albums that were selected when the menu was opened. So it could, should, and hopefully would apply whichever state you want to all the selected albums.
Well, that’s a breaking change, or we’re talking about different menus.
Confirmed … it’s a regression or a breaking change. The heart on the album details page used to be tristate and now it isn’t. You can’t ban with this heart icon anymore.
Ditto for the heart near the right side of each track on the album page. No more banning function. Gotta use the three dot menu.
Ditto for the heart beside each track in My Library > Tracks. No more banning function. Gotta use the three dot menu.
Seems like somebody decided the tri-state heart was a bad idea and removed it from everywhere, then added the ban menu item.
@DDPS posted a link to an article on pitfalls to avoid when making UI/UX redesigns.Check it out! Change in Album Menu Behavior after Roon Server 2.0 Update (ref#W14QR0) - #2 by DDPS
I guess we’ll have to remain constantly reminded that we can ban things whenever we open menus going forward.
I don’t have any OUT of library content, so I was not aware that you’re not allowed to like that stuff because there’s no heart icon. Seems like an odd restriction for roonlabs to make for, say, qobuz or tidal albums, to only allow banning but not liking.
Not at all. In order to edit something, there has to be a database entry in your local library to do so. When you add content to your library from a streaming service, that is when a local database entry is created for you to then Like or Edit.
Yeah, I thought so, good!
I meant the old normal/fav/ban tri-state 
, that one was terrible (in UX)
I don’t understand the streaming experience with roon, as mentioned, and unfortunately neither of your responses make sense to me.
What are the IN and OUT that you mentioned with respect to streaming content and local files and being able to edit (like/unfavorite/ban)? Can you explain how the local database of metadata relates to IN and OUT, and streaming versus locally-stored files (which are often referred to as your local database) and how this gives a consistent experience or not?
Thanks,
- Eric
Roon treats in-library content differently. Only what’s in the library has all the Roon features.
Every local file is automatically in the library.
Streaming albums are not - imagine the streaming service content like a store. You pick what you want to add it to your personal library. If an album is favorited in the streaming service, this is equivalent to adding it to the Roon library (and vice versa).
Thanks @carl for merging. Better title as well 
I think Suedkiez gave good comments and link.
Just wanted follow up on this. Your local database is made up of any local files and any streaming content that you have added to your library.
Thanks for the education, @Suedkiez and @Rugby.
I suppose, @Rugby, that you used OUT to mean that you have yet to favorite it on the streaming service, so no download occurs, no local metadata is created, and you can’t ban or favorite it. IN means you’ve favorited it (or somehow otherwise indicated you want to add it to your library) and then the audio data is downloaded to local storage and metadata is created so you could then ban or favorite it if you choose.
It’s not intuitive that streaming content, once added to your library, is downloaded to local storage instead of being streamed on demand.
