Home of the Squeezebox™ & Transporter® network music players.
Page 208 of 211 FirstFirst ... 108158198206207208209210 ... LastLast
Results 2,071 to 2,080 of 2102
  1. #2071
    Senior Member
    Join Date
    Oct 2014
    Location
    Pittsburgh PA
    Posts
    235
    Quote Originally Posted by rgdawson View Post
    Sam,

    I was secretly hoping one of the Denon AVP/AVR Control developers might reply. That is a very cool plugin. I tried it a long time ago, then again a couple weeks ago, but I did not notice the additional stuff in the screen shot. I was just using the Material Skin interface. Are these new controls available that way?

    I also use DeRemote on iOS devices, where one mounted on the fridge and pretty much dedicated always on. The problem I ran into was that if DeRemote is connected, then the plugin cannot connect (on Pre-2016 AVRs). DeRemote solved that problem for itself, with multiple DeRemote clients on, by a mechanism where the first DeRemote connects to the AVR and subsequent DeRemote clients connect to the first and use it to forward commands to the AVR. But of course, that approach does not work when other clients, such as the plugin, are involved. I began writing a Denon control app, mostly to learn how to do it. And maybe someday creating something as good as DeRemote for Windows/Android clients. (And DeRemote has not been updated since 2015.) The Telnet/CLI interface is pretty straight forward and you can find documentation. But there are other ways to interact with a Denon via http. Those are not documented anywhere (that I know of), but some folks have figured stuff out by monitoring network traffic and running Denon's apps. So I discovered AppCommand.xml (AVR-X models from about ~2013) and AppCommand0300.xml (2016+ models) endpoints, which let you query and command AVRs with an Http Post and sending a properly formatted xml file to these endpoints. And I discovered you can execute the CLI commands (except for queries) with an http Get to a url such as http://xxx.xxx.xxx.xxx//goform/formiPhoneAppDirect.xml?[CliCommand]. This approach does not conflict with telnet on port 23. But there are some things not supported by this approach and I have to resort to Telnet on Port 23 for, and that generally includes some of the more advanced stuff like RefLevOffset, LowFrequencyContainment, and more, depending on the model.

    I might suggest that the Denon AVP/AVR plugin adopt the http approach for On/Off and volume syncing functions in order to avoid the conflicts I mentioned. But I'm guessing you still need to use the TelNet interface for at least some the functions in your screen shot. But at least the basics would always work.

    I'm still learning with my little test app and experimenting with what commands work on what models. (I have a AVR-3313, AVR-X4000, AVR-X6200W, and AVR-X4500H to play with).

    We can take this to another/your forum, is there a forum for the Denon plugin, I can look.

    R Greg Dawson
    Hi, Greg. I'm sorry it took me so long to respond. I've had a lot going on lately, and have also been working on some changes to the client menu processing logic in the Denon plugin that were necessitated by the new Quick Select functionality shown at the bottom of the screen shot I posted previously. The latest version (v4.3) containing those changes was just published on Sunday. To answer some of your questions:

    * The client plugin menu shown on the screen shot is implemented via a Slim::Control::Jive menu and is currently only fully supported for the Squeezer (Android) and iPeng (iOs) client apps. I did not code the menu integration framework and am not sure exactly what has to be done on the client side in order to make use of it. I do know that some work is required and that the Squeezer and iPeng developers cooperated with us in getting it up and running with their clients. For instance, although the basic menu structure works with the Squeeze Ctrl client, some of the menu objects do not function correctly there, among those being the sliders used in the channel volume menu.

    * To use the plugin's audio settings client menu in the apps that support it, it is necessary to turn on the "Enable audio settings menus?" option in the LMS server settings for the plugin under "Player->DENON AVP/AVR Control", which is disabled by default. If you have an Android device, I suggest that you try it out using the Squeezer client app, which is very robust and is also free.

    * Yes, there is a forum for the Denon AVP/AVR plugin (to be distinguished from the Denon Serial plugin, which also uses Telnet on port 23). You can find it here. However, there has not been much activity recently due to the fact that the functionality and reliability of the plugin has been improved over the past few months to the point that there have been no requests for improvements or bug fixes for some time now. ;-)

    Regarding the limitations of using Telnet to communicate with the AVR, our plugin is different than most of the other apps in that we operate in more of an asynchronous transactional manner and do not maintain an open socket connection with the AVR. When we need to communicate with the AVR, we open a TCP connection, issue the command/request, and then return to the main processing loop. When a response is received (or a timeout notification), we immediately close the TCP connection and then take any additional action that may be required. There is also logic to retry or even ignore timeouts in certain known situations where the AVR might not respond to a command that is unsupported for that particular model, etc. An example of an app that does not work that way is the Android app "AVR Remote", which I like to use to control my Denon AVR-3311ci on occasion. However, I have to remember to make sure it's not running on my phone when I'm using the LMS plugin, since the app keeps the telnet connection active at all times, blocking communication from the plugin.

    I was generally aware of the http protocol used by the newer Denon and Marantz receivers but have not felt any need or desire to make use of it, especially since neither my old AVR-3311ci nor my co-developer Chris' even older AVP support it. As a point of interest, I actually became aware of the Squeezelite-X app while adding support in the plugin for the AVR mute on/off command via the cli "mixer muting" command around six months ago. The Android/iOs client developers had agreed to add support in their user interfaces for muting/unmuting but, in the meantime, I had no way of testing with a client until I discovered your app, which helped me greatly in my effort. So, thanks for that!

    Fyi, I just installed the latest version of SLX on my Windows box and activated the Denon control feature. While it didn't discover my AVR, I was able to add it manually and, to my surprise, I was able to power it on and off using the interface. However, the volume controls didn't function. If you ever need any help testing the app's behavior with old pre-http AVR models like mine, just let me know!
    Last edited by SamY; 2021-10-21 at 07:44. Reason: Try to better explain how the plugin works (sigh...)
    Sam

  2. #2072
    Senior Member
    Join Date
    Jan 2016
    Location
    Colorado Springs, CO, USA
    Posts
    987
    Quote Originally Posted by SamY View Post
    ...
    Regarding the limitations of using Telnet to communicate with the AVR, our plugin is different than most of the other apps in that we operate in more of an asynchronous transactional manner and do not maintain an open socket connection with the AVR. When we need to communicate with the AVR, we open a TCP connection, issue the command/request, and then return to the main processing loop. When a response is received (or a timeout notification), we immediately close the TCP connection and then take any additional action that may be required. There is also logic to retry or even ignore timeouts in certain known situations where the AVR might not respond to a command that is unsupported for that particular model, etc. An example of an app that does not work that way is the Android app "AVR Remote", which I like to use to control my Denon AVR-3311ci on occasion. However, I have to remember to make sure it's not running on my phone when I'm using the LMS plugin, since the app keeps the telnet connection active at all times, blocking communication from the plugin.

    I was generally aware of the http protocol used by the newer Denon and Marantz receivers but have not felt any need or desire to make use of it, especially since neither my old AVR-3311ci nor my co-developer Chris' even older AVP support it. As a point of interest, I actually became aware of the Squeezelite-X app while adding support in the plugin for the AVR mute on/off command via the cli "mixer muting" command around six months ago. The Android/iOs client developers had agreed to add support in their user interfaces for muting/unmuting but, in the meantime, I had no way of testing with a client until I discovered your app, which helped me greatly in my effort. So, thanks for that!

    Fyi, I just installed the latest version of SLX on my Windows box and activated the Denon control feature. While it didn't discover my AVR, I was able to add it manually and, to my surprise, I was able to power it on and off using the interface. However, the volume controls didn't function. If you ever need any help testing the app's behavior with old pre-http AVR models like mine, just let me know!
    Ah, so you have a AVR-3311ci. I had one of those but gave it to one of my kids a while back. So my oldest is the AVR-3313, newest AVR-X4500 (and a few in between). I was wondering about what the 3311 might support on the http side of things (again, since Denon never seems to document it). I wasn't expecting the 3311 to support anything on the http-side, so I think my code intentionally excludes discovering AVR's older than the 3313, but I don't have that exclusion when manually adding. I wonder if it supports the AppCommand.xml interface. Are you able to see the 3311's Inputs listed in the combo box in SLX? Does the mute button work?

    Also, please... try on 3311

    Open browser, type the following in address

    http://xx.xx.xx.xx:80/goform/Deviceinfo.xml

    you should get a response of XML text that looks something like this


    <?xml version="1.0" encoding="utf-8"?>
    <Device_Info>
    <DeviceInfoVers>0001</DeviceInfoVers>
    <CommApiVers>0210</CommApiVers>
    <BrandCode>0</BrandCode>
    <ProductCategory>01</ProductCategory>
    <DeliveryCode>01</DeliveryCode>
    <ModelName>*AVR-3313</ModelName>
    <MacAddress>000123456789</MacAddress>
    <UpgradeVersion>00</UpgradeVersion>
    <ReloadDeviceInfo>0</ReloadDeviceInfo>
    <DeviceZones>3</DeviceZones>
    <DeviceCapabilities>
    ...


    I'd like to know what the value is for CommApiVers (assuming it exists) for the 3311. For the 3313 the value is 0210, for example. Maybe 3311 supports more than we thought.

    R Greg Dawson
    Squeezelite-X

  3. #2073
    Senior Member
    Join Date
    Oct 2014
    Location
    Pittsburgh PA
    Posts
    235
    Quote Originally Posted by rgdawson View Post
    Ah, so you have a AVR-3311ci. I had one of those but gave it to one of my kids a while back. So my oldest is the AVR-3313, newest AVR-X4500 (and a few in between). I was wondering about what the 3311 might support on the http side of things (again, since Denon never seems to document it). I wasn't expecting the 3311 to support anything on the http-side, so I think my code intentionally excludes discovering AVR's older than the 3313, but I don't have that exclusion when manually adding. I wonder if it supports the AppCommand.xml interface. Are you able to see the 3311's Inputs listed in the combo box in SLX? Does the mute button work?

    Also, please... try on 3311

    Open browser, type the following in address

    http://xx.xx.xx.xx:80/goform/Deviceinfo.xml

    you should get a response of XML text that looks something like this


    <?xml version="1.0" encoding="utf-8"?>
    <Device_Info>
    <DeviceInfoVers>0001</DeviceInfoVers>
    <CommApiVers>0210</CommApiVers>
    <BrandCode>0</BrandCode>
    <ProductCategory>01</ProductCategory>
    <DeliveryCode>01</DeliveryCode>
    <ModelName>*AVR-3313</ModelName>
    <MacAddress>000123456789</MacAddress>
    <UpgradeVersion>00</UpgradeVersion>
    <ReloadDeviceInfo>0</ReloadDeviceInfo>
    <DeviceZones>3</DeviceZones>
    <DeviceCapabilities>
    ...


    I'd like to know what the value is for CommApiVers (assuming it exists) for the 3311. For the 3313 the value is 0210, for example. Maybe 3311 supports more than we thought.

    R Greg Dawson
    First of all, I get the following error when opening the Denon combo box:

    Name:  Untitled.png
Views: 294
Size:  4.6 KB

    The power on/off buttons work but none of the others, i.e. no muting, volume, or inputs.

    The Deviceinfo command returns the following error:

    Code:
    Access Error: Data follows
    Form Deviceinfo.xml is not defined
    So it looks like I missed the http 'cut' by one model. Btw, I bought my 3311ci new in 2011 and, so far, have not found a compelling reason to replace it. Before that, I had a 3808 that was destroyed in a fire and a 5600 that became a dinosaur with the flood of new tech standards in the first decade of the 2000's.

    Have you had a chance to try the plugin again with the client audio menu activated? I'd be interested in your thoughts on it.
    Sam

  4. #2074
    Senior Member
    Join Date
    Jan 2016
    Location
    Colorado Springs, CO, USA
    Posts
    987
    Quote Originally Posted by SamY View Post
    First of all, I get the following error when opening the Denon combo box:

    Name:  Untitled.png
Views: 294
Size:  4.6 KB

    The power on/off buttons work but none of the others, i.e. no muting, volume, or inputs.

    The Deviceinfo command returns the following error:

    Code:
    Access Error: Data follows
    Form Deviceinfo.xml is not defined
    So it looks like I missed the http 'cut' by one model. Btw, I bought my 3311ci new in 2011 and, so far, have not found a compelling reason to replace it. Before that, I had a 3808 that was destroyed in a fire and a 5600 that became a dinosaur with the flood of new tech standards in the first decade of the 2000's.

    Have you had a chance to try the plugin again with the client audio menu activated? I'd be interested in your thoughts on it.
    Looks that way. Generally the "X" devices are the ones that support the AppCommand.xml interfaces (though my 3313 does as well). Then from 2016 on, the AVRS do not seem to have the single connection limitation on Port 23 and they support additional interfaces (AppCommand0300.xml). The 2016+ models also have very fast response times over http, about 80 times faster than pre-2016 models.

    OK, well I need to add some steps to not allow manual add for 2011 and before, for my case. Anyway, this is helpful info.

    I'm looking forward to trying the latest plugin again this weekend. I do have an Android device with Squeezer on it and I do have iPeng on iOS devices. I'll take a close look. The newer models have sound modes I don't think you support yet and lack certain modes that were present in the older models.

    Thanks for the info!

    R Greg Dawson
    Squeezelite-X

  5. #2075
    Senior Member
    Join Date
    Jan 2016
    Location
    Colorado Springs, CO, USA
    Posts
    987

    Version 2.9.4

    Version 2.9.4

    Changes:

    • Lots of little improvements to the Denon/AVR control widget. It now can be displayed in two sizes. And now it "attaches" to the main form, so that when you drag the main window, the widget moves with it.


    Small version:

    Name:  DeControlWidget_Small.png
Views: 267
Size:  2.6 KB

    Full:

    Name:  DeControlWidget_Full.png
Views: 267
Size:  7.0 KB

    Attached:

    Name:  DeCOntrolWidget_Attached.png
Views: 276
Size:  135.4 KB
    Last edited by rgdawson; 2021-10-26 at 19:49.
    Squeezelite-X

  6. #2076
    Senior Member
    Join Date
    Jan 2016
    Location
    Colorado Springs, CO, USA
    Posts
    987

    Version 2.9.8

    Changes:

    • Redesign and re-implement Denon/Marantz AVR control. Well, I didn't like my implementation of Denon AVR control after all, so I re-implemented it as an internal pop-open panel.
    • Touch interface improvements. One thing I never liked was when using touch and you touch a button, the button would stay highlighted as if the mouse was over it (because actually it is). So I finally sat down and hooked in a gesture architecture so that I could make pushing a button work better and also, so that I could implement a touch and hold repeat (like holding a mouse button down). That way I could use a smaller, easier volume control that would fit better with the new Denon Control panel.
    • Will not let you manually add an older non-compatible Denen AVR. Reminder, this does not work with AVRs older than ~2012.


    So now, if you enable Denon AVR control, pressing the button basically expands the caption bar to reveal the controls. It looks like below.

    Since no one has mentioned it, I'm guessing this is not a particularly mainstream function, so it is not enabled by default. You have to go into Debug/Advanced options to enable it. But I find it valuable as I have 5 Denon AVRs in the house.


    Name:  New DeControl 1.png
Views: 206
Size:  68.5 KB

    Name:  New DeControl 2.jpg
Views: 209
Size:  27.5 KB

    R Greg Dawson
    Last edited by rgdawson; 2021-10-31 at 17:14.
    Squeezelite-X

  7. #2077
    Senior Member
    Join Date
    Oct 2014
    Location
    Pittsburgh PA
    Posts
    235
    Looks great, Greg! Nice job. Makes me want to upgrade my Denon to be able to take advantage of it.
    Sam

  8. #2078
    Senior Member
    Join Date
    Jan 2016
    Location
    Colorado Springs, CO, USA
    Posts
    987
    Quote Originally Posted by SamY View Post
    Looks great, Greg! Nice job. Makes me want to upgrade my Denon to be able to take advantage of it.
    It's time, Sam! I will say, I think very highly of Denon gear (obviously).

    R Greg Dawson
    Squeezelite-X

  9. #2079
    Senior Member
    Join Date
    Sep 2009
    Posts
    189
    Greg,

    Odd one - When "run in background" is on and I close the main window (not minimise) the start menu and taskbar pinned icons do not do anything. I think this was before 2.9.8 but still persists. I have deleted the pinned items and put them back, still the same. I can only open the window from the minimised icon in the bottom left (whatever that is officially called).

    Peter

  10. #2080
    Senior Member
    Join Date
    Jan 2016
    Location
    Colorado Springs, CO, USA
    Posts
    987
    Quote Originally Posted by Peter Galbavy View Post
    Greg,

    Odd one - When "run in background" is on and I close the main window (not minimise) the start menu and taskbar pinned icons do not do anything. I think this was before 2.9.8 but still persists. I have deleted the pinned items and put them back, still the same. I can only open the window from the minimised icon in the bottom left (whatever that is officially called).

    Peter
    Oops. Yah, I renamed the main window and forgot to also change a line of code that invokes an already running instance. So the already running instance is not getting the message. I'll have a fix up as soon as I can.

    R Greg Dawson
    Squeezelite-X

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •