DavidBulluss wrote:
> There was a possibility that I had inadvertently affected Z2QS when I
> was having problems with 4.1 beta so have reset Z2QS and it appeared to
> work well.New log 34509 to look at.
>
> Regards, David
It's a little hard to see it in the debug log due to all the YouTube
SamY wrote:
> While it may appear to be running fine with v4.0, that is only because
> the Quick Select is not being retried. It is still timing out after 5
> seconds. Btw, I have no idea what the QZ appearing on your AVR display
> means and could find nothing by googling it. Is there a
DavidBulluss wrote:
> All appears to be running fine in V4.0, as before.
>
> 34508
>
> Regards, David
While it may appear to be running fine with v4.0, that is only because
the Quick Select is not being retried. It is still timing out after 5
seconds. Btw, I have no idea what the QZ
SamY wrote:
> I would like you to go back to v4.0 and run the same power on sequence
> with debug on so I can see if the timeouts are happening there too but
> being compensated for in some way.
All appears to be running fine in V4.0, as before.
34508
Regards, David
SamY wrote:
> It appears that you are running into the same problem as MarSOnEarth,
> where the plugin is going into a Quick Select timeout retry loop after
> powering on successfully. I am working on a code change to prevent the
> retry loop but, as with Mars, I have no explanation for why the
DavidBulluss wrote:
> Synching volume now turned off. Zone 2 tested 34507.
> Whwn turning on all is correct except QZ appears every few seconds on
> screen of AVR. Also, initially adjusting volume on LMS does not control
> the amp until I take the LMS volume very high then the amp vol jumps to
SamY wrote:
> Synching the volume at track changes was only supported for the main
> zone prior to this release, regardless of whether the menu item was
> selected or not. In attempting to add support for it, I overlooked an
> issue that may have been the reason it was not supported before.
DavidBulluss wrote:
> If I untick it then LMS does not control the volume of the amp anymore,
> and of course the vol remains constant track to track.
>
> David
I assume you mean the Plugin checkbox on the player which of course
removes the plugin operations completely for that player.
If
DavidBulluss wrote:
> I have installed the new 4.1 beta and have noticed that when using Zone
> 2 with the setting "enable synching the volume" ticked (as I have had it
> set previously) LMS adjusts the amp volume correctly but the volume
> reverts back to the start up volume approx 3 seconds
Aesculus wrote:
> I have updated the 4.1 beta source files in GitHub with the zone fix
I have installed the new 4.1 beta and have noticed that when using Zone
2 with the setting "enable synching the volume" ticked (as I have had it
set previously) LMS adjusts the amp volume correctly but the
MarSOnEarth wrote:
> Hi Sam,
>
> I'm still on the Material Skin web app, and no, once started, the only
> other interaction with the app was to power the player off.
Okay. I see what is happening with the QS retry loop and I will have to
make some code changes to handle that situation.
SamY wrote:
> Thanks for testing. I'll take a look at the debug. What client app are
> you using? Are you interacting with it at all while the loop is
> happening?
Hi Sam,
I'm still on the Material Skin web app, and no, once started, the only
other interaction with the app was to power the
MarSOnEarth wrote:
> Just tested, and there's a problem. Every few seconds there's an attempt
> to set QS, which errors out on my AVR, and then is re-issued again, and
> again. This is true even after an explicit power off on the player. Yes,
> the power off command is executed, but then the QS
Aesculus wrote:
> I have updated the 4.1 beta source files in GitHub with the zone fix
Just tested, and there's a problem. Every few seconds there's an attempt
to set QS, which errors out on my AVR, and then is re-issued again, and
again. This is true even after an explicit power off on the
I have updated the 4.1 beta source files in GitHub with the zone fix
Chris
Aesculus's Profile: http://forums.slimdevices.com/member.php?userid=14876
View this thread: http://forums.slimdevices.com/showthread.php?t=60114
SamY wrote:
> Okay. It actually has nothing to do with what version of the plugin you
> are using. It does have to do with what firmware your AVR is using
> though. Only the newer models react this way to a PWON command. My
> AVR-3311ci (circa 2009) doesn't exhibit this behavior. Anyway, I have
madpatrick wrote:
> Hi SamY,
>
> First test looks good.
> AVR is switching On/Off with the plugin and Z2 is not On.
>
> Appreciate your swift fix and effort very much !!
> Great Job
Glad to hear that, Patrick. Thanks again for your help.
Sam
SamY wrote:
> Okay. It actually has nothing to do with what version of the plugin you
> are using. It does have to do with what firmware your AVR is using
> though. Only the newer models react this way to a PWON command. My
> AVR-3311ci (circa 2009) doesn't exhibit this behavior. Anyway, I have
al. wrote:
> I'm having the same issue with ZONE 2 powering on sporadically since ver
> 2.3 i think
> I'm attaching debug log using ver 4.0
>
> my denon receiver model is AVR-S740H
> daphile ver. 21.01
Okay. It actually has nothing to do with what version of the plugin you
are using. It does
I'm having the same issue with ZONE 2 powering on sporadically since ver
2.3 i think
I'm attaching debug log using ver 4.0
my denon receiver model is AVR-S740H
daphile ver. 21.01
+---+
|Filename: server.log.zip
Hi. i'm using a Denon AVR X4000 with three zones. I only use the main
zone. When i'm turning on for example the AVR with Ipeng all three zones
become active altough zone 2 and 3 have been switched off.
lalu01's Profile:
pfew... i was already doubting it was only me with the problem.
I was laready looking to switch back to version 2.3 or 3.0 to test.
-
Patrick
madpatrick's Profile: http://forums.slimdevices.com/member.php?userid=4929
SamY wrote:
> It's my opinion that the behavior you are seeing has nothing to do with
> the plugin. I would suggest looking around on the Denon forums for info
> regarding zone behavior. If you're not using Zone 2 at all, you can
> disable it. Here are a couple of things to look at:
>
>
madpatrick wrote:
> LMS version : 8.1.1 - 1610364019 @ Thu Jan 14 06:20:31 CET 2021
> SB touch : Firmware: 8.0.1-r16844
It's my opinion that the behavior you are seeing has nothing to do with
the plugin. I would suggest looking around on the Denon forums for info
regarding zone behavior. If
Aesculus wrote:
> I took a quick pass over it and can find nothing in the logs that
> indicated anything but the main zone was dealt with.
>
> Small note: Here you said Z1 but above you said Z2. But none the less,
> no zone requests in the log.
>
Sorry. Z1 = Z2. I have only 1 zone ;-)
>
>
Aesculus wrote:
> I took a quick pass over it and can find nothing in the logs that
> indicated anything but the main zone was dealt with.
>
> Small note: Here you said Z1 but above you said Z2. But none the less,
> no zone requests in the log.
>
> Here is another test:
>
> Go into
madpatrick wrote:
> I hope the test is helpfull.
> Attached the log file of my test
> 1st : AVR off / LMS On: Z1 was put on
> 2nd : AVR QS3 / LMS on : Z1 Not on
> 3rd : AVR off / LMS On: Z1 was put on
> Z1 put off and AVR off
> 4th : AVR off / LMS On: Z1 was put on
>
> 34463
I
I hope the test is helpfull.
Attached the log file of my test
1st : AVR off / LMS On: Z1 was put on
2nd : AVR QS3 / LMS on : Z1 Not on
3rd : AVR off / LMS On: Z1 was put on
Z1 put off and AVR off
4th : AVR off / LMS On: Z1 was put on
34462
madpatrick wrote:
> Putting the AVR on with the QS button : No Z2
>
> How can i enable debug logging for you ?
Go to the Settings in LMS. Then select Advanced. Choose the Logging pull
down. Scroll the list until you see the (plugin.denonavpcontrol) -
DENON AVP/AVR Control. Change it's
Aesculus wrote:
> Probably will need a debug log captured to see what is going on beneath
> the covers wrt the plugin.
>
> Here is another experiment: Have the AVR off and LMS off. Then select
> the physical button of the Quick Select you have indicated you want
> executed with the plugin. See
madpatrick wrote:
> Active as in On. In the display i see the option Z2 and i can turn it
> off with the button on the AVR.
> In DenonAvpControl i only have Main Zone selected.
>
> update --
>
> Ive tested it a bit more.
>
> AVR Off - Z2 Off / turn LMS on --> AVR On with Z2
>
SamY wrote:
> Not unless you specified Zone 2 in the DenonAvpControl menu or there's a
> bug. What do you mean by 'active'?
Active as in On. In the display i see the option Z2 and i can turn it
off with the button on the AVR.
In DenonAvpControl i only have Main Zone selected.
-
Patrick
madpatrick wrote:
> Ok. No problem. It was just a nice to have functionality.
>
> I notice btw that my Zone 2 is active when i use the squeezebox.
> This is not in my setup of my quick-select nor i have activated (so far
> i can see in my settings)
>
> Could it be triggered by the plugin ?
SamY wrote:
> There is currently no way to do that other than just stopping playback
> on the SB instead of powering it off before switching AVR inputs.
> However, depending on the player you are using, you can now switch back
> to the Squeezebox without powering the AVR off and on. This is
madpatrick wrote:
> Great. I will test the new version the coming days.
>
> Is it a possibility to disable the poweroff when you switch of the
> Squeezebox when it is on a different Quick select.
> For example, when i'm lisiting to the squeezebox, but want to switch to
> my mediaplayer (with
Great. I will test the new version the coming days.
Is it a possibility to disable the poweroff when you switch of the
Squeezebox when it is on a different Quick select.
For example, when i'm lisiting to the squeezebox, but want to switch to
my mediaplayer (with sound over the AVR) i don't want
We have a beta for version 4.1 ready for testing. You can get the zip
file from GitHub here
https://github.com/aesculus/denonavpcontrol/blob/master/src/DenonAvpControl_4_1.zip
Unzip and copy the files and folders to you LMS plugin cache.
These are the features to test:
* Improved support for
madpatrick wrote:
> First i want share my happiness with this plugin. It works great and
> makes life a lot easier.
>
> Maybe ive missed something on the development or on the forum, but is
> it correct that when i change the volume on my squeezebox, volume of the
> AVR is also changing ?
> I
First i want share my happiness with this plugin. It works great and
makes life a lot easier.
Maybe ive missed something on the development or on the forum, but is
it correct that when i change the volume on my squeezebox, volume of the
AVR is also changing ?
I mean literally. The volume number
SamY wrote:
> Good to know, although it seems like overkill seeing as each zone has
> its own set of Quick Selects. It's an easy code change though. Any other
> differences in recent models that might call for code changes?
> Additional zones?
I think you may find that the upper level models
SamY wrote:
> Good to know, although it seems like overkill seeing as each zone has
> its own set of Quick Selects. It's an easy code change though. Any other
> differences in recent models that might call for code changes?
> Additional zones?The AVR-X2500H has 1 main zone and another secondary
edwin2006 wrote:
> Mine AVR-X2500H also has 4 quick presets
Good to know, although it seems like overkill seeing as each zone has
its own set of Quick Selects. It's an easy code change though. Any other
differences in recent models that might call for code changes?
Additional zones?
Sam
madpatrick wrote:
> Great. Will check it out
>
> One point for attention.
> In the configuration you can chosse 3 Quick selects, but my AVR has 4
> Quick selects.
> Not a major issue, but maybe good to know that the newer AVR are having
> 4 Quick selectsMine AVR-X2500H also has 4 quick presets
Aesculus wrote:
> SamY and I have completed our updates to 4.0 and it is now on GitHub. It
> should show in your LMS Plugins panel in a few hours or automatically
> update if you have selected that option.
>
> Not much physical changes that you can see other than new icons.
>
> But under the
Aesculus wrote:
> SamY and I have completed our updates to 4.0 and it is now on GitHub. It
> should show in your LMS Plugins panel in a few hours or automatically
> update if you have selected that option.
>
> Not much physical changes that you can see other than new icons.
>
> But under the
SamY and I have completed our updates to 4.0 and it is now on GitHub. It
should show in your LMS Plugins panel in a few hours or automatically
update if you have selected that option.
Not much physical changes that you can see other than new icons.
But under the covers there is a lot going on
peterw wrote:
> Here's what my AVR (an old 2309CI) just gave me for "Z2?" :
>
> Z2TV/CBL
> Z240
> Z2OFF
>
Hmmm... Looks like you're right. My AVR3311ci returns:
Z2OFF
Z2DOCK
Z240
SVSOURCE
Looks like support for Sync on Track Change for all zones is possible
after all.
Thanks!
Sam
SamY wrote:
> I've actually thought about adding that as an optional feature in
> AvpControl also. Maybe v5.0. The only method currently in place for
> handling that situation is the optional "Sync on track change", which
> only works for the main zone since, as far as I have been able to
>
peterw wrote:
> Except that you have to power cycle the AVR?
Not really. The timeout only happens (but rarely) when the AVR is
powered off (in standby mode) and I am trying to query its power status
(PW?) during player startup. If it's already powered on, there's not a
problem. The AVR always
SamY wrote:
> Good news! I was able to re-create the situation with my fix applied and
> it worked like a champ. It will be included in v4.0. No more needless
> trips through the house to fiddle with the AVR, David. You will finally
> be able to achieve true "couch potato" nirvana. ;-)
>
>
> I think we're probably talking about the same behavior, which is rooted
> in the fact that, under certain circumstances which are still unclear to
> me, an AVR in standby mode can go into a state where the only command it
> will respond to is a "PWON" (or "ZnON")
Except that you have to power
peterw wrote:
> I've seen something similar, but far more frequently, sometimes just a
> small number of minutes apart and while the AVR was powered on.
>
> It's been so long since I dealt with this, but several versions back in
> my DenonSerial plugin I added logic to clear my command queue
DavidBulluss wrote:
> It probably does bother me as much as you, needless trips to that part
> of the house to turn the amp on and off! I have always assumed it was to
> do with the wifi in the amp needing livening up or something
> non-technical like that. Look forward to hearing if it does it
SamY wrote:
> Thanks, David. It's good to know it's not just me, although it sounds as
> though it doesn't bother you as much. If my fix works out, I will try to
> get it in v4.0. I'm just waiting for it to happen again now which, of
> course, it never will. Sort of like your car refusing to
DavidBulluss wrote:
> Yep, my AVR 2113 does it regularly, and solution for me has always to
> turn the amp on manually, then off again, usually all good after that.
> It doesn't seem related to how long it has been turned off though, I can
> go a few weeks without powering on from the client
SamY wrote:
> Hello all. I have a question for you. I regularly experience a situation
> where my AVR won't respond to a "power on" command from the client, no
> matter how many times I try. It only happens after the AVR has been
> powered off overnight or longer, and the only way to clear it
SamY wrote:
> Hello all. I have a question for you. I regularly experience a situation
> where my AVR won't respond to a "power on" command from the client, no
> matter how many times I try. It only happens after the AVR has been
> powered off overnight or longer, and the only way to clear it
No issues with On/Off for me on my Denon AVR-950H
Plugin works great
-
Patrick
madpatrick's Profile: http://forums.slimdevices.com/member.php?userid=4929
View this thread:
SamY wrote:
> ...
>
> Have you ever experienced this problem? If you have, how often does it
> happen and what is your AVR model? If you experience it regularly and
> would like to help me test the fix, let me know. Thanks.
All smooth going with my AVR-X1300W here. A good place to ask about
Hello all. I have a question for you. I regularly experience a situation
where my AVR won't respond to a "power on" command from the client, no
matter how many times I try. It only happens after the AVR has been
powered off overnight or longer, and the only way to clear it up is to
manually turn
MarSOnEarth wrote:
> Both. There is an "Volume Step" setting in Material Skin. It's a
> drop-down with '1', '2', '5', and '10'% choices, with mine set at '5%',
> BUT which was promptly ignored when the player's volume was set to
> 'fixed'; hence the 1% increment you saw. Then, I switched the
SamY wrote:
> Everything looks good in the log. I noticed that your volume change
> increments started out at +/-1 but changed later to +/-5. Is that a
> configurable setting in your client, or did you change to a different
> client?
Both. There is an "Volume Step" setting in Material Skin.
MarSOnEarth wrote:
> My brain/fingers seem not cooperating tonight. I thought I was
> attaching the corresponding server log, but it's not there in my post.
> Attaching it here
> ]
Everything looks good in the log. I noticed that your volume change
increments started out at +/-1 but changed
DavidBulluss wrote:
> Good morning! I set the Squeeze CTRL vol incs @ 5 for all players. Log
> file attached is firstly for the Zone 1 AMP which did not respond at all
> to UP then DN mute control although it faithfully responded to the other
> two options. Secondly for Zone 2 AMP which did not
SamY wrote:
> Thanks. This looks interesting but it's late here "up top" and I'm
> headed to bed. Thanks.
Good morning! I set the Squeeze CTRL vol incs @ 5 for all players. Log
file attached is firstly for the Zone 1 AMP which did not respond at all
to UP then DN mute control although it
SamY wrote:
> Glad to hear that
My brain/fingers seem not cooperating tonight. I thought I was
attaching the corresponding server log, but it's not there in my post.
Attaching it here
[Ah, I see, .7z format is not allowed]
DavidBulluss wrote:
> OK, first up AMP 1 Zone 2 turned on, music played. when muting the dn
> then up worked, but up then dn didn't. Simultaneous up worked. Then I
> played with volume a bit and then up then dn worked. Turned off LMS &
> system.
> Next AMP 2 Zone 1 turned on. Mute via dn then
SamY wrote:
> Thanks for the feedback, David. When you have time, I would appreciate
> it if you could generate a debug log and send it, along with a
> description of what you observed during the test.
OK, first up AMP 1 Zone 2 turned on, music played. when muting the dn
then up worked, but up
DavidBulluss wrote:
> Pressing down then up or down and up works on my Zone 2. Up then down no
> result. I have just tried it on Zone 1 on a different Denon AVR and at
> first muting worked down then up, but down and up at same time didn't,
> nor did up then down. Interesting that it stopped
MarSOnEarth wrote:
> It all worked as you inteneded in the Material UI app, and the Squeezer
> app. I also tried both, with 'fixed', and 'variable' volume control on
> the player. Muting worked in every case.
>
> Thanks, Sam.
Glad to hear that. The software muting method should work whether
SamY wrote:
> I have made some changes to be included in version 4.0 that add support
> for muting and unmuting the AVR in response to a client "mixer muting"
> command...
It all worked as you inteneded in the Material UI app, and the Squeezer
app. I also tried both, with 'fixed', and
DavidBulluss wrote:
> I will try the up then down again, but it wasn't working for me
> yesterday although I may have been timing out on the 0.25 secs. Pretty
> sure my phone is 2 buttons although one piece of plastic! Acts as a
> rocker or both together. Will try both together.
>
> Cheers,
SamY wrote:
> Pressing the buttons in either order should work, David. If your phone
> has separate buttons for volume up and down, the easiest way is to press
> both at once. If it is a rocker switch, a quick up/down or down/up
> should do it. I feel that the .25 second time interval is
peterw wrote:
> FYI, iPeng (version 9, at least), effectively toggles muting if you
> double-tap its onscreen volume slider. Under the covers it's setting the
> player volume to *not zero but (-1 * the current volume), e.g. volume 50
> becomes -50* when muting, which works (and which I like --
peterw wrote:
> Yes. Also recall I'm hijacking a bit here and discussing my plugin, in
> hopes that my experience w/ iPeng will help you all better support iPeng
> users with your plugin. (My plugin actually refuses to take any action
> unless the Squeezebox player volume is fixed at 100%.)
>
> I double-tap the iPeng slider to mute. My plugin saw Squeezebox volume
> change to -71/100, treats that like 0/100, sends a command to the AVR
> like MV99 and all is well.
It sounds like iPeng is sending a superfluous volume change command
after the mute on/off commands, which is something
Aesculus wrote:
> Did you try this with the volume in the player fixed at 100%? For me
> muting works as described with the regular setting but I get no response
> when the volume is fixed at 100%
Yes. Also recall I'm hijacking a bit here and discussing my plugin, in
hopes that my experience
peterw wrote:
> FYI, iPeng (version 9, at least), effectively toggles muting if you
> double-tap its onscreen volume slider. Under the covers it's setting the
> player volume to 0 when muting, which works (and which I like -- my old
> AVR has a relay clicking noise when you use the Denon MUON
SamY wrote:
> I have made some changes to be included in version 4.0 that add support
> for muting and unmuting the AVR in response to a client "mixer muting"
> command ... there unfortunately are very few client apps that currently
> contain support for muting. However, based on recent
DavidBulluss wrote:
> I forgot the procedure for mute using the phone vol buttons was down/up
> quickly and I was trying up/down initially. Is it possible to add script
> for both options?. Also, for me, 0.5 sec would be a better limit from
> down/up.
Pressing the buttons in either order
DavidBulluss wrote:
> Installed and ready to go but no time at the minute, heading out for the
> day. Will have a good play with it later today. Looking forward to the
> Easter egg! :-)
>
> Regards, David
The Easter egg found and works like a treat! :-)
The entire app is working beautifully
DavidBulluss wrote:
> Installed and ready to go but no time at the minute, heading out for the
> day. Will have a good play with it later today. Looking forward to the
> Easter egg! :-)
>
> Regards, David
Likewise, but playing postponed until tomorrow.
SamY wrote:
> Happy holidays and happy testing!
Installed and ready to go but no time at the minute, heading out for the
day. Will have a good play with it later today. Looking forward to the
Easter egg! :-)
Regards, David
*Server*rpi3 pCP7.0.1 LMS8.1.2
*Media*USB hard drive
*Lounge/dining
I have made some changes to be included in version 4.0 that add support
for muting and unmuting the AVR in response to a client "mixer muting"
command, as well as a backdoor way to mute it manually via your phone's
hardware which, in light of the upcoming holiday, I'll call an 'easter
egg'. ;-)
madpatrick wrote:
> Hi,
>
> I wanted to support this great plugin, so i've made a translation to
> Dutch (NL) for the Strings
> Not sure if is needed and you will incorporate in your plugin.
>
>
> 33916
Thank you.
I have incorporated it into the master.
Chris
SamY wrote:
> That's exactly what I hoped to hear. If you want to adjust the initial
> volume when turning the Squeezebox player on, simply change the Zone 2
> Quick Select volume setting. Zone support is now complete (pending any
> future bug fixes) and working as designed (if not better :o).
DavidBulluss wrote:
> Good to see it is coming together well! My Zone 2 vol is set at LAST for
> power on. Volume that I had Zone 2 QUICK SELECT set for is 65 (guessing
> decibels as it is set within the DENON setup browser via network) which
> is reported by SQUEEZE CTRL as 85%. I have Denon
SamY wrote:
> Good news, David! First of all, we finally got a reply from the Quick
> Select command, and you'll never guess what the response time was
> 2.06 seconds! That's right. Your AVR was missing the timeout limit by
> .06 seconds. Based on this, I will increase the timeout value
DavidBulluss wrote:
> Whoops! I accidentally picked up the wrong one and sent it to you,
> correct one from yesterday attached.
>
Good news, David! First of all, we finally got a reply from the Quick
Select command, and you'll never guess what the response time was
2.06 seconds! That's
SamY wrote:
> That's the same log you sent previously, David. Did you remember to turn
> debug on before running the test? Also, to make things easier for me, I
> would appreciate it if you could start a new log file or just cut and
> paste the portion that corresponds to the latest test.
Hi,
I wanted to support this great plugin, so i've made a translation to
Dutch (NL) for the Strings
Not sure if is needed and you will incorporate in your plugin.
Only i did not see the translated text in the plugin yet. also not
after a reload
33916
DavidBulluss wrote:
> Log attached. Again seemed the same at my end except that the start
> volume seemed higher, even though it read the same on the amp.
> Interested to see what you get out of the log
>
That's the same log you sent previously, David. Did you remember to turn
debug on before
SamY wrote:
> I'm glad it's all working from your point of view, but the Quick Select
> continues to time out, which prevents us from syncing the client volume
> accurately at power on. In comparing your log files to those of
> MarSOnEarth, I noticed that his Power On commands (Z2ON) are
>
DavidBulluss wrote:
> OK, set Zone 2 input manually to something else, set volume of Zone 2 at
> 30. My QUICK SELECT volume setting is 65. Using SQUEEZER turn on of LMS
> worked as expected, with Zone 2 volume being set to 65 and correct input
> selected. Seems all good from where I sit :-)
SamY wrote:
> Well, everything looks great except the Zone 2 Quick Select 3 command is
> still timing out. Did you notice anything unusual? I guess it completed
> successfully? The next time you test, change the Zone 2 input manually
> to something other than the Squeezebox player before
DavidBulluss wrote:
> From memory I probably didn't change the volume during the previous log,
> I was more concerned about Zone 1 having not turned off! New log file
> attached :-)
>
Well, everything looks great except the Zone 2 Quick Select 3 command is
still timing out. Did you notice
SamY wrote:
> Hey, David. Is it possible you didn't have debug turned on for your last
> test? All I see is a Zone 2 power on (successful) followed by a Quick
> Select 3 command that times out and then a Zone 2 power off (also
> successful). There are no volume changes. I'm hoping maybe that's
SamY wrote:
> Sounds good, David. Fyi, I just now refreshed the replacement version of
> plugin.pm that I uploaded in my last post to fine tune the changes. At
> the time, it was showing 0 views so I thought it was safe but you should
> probably re-download it just in case. I'll check your
DavidBulluss wrote:
> Latest files installed and tested. I thought there was an issue with the
> main zone of the amp remaining on after turning LMS off so I turned on
> debug and went through turn on, play track etc. and turn off and the
> main zone went off. Log attached. At this time I must
SamY wrote:
> Okay. Almost perfect is not perfect enough. This version will prevent
> the plugin from sending volume requests that don't result in a change
> from the previous value, preventing unnecessary timeouts. I have tested
> it successfully in my system and it is working as designed so
401 - 500 of 935 matches
Mail list logo
