By-track, by-album or output device DSP settings

Please add this now! At least the ability to trigger a pre defined de emphasis dsp!

Bumping again cuz I really really care about this…

Realy like this sugestion…support it fully

Bumping this… I wish the Roon team would chip in…

1 Like

Bumping this again… I think this is one of those niches that would differentiate Roon tremendously from any other music playback/library management system out there.

Since Roon has track-associated additive data (ie the tags one can add), this is almost a no-brainer I think.

I understand the complexity that might arise from the fact that the current DSP system is probably endpoint-based and applied (ie I imagine there’s no overall DSP applicable to all endpoints currently implementable in the architecture).

But then again, having an overall DSP that is track associated and is applied “first” - rather than trying to convolute possibly two DSPs - would be a solution I would be supportive of.

1 Like

Maybe this and the request for multi-zone DSP are very similar architecturally?

1 Like

I would support such a feature if supported with genre tags. While Roon has a complex systems of genre tags which work for some, I use primarily my own genre and other tags whenever possible. The specific genre tag could be a good method to assign DSP settings on track/album import. Settings such as both pre-emphasis and HDCD settings could be detected on import as well as others. A Roon supplied addition menu to apply user and/or suggested Roon settings could be added. I’m not sure how the settings might conflict with any current user settings–so it would be a solution requiring some thought–but it could still be elegant.

Regarding genre tag specifically, sorting/filtering would be nice, so individuals with large collections could wade through their collections more easily (I have multiple duplicates of albums where only one sounds the best). Using the genre tag and being able to filter the following would be a powerful option:

  • BM: Best Master
  • Classical: Classical
  • Soft Rock: Soft Rock
  • Electronic: Electronic
  • PRE: Pre-Emphasis

The HDCD and pre-emphasis are problems requiring and elegant solution and IMO a software solution vs. having to purchase the every decreasingly available hardware. I suspect the solution would add quite a bit of value to the power (and value) to users with large music collections. I view the Roon software as an open collaboration between a commercial venture and my own music collection data system with the ability of both parties to grow and develop a better music system and listening experience.

So, my 2 cents and first post.


For me that would be a workaround. My corrections are less genre specific. Mostly my corrections depends on the sound of the album. More specific on the quality of the mastering that depends on the quality of the studio equipment and the abilities of the sound engineer. Best example: Alan Parson’s Mastering of Pink Floyd. Sorry for that.



Indeed. As I mentioned elsewhere, I actually find many 80’s pop albums need some bass boost. So I would use the feature to create a profile “80s Pop” and associate that with 80s albums that need a bass boost - not necessarily all of them.

1 Like

Note: in general the number of tags supports by flac is exceeded by user needs–especially for classical music. Long debates have ensued over time. One method of adding information to music files is by using the genre (and album name) tag. See above initial post. Advance users have historically used a wide variety of workarounds to gain additional information about their music files. Roon generally allows users to display and filter a lot of data. File name and genre tag examples for Steely Dan below.

1976 - The Royal Scam [CD][1986 MCA {Roger Nichols uncredited}][JVC Arial, MCAD-37044-U2E 11][JP for US]

BM; Classic Rock; Soft Rock; Pop; CD

1977 - Aja [CD][1985 MCA {Steve Hoffman clone}][JVC Arial, MCAD-37214-T5E 21][JP for US]

BM; Classic Rock; Soft Rock; Pop; CD

Note BM in genre tag is Best Master which I can already filter in Roon–which (I believe) covers your examples.

Understood. However, I am not suggesting any of this EQ info be saved with files at all. Roon does not touch your files, any additional tags you add exist only in the Roon db. So there’s no need to find a place for such EQ or conform to a datatype for such a place since it only exists in the Roon db, and there the Roon team can define whatever they please.

I would also add that this is one of those use cases that fits like a glove to the Roon concept of metadata and would be extremely hard for other software to replicate for many reasons, a few being:
1- They don’t have a parallel database with all of the info - Audirvana/JRiver/etc rely exclusively on file-based data (to my knowledge)
2- If AudioUnits are used to produce EQ (as is the case with Audirvana), then again, controlling the plugin settings dynamically is probably impossible.

The fact that Roon has both a database and a DSP engine built-in is a huge strategic advantage in this regard, and an important differentiator in my opinion.

I do understand that the architecture of DSP looks to be tied to the endpoint in some regard, and this is ok. But creating a higher DSP layer should be possible in my opinion, and would allow for this and some other applications such as DSP to a grouped set.

My suggestion is to use the genre tag set as file metadata by users see (Roon would not alter the user data):

Roon already has the ability to read and filter on the user genre tag. My suggestion is for Roon to use the user tag to apply additional settings for albums and or tracks. My best guess is that it would be possible.

Note my thoughts are ‘out of the box’ but are based on analyzing and developing back-end data and databases for software since PCs came out in the eighties. Just my to cents… I’m not sure of the flexible of the Roon back-end, but as I noted the above it could be an elegant solution for handling both pre-emphasis and HDCDs, since the user tags are read on album import. Once Roon and/or the user can isolate the specific file/album additional information it can define the link to however it wants to use and play the data.

Perhaps you are suggesting a different and valid approach, what I’m suggesting is a paradigm shift allowing users to provide Roon additional atypical data on file import. Pre-emphasis and HDCDs are a low percentage of all CDs made, but represent some of the best mastered albums of the artist pressings available. The Roon users relying mostly on streaming may be less concerned about sound quality. I’m not sure I have anything else to add… :grinning:

This is completely orthogonal to the topic of this thread, which is to allow by-track DSP settings.

You could achieve your goal by selecting with the appropriate tag and then applying what is discussed here, but please don’t sidetrack the topic of this thread.

1 Like

I am curious how replaygain or similar works within Roon as it has to be file-based, and volume leveling is a way of DSP…

1 Like

#currentmood: Like screaming in an anechoic chamber… :frowning:

I sent a direct qestion to Support. May I will get a response! Hope so.

Playing “Home By The Sea” with this parametric eq settings right now…

But I have to remember to turn this on when this album plays, and turn it off after.

Doesn’t the Roon team see the incredible value of the feature I am requesting???


Think of the typical weekly stand up where the roadmap and bugs in hand are discussed. The team have a rating system based on criticality/impact for bugs and value for dev hours along with “essential for roadmap” or “required new feature” etc. They want to hit the big numbers for any feature.
So box sets, mobile access, new streaming services, hardware integration, classical work Vs track are all up in there.
I would posit that he audience for individual DSP settings, given the new less technical majority, is pretty small. So chances of it being high up the queue?

First of all, thank you for your quick response.

I also believe that this is exactly how you described it. Nevertheless, I think it will result in something like a product owner or a business owner or something like a product strategy, which is also, above all, the master of the road map. I’m pretty sure that the feature is at least not relevant for the target group of “music enthusiasts who value sound quality”.

That the feature is not important is certainly an assumption. Have you already validated this assumption based on user research? If so, Miguel and I were just unlucky and you’re right that the feature is probably not relevant for most people.

But if it’s just an assumption, then I think it’s worth checking out. Miguel, what do you think? And of course the other forum members? One could, for example, have a voting essay that all forum members could vote on.

If there is a relevance of this feature, ist has a huge lock–in Effect.

I don’t think the lock-in effect should be underestimated. And yes, I can understand that your product strategy is aimed at attracting more users. But maybe you can add it to your roadmap, so that people like Miguel and me know if such a feature can be expected in the next two years.