We added and removed an implementation that would allow us to get Audyssey (and other) info. This corresponded with all the connection problems so it may get implemented again since it was not the culprit.
Here is the body of a POST that you would send to goform/AppCommand0300.xml
You can find more about these commands in my notes here:
My current understanding is that we call receivers that support this sort of command AVR X 2016 - but receivers made before then do have Audyssey so it would be nice to know if there was an HTTP API for them.
Schema for supporting commands like these (see audyssey.py in main for what is currently supported):
My new library will handle this stuff from the start though fast response is the main goal:
Good point - if we are sending discrete commands then knowing the state is not required.
BTW @ricarva your initial goal of automating dynamic range control is the main reason I got involved in this integration … and it’s been a great 2 years lol!
Seriously though, there is something that confuses me: I refer to Audyssey Dynamic Volume as “DSP dynamic range control” since it is basically a compressor/limiter acting on the signals. Dolby (and others?) add another feature that I call “metadata dynamic range control” that should yield better results when supported. The issue is how Denon handles this - does it prefer metadata if it sees it? There are separate telnet and HTTP API commands for it - Denon calls the metadata version “dyncomp” in HTTP or DCO in telnet. Finally, there is the option to enable/disable loudness management. So three ways and it is confusing - I want the user presented with one simple option!
@samnewman86 true, I don’t necessarily need to know the state to send out the command, but it would be ideal.
@JPHutchins confusing indeed. For my setup, though, I find that fiddling only with DynamicEQ ON/OFF and Dynamic Volume OFF/LOW/MED/HIGH gives me good customization results without messing with any other options.