If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
> So if I understand this correctly, album gain normalization is now used
> permanently, but I can't set it anywhere, can I?
Normalization can be enabled/disabled globally in LMS. That would still
be taken into account. But you can't disable/enable it for TIDAL only.
The following observation: The Tidal files are definitely played with replaygain - however, this behaviour does not change when I switch off the normalisation for the respective player - the volume simply remains the same, i.e. equally quiet ... am I making a mistake in thinking?
I use version 8.3.0-1644324995.exe on Winows 10
The following observation: The Tidal files are definitely played with replaygain - however, this behaviour does not change when I switch off the normalisation for the respective player - the volume simply remains the same, i.e. equally quiet ... am I making a mistake in thinking?
I use version 8.3.0-1644324995.exe on Winows 10
I see the same. I hadn't tried turning replaygain off before but the server log with Tidal set to debug definitely states that replaygain is being applied when player replaygain is disabled.
Sent from my Pixel 3a using Tapatalk
Living Room: Touch or Squeezelite (Pi3B) > Topping E30 > Audiolab 8000A > Monitor Audio S5 + BK200-XLS DF
Bedroom: Radio
Bathroom: Radio
I see the same. I hadn't tried turning replaygain off before but the server log with Tidal set to debug definitely states that replaygain is being applied when player replaygain is disabled.
Sent from my Pixel 3a using Tapatalk
Thanks for the confirmation! Many greetings, Oliver
> The following observation: The Tidal files are definitely played with
> replaygain - however, this behaviour does not change when I switch off
> the normalisation for the respective player - the volume simply remains
> the same, i.e. equally quiet ... am I making a mistake in thinking?
Could you please enable INFO logging for plugin.tidal, then watch the
server.log for statements like "Using replaygain value of x.x for TIDAL
track"?
Michael
"It doesn't work - what shall I do?" - "Please check your server.log and/or scanner.log file!"
(LMS: Settings/Information)
> The following observation: The Tidal files are definitely played with
> replaygain - however, this behaviour does not change when I switch off
> the normalisation for the respective player - the volume simply remains
> the same, i.e. equally quiet ... am I making a mistake in thinking?
Could you please enable INFO logging for plugin.tidal, then watch the
server.log for statements like "Using replaygain value of x.x for TIDAL
track"?
You didn't see my comment. I did that (well debug) and replaygain is mentioned in the log even when it should be disabled.
Sent from my Pixel 3a using Tapatalk
Living Room: Touch or Squeezelite (Pi3B) > Topping E30 > Audiolab 8000A > Monitor Audio S5 + BK200-XLS DF
Bedroom: Radio
Bathroom: Radio
> You didn't see my comment. I did that (well debug) and replaygain is
> mentioned in the log even when it should be disabled.
I'm sorry, yes, didn't see your comment before I posted.
Anybody willing and able to edit a source file?
In Slim/Plugin/WiMP/ProtocolHandler.pm, around line 449 there's a
function "trackGain". Rename it to "trackGainXX" and restart LMS. Then
please test again, with and without replaygain enabled.
Michael
"It doesn't work - what shall I do?" - "Please check your server.log and/or scanner.log file!"
(LMS: Settings/Information)
> You didn't see my comment. I did that (well debug) and replaygain is
> mentioned in the log even when it should be disabled.
I'm sorry, yes, didn't see your comment before I posted.
Anybody willing and able to edit a source file?
In Slim/Plugin/WiMP/ProtocolHandler.pm, around line 449 there's a
function "trackGain". Rename it to "trackGainXX" and restart LMS. Then
please test again, with and without replaygain enabled.
Where would I find that file? I can't find a "slim" folder in raspbian.
Sent from my Pixel 3a using Tapatalk
Living Room: Touch or Squeezelite (Pi3B) > Topping E30 > Audiolab 8000A > Monitor Audio S5 + BK200-XLS DF
Bedroom: Radio
Bathroom: Radio
I made the change and now the volume is noticeably different if Replaygain is enabled but the server log no longer reports Replaygain at all whether on or off.
Sent from my Pixel 3a using Tapatalk
Living Room: Touch or Squeezelite (Pi3B) > Topping E30 > Audiolab 8000A > Monitor Audio S5 + BK200-XLS DF
Bedroom: Radio
Bathroom: Radio
I learned that the trackGain() function was an override which was applied no matter what the setting was. Whereas without the override LMS would use the gain value returned in the metadata - when enabled.
Michael
"It doesn't work - what shall I do?" - "Please check your server.log and/or scanner.log file!"
(LMS: Settings/Information)
I learned that the trackGain() function was an override which was applied no matter what the setting was. Whereas without the override LMS would use the gain value returned in the metadata - when enabled.
Not really. It works but the server log does not report the fact that replaygain is being applied even when it is enabled. Before the change the server log always reported that replaygain was used.
Sent from my Pixel 3a using Tapatalk
Living Room: Touch or Squeezelite (Pi3B) > Topping E30 > Audiolab 8000A > Monitor Audio S5 + BK200-XLS DF
Bedroom: Radio
Bathroom: Radio
> You didn't see my comment. I did that (well debug) and replaygain is
> mentioned in the log even when it should be disabled.
I'm sorry, yes, didn't see your comment before I posted.
Anybody willing and able to edit a source file?
In Slim/Plugin/WiMP/ProtocolHandler.pm, around line 449 there's a
function "trackGain". Rename it to "trackGainXX" and restart LMS. Then
please test again, with and without replaygain enabled.
I have renamed trackGain to trackGainXX ... however, that definitely disabled normalization on Tidal.
I always compare the following two files because they couldn't be more different:
> Not really. It works but the server log does not report the fact that
> replaygain is being applied even when it is enabled. Before the change
> the server log always reported that replaygain was used.
I'm only interested in the audible effect of the change. The logging is
something I can add or remove at will, and it has nothing to do with the
audio output :-).
FWIW: the logging came from that method you renamed. As it's no longer
available under its expected name, it's no longer called by LMS. I've
learned that that method was used to override the replay gain setting -
which you experienced and confirmed as unexpected. By disabling the
override LMS would read the gain value from a track's metadata like with
any other track. Which should give the expected behaviour.
If you can confirm that you now get normalized levels with gain enabled
in LMS, and "standard" volume without it, I can make the code change.
Michael
"It doesn't work - what shall I do?" - "Please check your server.log and/or scanner.log file!"
(LMS: Settings/Information)
I have renamed trackGain to trackGainXX ... however, that definitely disabled normalization on Tidal.
I always compare the following two files because they couldn't be more different:
Are you saying that even with Replaygain enabled you don't hear the difference after the change? That wasn't my experience, I heard the difference but the log didn't report that replaygain was being used.
Sent from my Pixel 3a using Tapatalk
Living Room: Touch or Squeezelite (Pi3B) > Topping E30 > Audiolab 8000A > Monitor Audio S5 + BK200-XLS DF
Bedroom: Radio
Bathroom: Radio
We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, personalize advertising, and to analyze site activity. We may share certain information about our users with our advertising and analytics partners. For additional details, refer to our Privacy Policy.
By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.
Comment