mpogue2
commented
11 months ago - That's something I have felt I needed from time-to-time, too! Maybe there's some UX way I can prevent callers from causing unwanted clipping, either an explicit enabling of this feature (like in Preferences), or coloring the waveform bright red where it clips?
- Question: If we implement this, do we now need to think about scaling the Waveform display when the volume slider is changed? (That's pretty costly...). Is this a "slippery slope", and we need to then also update the waveform display when the EQ sliders are changed (which would show clipping when it was caused, e.g. by pushing the bass control up). More costly...
- a) There's no way to trick it. At load time, the database value is sent to the volume control, which has hard limits of 0 to 100%.
- b) There are probably a couple of alternatives here, to prevent accidentally setting the volume too high. Let me think about this. I'm gonna call this one a Feature Request, since it's an enhancement to the existing GUI.
Gero5
I have calls recorded at different levels
new songs look like this (0 dB is reached throughout the song)
other mostly older recordings like that
I was wondering if a (up to) plus 3dB or so for the song volume controller. At the moment I am pressing the volume of the new songs down, but I would rather have it the other way. I know that there is a risk of clipping and I am personally able to deal with that (maybe not every hapless caller).
BTW: the volume value is missing in the database report Song Play History. a) as a nerdy work around: would it be possible to put a volume value of e.g. 130 % in the database for a song just by sql editing? Would the player play a higher gain then? b) Allow adjusting volume over 100 %. May with a secure mechanism so that by default if I push the volume up it will stay at 100% and I have click something (e. g. pop up message) if I really want to go over. related to #922