Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[fidelious]

I would love the option to change MC's volume in dB, as an alternative to the current %. Would that be possible in a future build?

[Matt]

If you're trying to calibrate something, you can do precise decibel adjustments with DSP Studio > Parametric Equalizer.

I don't think we'll switch the main program volume away from a 0 to 100 scale.  There are some technical reasons for this, like the fact that system volume slider (as opposed to the internal volume slider) doesn't offer a reliable way to get the volume as a decibel value.

[mojave]

I would love the option to change MC's volume in dB, as an alternative to the current %. Would that be possible in a future build?

There are some technical reasons for this, like the fact that system volume slider (as opposed to the internal volume slider) doesn't offer a reliable way to get the volume as a decibel value.

I would think, but am not sure, that a receiver or preamp is able to do this because it knows its voltage output capabilities. With JRiver, you have any number of soundcards and audio devices being used. Each device will have a different maximum output voltage. JRiver has no idea how to scale the volume to match the output device. When other say they watched a movie at -10 dB, I respond that my system is so powerful that I only listen at 10%. 

[fidelious]

Thank you for your answers.

@Matt, I am not looking for a calibration of the absolute (acoustic) playback level, but (like I have for example in foobar2000) having the option to make MC's internal volume take 1-dB (or 0.5-dB) steps.

From a perceptual point of 'view' (that should probably be 'audition'  ), taking dB steps is more intuitive, since they mean a constant subjective loudness step independent of the absolute level from the loudspeakers. MC's current % steps mean hardly a subjective change when you're playing close to 100% (a 1% step from 100% down to 99% is less than 0.1 dB down), but mean a larger change when you're playing around 10% (going from 10% down to 9% means reducing playback level by about 1 dB).

Also, I do not think that MC's % scale needs to go. I would be perfectly happy with the option of having the % steps (i.e. the change of the Volume % upon issuing the Volume Up / Down commands) depend on the current % value. For example, when playing at 100%, this would make 'Volume Down' result in 89%.

[Matt]

From a perceptual point of 'view' (that should probably be 'audition'  ), taking dB steps is more intuitive, since they mean a constant subjective loudness step independent of the absolute level from the loudspeakers. MC's current % steps mean hardly a subjective change when you're playing close to 100% (a 1% step from 100% down to 99% is less than 0.1 dB down), but mean a larger change when you're playing around 10% (going from 10% down to 9% means reducing playback level by about 1 dB).

The percentage scale used for internal volume is logarithmic.

With internal volume we also know the exact -
Also, I do not think that MC's % scale needs to go. I would be perfectly happy with the option of having the % steps (i.e. the change of the Volume % upon issuing the Volume Up / Down commands) depend on the current % value. For example, when playing at 100%, this would make 'Volume Down' result in 89%.

This will be in a coming build:
Changed: When using internal volume, the volume display will both the volume percentage and also the decibel value.

[fidelious]

The percentage scale used for internal volume is logarithmic.

This will be in a coming build:
Changed: When using internal volume, the volume display will both the volume percentage and also the decibel value.

Thanks again.

Indeed, MC's Internal volume is logarithmic, as I found out after analyzing some output files using the Disk Writer. See the below graph.

• MC's Internal volume converts % to "Applied Scaling dB" (ASdB) using [ASdB] = 10*log2([%]) turquoise line and blue dots
• This is certainly better than what I assumed MC to do, [ASdB] = 20*log10([%]) red line
• My ideal would be for MC to do [ASdB] = [factor]*[%], with [factor] a user-settable constant. This would allow users to choose the sensitivity of the Internal volume green line: [factor] = 0.5
• More practical and acceptable in view of MC's current implementation might be to just introduce this [factor] in the existing Internal volume, i.e.: [ASdB] = [factor]*log2([%]) pink line: [factor] = 25