4 ms·

I have my system centered around a Denon A/V receiver, with a Sony tv (with a single HDMI cable from the Denon being the only cable to it). Everything works mor

I have my system centered around a Denon A/V receiver, with a Sony tv (with a single HDMI cable from the Denon being the only cable to it). Everything works more or less perfect, with the ocassional glitch where the a/v and tv no longer talk to each other (I need to reboot the whole system when this happens). - The tv and cable remote are both able to turn off the off the tv, which will tell the a/v receiver to turn off - Pressing home on the fire stick causes the tv and a/v to turn on - The volume on the tv, cable remote, and denon remote all trigger the volume of the denon to change. The tv and cable remotes do not trigger the denon's volume's "speed up how fast it changes" on the volume (I don't like that feature, so it works out well) Just pressing the button you would expect to work results in the expected action. I imagine adding sound multi-channel would add complexity (it, picking a channel), but that should be orthogonal to the rest of the setup, and be the same level of complexity between wired and not. What kinds of issues did you run into? Edit: To be clear, I'm an a/v newbie, I doubt I'd be able to offer any advice. I was just curious what issues you saw.

tzs 7y ago
I too have a Denon A/V receiver, although probably older than the rest of you (an AVR-1913 bought in 2013). I don't know if the later Denons still have this, but try finding out its IP address on your network (assuming you have put it on your LAN), and then go to that address, port 80, in your browser. Mine has a built-in web server running there that serves up a status and settings site that lets you do most or all of the things you'd normally do via the remote and on-screen menus, which sometimes gets tedious. The web server is very slow, so it is still tedious, but a "twiddle your thumbs" tediousness as opposed to "way to much remote button pressing to navigate" tediousness. They also have some kind of much faster network access, probably still through the web server but without all the GUI stuff which is apparently where the slowness is. They've got an app on the iOS [1] and Google stores that uses this. Did any of you have trouble getting ARC to work? It simply would not work for me, until I finally noticed that the Denon manual very specifically says you have to use a “Standard HDMI cable with Ethernet” or “High Speed HDMI cable with Ethernet” for HDMI. I was using a regular HDMI cable. Switching to one "with Ethernet" made ARC work. This puzzles me. Everything I've been able to find says that for the version of ARC available in 2013 it should not require a special cable. It should work with any HDMI 1.4 cable. A "with Ethernet" cable should only be required for eARC. I don't think eARC was even in the pipeline in 2013, and didn't start showing up on receivers until 2019. I've checked some Denon manual for later models, and they also have the explicit "with Ethernet" requirement. What is going on? [1] https://apps.apple.com/us/app/denon-remote-app/id388608880 https://apps.apple.com/us/app/denon-remote-app/id388608880
- RHSeeger 7y ago
  Arc "just worked" for me, but I was probably using such a cable by default. As far as it's IP address, I don't have it connected to the internet.
- aidenn0 7y ago
  Network remote control is through port 23 (telnet); I hacked up a little remote app with the functions I need most (input select, volume &c.).
  - tzs 7y ago
    Oh, that's neat. For those who want to play with this, Denon documents it in the manuals and downloads section of their site. Go here [1], find the page for your receiver, and look for the document with "protocol" in its name. If they don't have it listed for your receiver, a couple I know have them are AVR-1913 (Rev 8.5.0 of the protocol document) and AVR-X4000 (Rev 10.0.3). I tried it and it worked. echo -ne MVUP\\r | nc denon 23 increased the volume by one notch. The remote app on my phone is able to get a listing showing my favorite stations in the internet radio app of the receiver, and I didn't see offhand how that is done via the telnet interface, so I watched via tcpdump while the app did it, after some difficulty [2]. It turns out that the remote app for my AVR-1913 is not using the telnet interface. It's doing HTTP POST to the receiver's web server. All the ones I saw were to /goform/AppCommand.xml. What it posts is some XML with one or more commands. For example, it posts this periodically to get information: <?xml version="1.0" encoding="utf-8"?> <tx> <cmd id="1">GetAllZonePowerStatus</cmd> <cmd id="1">GetVolumeLevel</cmd> <cmd id="1">GetMuteStatus</cmd> <cmd id="1">GetSourceStatus</cmd> </tx> The response is XML with the root element being <rx>, then one or more <cmd> elements. The number of <cmd> elements in the response seems to be the same as the number in the request, and they contain the response for the corresponding command. Here's what is coming back for the <tx> shown above (formatted a bit nicer): <?xml version="1.0" encoding="utf-8" ?> <rx> <cmd> <zone1>ON</zone1> <zone2>OFF</zone2> </cmd> <cmd> <volume>-40.0</volume> <disptype>RELATIVE</disptype> <dispvalue>-40.0dB</dispvalue> </cmd> <cmd> <mute>off</mute> </cmd> <cmd> <source>SAT/CBL</source> </cmd> </rx> I've only searched briefly, but so far not found any documentation for this. [1] https://usa.denon.com/us/downloads/manuals-and-downloads https://usa.denon.com/us/downloads/manuals-and-downloads [2] I set my switch [3] to mirror the port the receiver is on to my Mac, but was not seeing anything with tcpdump on the Mac. Took me an embarrassingly long time to remember that if you don't explicitly specify the interface to monitor, it monitors them all but not in promiscuous mode, so you only see traffic to/from yourself. [3] TP-Link SG-108E. I highly recommend this or the SG-105E or others in the family. They are unmanaged switches, but they do support port mirroring, some VLAN features, and some QOS features that you normally have to go to an expensive managed switch for. My 108E (8 port) was only $30. The only thing I don't like about it is that the status lights for the ports are in the back, above the connectors, rather than on the front.

tzs 7y ago

I too have a Denon A/V receiver, although probably older than the rest of you (an AVR-1913 bought in 2013). I don't know if the later Denons still have this, but try finding out its IP address on your network (assuming you have put it on your LAN), and then go to that address, port 80, in your browser. Mine has a built-in web server running there that serves up a status and settings site that lets you do most or all of the things you'd normally do via the remote and on-screen menus, which sometimes gets tedious. The web server is very slow, so it is still tedious, but a "twiddle your thumbs" tediousness as opposed to "way to much remote button pressing to navigate" tediousness. They also have some kind of much faster network access, probably still through the web server but without all the GUI stuff which is apparently where the slowness is. They've got an app on the iOS [1] and Google stores that uses this. Did any of you have trouble getting ARC to work? It simply would not work for me, until I finally noticed that the Denon manual very specifically says you have to use a “Standard HDMI cable with Ethernet” or “High Speed HDMI cable with Ethernet” for HDMI. I was using a regular HDMI cable. Switching to one "with Ethernet" made ARC work. This puzzles me. Everything I've been able to find says that for the version of ARC available in 2013 it should not require a special cable. It should work with any HDMI 1.4 cable. A "with Ethernet" cable should only be required for eARC. I don't think eARC was even in the pipeline in 2013, and didn't start showing up on receivers until 2019. I've checked some Denon manual for later models, and they also have the explicit "with Ethernet" requirement. What is going on? [1] https://apps.apple.com/us/app/denon-remote-app/id388608880 https://apps.apple.com/us/app/denon-remote-app/id388608880

RHSeeger 7y ago
Arc "just worked" for me, but I was probably using such a cable by default. As far as it's IP address, I don't have it connected to the internet.
aidenn0 7y ago
Network remote control is through port 23 (telnet); I hacked up a little remote app with the functions I need most (input select, volume &c.).
- tzs 7y ago
  Oh, that's neat. For those who want to play with this, Denon documents it in the manuals and downloads section of their site. Go here [1], find the page for your receiver, and look for the document with "protocol" in its name. If they don't have it listed for your receiver, a couple I know have them are AVR-1913 (Rev 8.5.0 of the protocol document) and AVR-X4000 (Rev 10.0.3). I tried it and it worked. echo -ne MVUP\\r | nc denon 23 increased the volume by one notch. The remote app on my phone is able to get a listing showing my favorite stations in the internet radio app of the receiver, and I didn't see offhand how that is done via the telnet interface, so I watched via tcpdump while the app did it, after some difficulty [2]. It turns out that the remote app for my AVR-1913 is not using the telnet interface. It's doing HTTP POST to the receiver's web server. All the ones I saw were to /goform/AppCommand.xml. What it posts is some XML with one or more commands. For example, it posts this periodically to get information: <?xml version="1.0" encoding="utf-8"?> <tx> <cmd id="1">GetAllZonePowerStatus</cmd> <cmd id="1">GetVolumeLevel</cmd> <cmd id="1">GetMuteStatus</cmd> <cmd id="1">GetSourceStatus</cmd> </tx> The response is XML with the root element being <rx>, then one or more <cmd> elements. The number of <cmd> elements in the response seems to be the same as the number in the request, and they contain the response for the corresponding command. Here's what is coming back for the <tx> shown above (formatted a bit nicer): <?xml version="1.0" encoding="utf-8" ?> <rx> <cmd> <zone1>ON</zone1> <zone2>OFF</zone2> </cmd> <cmd> <volume>-40.0</volume> <disptype>RELATIVE</disptype> <dispvalue>-40.0dB</dispvalue> </cmd> <cmd> <mute>off</mute> </cmd> <cmd> <source>SAT/CBL</source> </cmd> </rx> I've only searched briefly, but so far not found any documentation for this. [1] https://usa.denon.com/us/downloads/manuals-and-downloads https://usa.denon.com/us/downloads/manuals-and-downloads [2] I set my switch [3] to mirror the port the receiver is on to my Mac, but was not seeing anything with tcpdump on the Mac. Took me an embarrassingly long time to remember that if you don't explicitly specify the interface to monitor, it monitors them all but not in promiscuous mode, so you only see traffic to/from yourself. [3] TP-Link SG-108E. I highly recommend this or the SG-105E or others in the family. They are unmanaged switches, but they do support port mirroring, some VLAN features, and some QOS features that you normally have to go to an expensive managed switch for. My 108E (8 port) was only $30. The only thing I don't like about it is that the status lights for the ports are in the back, above the connectors, rather than on the front.