12-20-2019, 06:37 PM
@waffle
Old vaudeville joke (think the Marx brothers routines, for instance) -
Patient: Doctor, it hurts when I do this.
Doctor: So don't do that.
But seriously, my guess is you are in effect "flooding" the system by holding the volume button down. This might be confusing the routine which decodes the IR-pulses and converts them to commands and/or confusing the code which responds to the commands.
If you look at the code in /var/www/vol.sh you'll see that a number of tests and database operations are done before mpc is invoked. That's necessary to keep the UI and MPD volume settings in sync, provide a memory of current volume setting, etc.
As I said, this is a guess.
Regarding an asymmetry between volume up and volume down, I expect that's because the 10%-step "regulator" is in effect only for volume up. Tim's not available for the time being to explain his coding decisions. I'll hazard another guess that the regulator was introduced so that users didn't inadvertently drive their system to 100 percent volume with consequential physical damages.
As an aside, I see 51 mentions of "volume" in the relnotes.txt file. All sorts of issues and fixes have occurred over the years.
Regards,
Kent
Old vaudeville joke (think the Marx brothers routines, for instance) -
Patient: Doctor, it hurts when I do this.
Doctor: So don't do that.
But seriously, my guess is you are in effect "flooding" the system by holding the volume button down. This might be confusing the routine which decodes the IR-pulses and converts them to commands and/or confusing the code which responds to the commands.
If you look at the code in /var/www/vol.sh you'll see that a number of tests and database operations are done before mpc is invoked. That's necessary to keep the UI and MPD volume settings in sync, provide a memory of current volume setting, etc.
As I said, this is a guess.
Regarding an asymmetry between volume up and volume down, I expect that's because the 10%-step "regulator" is in effect only for volume up. Tim's not available for the time being to explain his coding decisions. I'll hazard another guess that the regulator was introduced so that users didn't inadvertently drive their system to 100 percent volume with consequential physical damages.
As an aside, I see 51 mentions of "volume" in the relnotes.txt file. All sorts of issues and fixes have occurred over the years.
Regards,
Kent
