In-Progress Emby server/client - ReplayGain or R128 volume normalization support for music

[Luke 43439]

Oh and Emby for macOS as well !

[GreatFlashMan 95]

16 hours ago, Luke said:

Oh and Emby for macOS as well !

Any timescale on Web and Android? 

[Luke 43439]

47 minutes ago, GreatFlashMan said:

Any timescale on Web and Android? 

Web browser audio players don’t natively support it. We can only simulate it with programmatic volume adjustments, but that doesn’t let you go past 1.0. The same currently goes for the player we use on Android, exoplayer. I’ve seen other apps using this same sort of technique.  Without being able to go past 1.0 it’s not a full implementation but it seems like many are ok with it.

[Vicpa 614]

What about Windows? 

[ManiacDC 10]

27 minutes ago, Luke said:

Web browser audio players don’t natively support it. We can only simulate it with programmatic volume adjustments, but that doesn’t let you go past 1.0. The same currently goes for the player we use on Android, exoplayer. I’ve seen other apps using this same sort of technique.  Without being able to go past 1.0 it’s not a full implementation but it seems like many are ok with it.

A lot of CDs still suffer from heavy loudness, so most of the time RG is used to reduce volume rather than raise it.

However, wouldn't it be possible to simulate going past 1.0 by blanket reducing the volume ahead of time? I wouldn't think you'd want this as the default, but you could add an option for it for those who want it. Could also just be slated as a future enhancement if requested.

[Luke 43439]

1 hour ago, Vicpa said:

What about Windows? 

Windows uses the native audio player which I think will fall into the same bucket, but we intend to switch to mpv, so that will help with this.

[Luke 43439]

1 hour ago, ManiacDC said:

A lot of CDs still suffer from heavy loudness, so most of the time RG is used to reduce volume rather than raise it.

However, wouldn't it be possible to simulate going past 1.0 by blanket reducing the volume ahead of time? I wouldn't think you'd want this as the default, but you could add an option for it for those who want it. Could also just be slated as a future enhancement if requested.

In theory that might work. Maybe not on every platform but I’m sure some could do that.

[ryancey 60]

21 hours ago, Luke said:

Hi everyone. This will be in the next updates to Emby for iOS and Emby for Apple TV.  They have players embedded that already support replaygain, which means they can do it without anything being added server-side.

It will need to be enabled in the settings for the app once released. Thanks.

Thanks for those users, but why the silence between end of July "I don't have an ETA" and early october with a full blown release of the feature? 

[ebr 16947]

1 hour ago, ryancey said:

with a full blown release of the feature?

Hi.  It isn't full-blown as discussed here.  It is still limited.  But we are catching up on some backlogged items lately.

[nospotify 201]

Why not just have the max replay gain of all tracks be the max volume peg point (or pick an arbitrary but likely max gain), and use each track's embedded adjustment factor to reduce volume on some tracks as appropriate? Users can rely on the volume settings of whichever device they're using to set the overall volume level wherever the heck they want it, yes?

[ryancey 60]

12 hours ago, ebr said:

Hi.  It isn't full-blown as discussed here.  It is still limited.  But we are catching up on some backlogged items lately.

Okay but it doesn't answer the question really ; I understand you maybe don't want to commit on doing certain things at a certain date, but it just feels weird to come out the blue with the feature just like that. It's been literally 9 years since the request. Can you explain this choice of communication with your users? Even if the answer is "we just pick random issues every day to work on". It's just rude to ignore everyone like that, and some of us are paying customers too.

Edited October 8 by ryancey

[ebr 16947]

6 hours ago, ryancey said:

but it just feels weird to come out the blue with the feature just like that

I'm sorry but I don't understand what you are asking for.  It appears that you are upset because this feature has made it to the top of our backlog - at least in a limited form.

Many times, we don't like implementing things that will only partially work but we decided to go ahead and put this out in limited fashion.  I'm not sure what else to say...

[ryancey 60]

You really don't see how you could improve your communication skills here? Just read this thread which is a perfect case of how to frustrate your userbase. I also suggest you take example on successful project communication strategies like Home Assistant and compare.

We can't see how you work, how you priorize features, what is being worked on, why it's taking time, what can't be done, what's planned in the next release, etc. You just leave your users with vague ready-made answers on every threads ("That's a good idea, thanks" / "It is planned for future updates, thanks").

I'm talking about the most basic relation between a software company and their users and I'm honestly baffled you can't see it.

The fact that the only thing that you wanted to read in my previous reply is that I'm upset *with the feature* would almost be funny if it wasn't sad.

I'm web / Android but I'm glad Apple users finally get to have this, it's been a long time.

[ebr 16947]

11 minutes ago, ryancey said:

I'm talking about the most basic relation between a software company and their users and I'm honestly baffled you can't see it

Hi.  We do not publish our internal plans and I'm not really aware of many software companies who do...  However, you can see what we are currently working on in our beta areas.

This particular item was something we decided could be quickly addressed in a limited fashion so we did.  We are trying to accelerate some of these types of long-standing requests at this time.  I think you should see that within this forum lately.

[GreatFlashMan 95]

On 07/10/2026 at 15:58, Luke said:

Web browser audio players don’t natively support it. We can only simulate it with programmatic volume adjustments, but that doesn’t let you go past 1.0. The same currently goes for the player we use on Android, exoplayer. I’ve seen other apps using this same sort of technique.  Without being able to go past 1.0 it’s not a full implementation but it seems like many are ok with it.

Thanks for the reply.

If could have also been done as server source. Not nit picking, just happy to see the feature making headway, and a 1.0 cap would be a damn fine starter on android and win.

[ManiacDC 10]

3 hours ago, GreatFlashMan said:

If could have also been done as server source.

Pretty sure that would require transcoding.

[GreatFlashMan 95]

20 hours ago, ManiacDC said:

Pretty sure that would require transcoding.

yes, it would.

[Luke 43439]

23 hours ago, GreatFlashMan said:

yes, it would.

I don't see that as a good solution that users would be happy with. If that's what you meant by the "10 minutes of work", then I don't think that is viable.

[GreatFlashMan 95]

1 hour ago, Luke said:

I don't see that as a good solution that users would be happy with. If that's what you meant by the "10 minutes of work", then I don't think that is viable.

no, that's not what i originally was thinking, but could be a server option? more for "across the board" than anything

 

[ManiacDC 10]

1 hour ago, GreatFlashMan said:

no, that's not what i originally was thinking, but could be a server option? more for "across the board" than anything

Yeah an option would be nice there for when the client doesn't work with RG, it could even work with DLNA in that case I think

[Luke 43439]

This is now in the released version of Emby for iOS and Emby for macOS. You'll need to enable ReplayGain in the app settings.