Volume Variable not updating

Hi Dave,

Did you get my email yesterday with my TeamViewer id? No worries if you haven't gotten around to looking into it yet - just making sure the email went through and that you have what you need. 

The default Volume up and down commands in the Denon protocol only change volume by a 1/2 db at a time. It would take multiple up and down presses to register a change. I just modified the driver to honor the optional steps command on the volume up and down commands. Now volume up and down commands should register an immediate change.

Install the updated driver and let me know if it solves the issue.

Unfortunately, I think it's made things worse.  Now the volume up and down commands from "Driver Command Testing" don't work at all (they did work previously).  The only command that works is the "0 to 98" volume command when entering a specific number. 

Also, the main issue I reported is still there.  The variable for volume is still the wrong number and does not change when the the volume is successfully changed through the driver (0 to 98 volume command.  

Here's the logs in case it's helpful.  Volume up and volume down commands only show Denon.TX: MV0 with no RX response.  

• 24/03/2024 20:40:09.40 · DEBUG · Server.doCommand - AV|103~Volume~Down from dashboard-fx-0xeh
• 24/03/2024 20:40:09.40 · DEBUG · Denon.doCommand - Cmd=[103~Volume~Down] Client=[dashboard-fx-0xeh]
• 24/03/2024 20:40:09.40 · DEBUG · Denon.TX: (103) - MV0

Here's the log when sending a specific volume number through the driver (does get an RX response from Denon) 

• 24/03/2024 20:35:18.35 · DEBUG · Server.doCommand - AV|103~Volume~60 from dashboard-fx-0xeh
• 24/03/2024 20:35:18.35 · DEBUG · Denon.doCommand - Cmd=[103~Volume~60] Client=[dashboard-fx-0xeh]
• 24/03/2024 20:35:18.35 · DEBUG · Denon.TX: (103) - MV60
• 24/03/2024 20:35:18.35 · DEBUG · Denon.RX - <<MV60>>
• 24/03/2024 20:35:18.35 · DEBUG · Denon.RX - <<MVMAX 98>>

The volume successfully changed to 60 but the variable still shows as 50 (no changes):

• av_103_volume: 50

Thanks again for looking into it,

Neil

Looks like we now need to add a "1" to our volume commands like this, AV|2~Volume~Up~1.  That will move the volume one full db up so we can't move in half dbs anymore.  I think ideally we could still move in half db increments and the volume number variable would reflect the half db steps instead of the full db steps it does today.

Thanks for the suggestion - I was playing around with it this morning and had partial success in adding the "1" to the end of the command.  It does now increase the volume by 1 but with new strange behavior.  It'll add +1 to the volume number from the last time it sent a volume up command rather than whatever the volume is set to at the time the command was issued.  

For example:
- Volume is set to 18 at the start
- Volume~Up~1 command sets the volume to 19
- Volume~55 command sets the volume to 55
- Volume~Up~1 command sets the volume to 20 (rather than to 56 which would be +1 to the current volume)

Here's that example playing out in the logs:

• 25/03/2024 09:06:06.06 · DEBUG · Server.doCommand - AV|103~Volume~Up~1 from dashboard-fx-0xeh
• 25/03/2024 09:06:06.06 · DEBUG · Denon.doCommand - Cmd=[103~Volume~Up~1] Client=[dashboard-fx-0xeh]
• 25/03/2024 09:06:06.06 · DEBUG · Denon.TX: (103) - MV19
• 25/03/2024 09:06:06.06 · DEBUG · Denon.RX - <<MV19>>
• 25/03/2024 09:06:06.06 · DEBUG · Denon.RX - <<MVMAX 66>>
• 25/03/2024 09:06:22.06 · DEBUG · Server.doCommand - AV|103~Volume~55 from dashboard-fx-0xeh
• 25/03/2024 09:06:22.06 · DEBUG · Denon.doCommand - Cmd=[103~Volume~55] Client=[dashboard-fx-0xeh]
• 25/03/2024 09:06:22.06 · DEBUG · Denon.TX: (103) - MV55
• 25/03/2024 09:06:22.06 · DEBUG · Denon.RX - <<MV55>>
• 25/03/2024 09:06:22.06 · DEBUG · Denon.RX - <<MVMAX 75>>
• 25/03/2024 09:06:36.06 · DEBUG · Server.doCommand - AV|103~Volume~Up~1 from dashboard-fx-0xeh
• 25/03/2024 09:06:36.06 · DEBUG · Denon.doCommand - Cmd=[103~Volume~Up~1] Client=[dashboard-fx-0xeh]
• 25/03/2024 09:06:36.06 · DEBUG · Denon.TX: (103) - MV20
• 25/03/2024 09:06:36.06 · DEBUG · Denon.RX - <<MV20>>
• 25/03/2024 09:06:36.06 · DEBUG · Denon.RX - <<MVMAX 66>>

LimeyFK please turn on your teamviewer so I can look at your system. The Denon response Denon.RX - <<MV55>> should be telling the driver that the man zone is at 55. I need to figure out why it doesn't.

There is no need to append ~1 to the end of the volume up and down commands. It will default to 1 if no value is provided. Make sure you are using the latest driver.