SamY wrote:
> Yes, the
> /var/lib/squeezeboxserver/cache/InstalledPlugins/Plugins/DenonAvpControl
> directory should be the correct one. You can verify this by looking at
> the 'Information' page in the LMS server settings. Once the fix is
> installed, you can go back to using the plugin
Giunti wrote:
> I suppose I will be able/willing to do that ... with a little help from
> SamY ;-)
>
> I'm running LMS on a armv7l-linux Debian "Buster" environment and here's
> where the DenonAVP control plugin seems to reside:
> root@CT:/# find -name denon*
>
SamY wrote:
> I have a fix for you to test but it will involve manually replacing two
> files in the DenonAvpControl LMS plugin directory and then restarting
> LMS. Would you be willing and able to do that? I can give you detailed
> instructions and upload the files as an attachment. I can't
Giunti wrote:
> Thank YOU for your kind and most elongated efforts to get me on the
> right track, Sam.
I have a fix for you to test but it will involve manually replacing two
files in the DenonAvpControl LMS plugin directory and then restarting
LMS. Would you be willing and able to do that? I
SamY wrote:
> Once again, thanks for helping me debug this problem. There will be a
> fix for it in the next release.
Thank YOU for your kind and most elongated efforts to get me on the
right track, Sam.
Giunti's
Giunti wrote:
> It seems that the restorer reverts to "medium" whenever ZMOFF is issued
> and thus requires to be set to OFF manually via AVR GUI. When all's set
> right I get these responses via Telnet:
>
> ZMON
> SSINFAISFSV 441
> PWON
> MVMAX 80
>
> PSRSTR MED
> PSRSTR MED
>
> PSRSTR
Giunti wrote:
> BUT ... after the above Telnet commands had been carried out both
> functions (on/OFF and vol control) were dropped again. I have no idea
> why.
It seems that the restorer reverts to "medium" whenever ZMOFF is issued
and thus requires to be set to OFF manually via AVR GUI. When
Giunti wrote:
> I eventually got the restorer to accept and keep the OFF state and thus
> run a telnet session:
>
> ZMON
> PWONX 80
>
> PSRSTR MED
> [no response]
>
> PSRSTR MODE1
> [no response]
>
> However, this time it worked switching the AVR on AND off via Squeezer.
> And, having set
SamY wrote:
> It's because the plugin is keeping its telnet session open due to the
> problem. Until you can get the Restorer mode changed to 'Off' or turn
> off the 'Enable audio settings menus?' option in the plugin menu, you
> will have to shut down LMS temporarily in order to establish a
Giunti wrote:
>
> Now, when starting a telnet session with Denon AVR I immediately get a
> 'PSRSTR MED' without any command from my part. Besides, I can't enter
> any new command ... weird behavior to me.
It's because the plugin is keeping its telnet session open due the
problem. Until you
Giunti, please don't edit your previous posts to change or provide new
information. I do not get notified when edits takes place. Thanks.
Sam
SamY's Profile: http://forums.slimdevices.com/member.php?userid=63495
View
Ok. I know exactly what is happening now. The volume control not working
is also a result of the Restorer mode not being set to "Off" for the LMS
player input. If you can't figure out how to turn it off using the Denon
remote or app, uncheck the Denon plugin setting labeled "Enable audio
Giunti wrote:
>
> In Squeezer I now found "Fixed Volume 100%" and ticked it. But now I can
> no longer control the volume via Squeezer or the LMS-UI.
With volume fixed at 100%, volume changes in the client app should now
be carried out by the AVR's preamp. So you're saying that the AVR volume
Giunti wrote:
> At first, "Restorer" was greyed out, thus couldn't be changed. Upon
> clicking on active entries like "Volume" all of a sudden "Restorer"
> turned white and I set it to "OFF"
>
> HOWEVER, when thereafter trying to turn on and off the player via
> Squeezer ended up in starting
SamY wrote:
> There were definitely some major problems in the plugin with volume
> management at one time but they have all been taken care of now. If you
> have the time, I would ask that you try the 'Fixed at 100%' option
> again. The plugin now supports switching back and forth between
Giunti wrote:
> Well, Sam, at one earlier stage I decided to change from "Fixed at 100%"
> to "Variable" because I had got strange behavior of the volume level
> (far too loud) at start up of the LMS and when controlling the AVR via
> the Denon App on my mobile, especially when switching to
Giunti wrote:
> Hi Sam,
> here's what my Putty telnet session yielded:
>
> ZMON
> ZMON
> MVMAX 80FRL OFF
>
> PSRSTR MED
> [-no response-]
>
> PSRSTR MODE1
> [-no response-]
>
> Sorry for this result ;-)
Thanks for your help, Giunti. The fact that there was no response to the
'PSRSTR MED'
SamY wrote:
> ...
> I noticed in the log that you have set the volume setting for the player
> in the Audio section to "Variable", meaning that volume changes are
> handled by LMS in the digital domain. Normally, it is recommended that
> you set it to "Fixed at 100%" in order to preserve the
SamY wrote:
> An update to my previous post. As it turns out, it's not simply a matter
> of AVP vs AVR. Apparently, Denon changed the content of the response to
> the telnet command for querying the AVR's audio restorer mode, as well
> as the syntax of the command used to set it, at some point
An update to my previous post. As it turns out, it's not simply a matter
of AVP vs AVR. Apparently, Denon changed the content of the response to
the telnet command for querying the AVR's audio restorer mode, as well
as the syntax of the command used to set it, at some point in the
mid-2010's.
Giunti wrote:
> Hi again Sam,
>
> hope the attached log file will yield the necessary data to pin down the
> problem.
>
> Cheers !
Congratulations! You have uncovered a bug in the plugin that would only
occur if you are using an Audio Restorer mode other than 'Off' with a
Denon AVR (as
SamY wrote:
> Here you go...
>
> > > >
> Go to Advanced->Logging in LMS settings.> >
> > > >
> Change the logging level for (plugin.denonavpcontrol) to "Debug" and
> hit "Apply" at the bottom of the page.
> > >
> > > > Using Squeezer, turn on the LMS player associated
Giunti wrote:
> Tanks for replying that promptly, SamY !
>
> Well, upon reading several relevant posts in this forum prior to my
> query I already knew about your above explanations: Definitely my AVR
> was always set to the same input associated with the player and, YES,
> the plugin is set
SamY wrote:
> Hello, and welcome to the forum! Prior to v4.2, the plugin would always
> power off the AVR when the associated LMS player (not the server) was
> turned off. However, this behavior was modified in v4.2 such that the
> AVR is now only powered off if it is currently set to the input
Giunti wrote:
> Hi everyone !
>
> I've been using a Squeezebox/LMS for about 10 years now, for the past 2
> yrs together with a DENON AVR-X1500H. At some stage I decided to install
> the Denon AVVP/AVR control plugin and it worked fine right away. I very
> much liked its automatic ON/OFF
Hi everyone !
I've been using a Squeezebox/LMS for about 10 years now, for the past 2
yrs together with a DENON AVR-X1500H. At some stage I decided to install
the Denon AVVP/AVR control plugin and it worked fine right away. I very
much liked its automatic ON/OFF control of the AVR via the
mctr wrote:
> Yep no worries. The power offs definitely happened, also I could never
> get the quick select working. My Marantz calls it "Smart Select" I
> assume it's the same, maybe not. But cheers for the hard work and timely
> responses.
No problem. If you should ever decide that the
SamY wrote:
> I'm sorry that the plugin didn't meet your needs. The next release will
> ignore absolute volume requests of 100% for all players (not just the SB
> Touch) when the player is running at fixed volume in order to avoid the
> sporadic spikes you observed earlier with your version of
mctr wrote:
> Sadly I went back to not using the plugin - first went back to variable
> volume although I just use the remote control mostly for the AVR with
> this particular player. And then ended up turning off the power-control
> feature because I had one too many power-offs while it was
uudruid74 wrote:
> That would be annoying, but why turn the player off at all? I dont turn
> it off because a Rpi doesnt use much power and I dont want to wait for
> it to boot.
>
> I have my Denon trigger out controlling an outlet that turns my DAC and
> a tube preamp I use for music
mctr wrote:
> Sadly I went back to not using the plugin - first went back to variable
> volume although I just use the remote control mostly for the AVR with
> this particular player. And then ended up turning off the power-control
> feature because I had one too many power-offs while it was
SamY wrote:
> Thanks for the info. The next step in resolving this would be either of
> the following:
>
> 1. Install a patched copy of Plugin.pm in your plugin directory that
> ignores 100% volume requests from ANY player when running with fixed
> volume, not just the SB Touch.
>
> 2. Turn
SamY wrote:
> I'd like to get an idea of how many users of this plugin there are out
> there. I know that, in my case, I was using it for more than a year
> before discovering this forum so it won't be accurate. But, if you're
> seeing this post, just reply and provide a short description of
SamY wrote:
> I'd like to get an idea of how many users of this plugin there are out
> there. I know that, in my case, I was using it for more than a year
> before discovering this forum so it won't be accurate. But, if you're
> seeing this post, just reply and provide a short description of
mctr wrote:
> Model: SqueezeLite
> Type: squeezelite
> Firmware: v1.9.7-1270
>
> running under moode 761, pi 3b, material skin, ios chrome
Thanks for the info. The next step in resolving this would be either of
the following:
1. Install a patched copy of Plugin.pm in your plugin directory
SamY wrote:
> Looking into this further, your volume spike problem is very similar to
> a known bug in the Squeezebox Touch firmware where it will mistakenly
> set the actual player volume to 100% during its initialization if the
> player is set to fixed output. We handle this in the plugin by
mctr wrote:
> Just turning off fixed volume/AVR volume control. Will play around with
> it in the future if I have time to see whatÂ’s going on
Looking into this further, your volume spike problem is very similar to
a known bug in the Squeezebox Touch firmware where it will mistakenly
set the
SamY wrote:
> I'm not sure what you mean. What feature exactly is it that you are
> disabling? If you need directions to enable debug logging for the plugin
> in order to see what LMS commands are triggering the volume spike, let
> me know.
Just turning off fixed volume/AVR volume control. Will
mctr wrote:
> It is tough to nail down, I am not really sure what the trigger is. I
> think it happened just now while I was pulling up the tab within iOS
> chrome with my LMS. Happens often enough that I have to disable the
> feature.
I'm not sure what you mean. What feature exactly is it
SamY wrote:
> I have no idea but it sounds like a client (Material Skin) problem. Does
> it happen only when switching TO the plugin player, FROM the plugin
> player, or both? I would need a plugin debug log showing the time period
> where the behavior occurs in order to see what triggers the
mctr wrote:
> Here's another little issue that I've run into (using Material skin on
> Win10 LMS outputting to Pi 3 on SqueezeLite) - Occasionally when
> switching back and forth between players the AVR will jump to 100%
> volume (70dB setting) on the player running the plugin. Not sure how
>
Here's another little issue that I've run into (using Material skin on
Win10 LMS outputting to Pi 3 on SqueezeLite) - Occasionally when
switching back and forth between players the AVR will jump to 100%
volume (70dB setting) on the player running the plugin. Not sure how
this is triggered and
uudruid74 wrote:
> I assume I need to change Jivelite for this? Oddly, my Play/Pause
> button doesn't work (hasnt ever) so I need to patch it for this anyway.
It certainly sounds as though that's the case, although I have zero
familiarity with Jivelite. I'm a little surprised that it
SamY wrote:
>
> Update: Just discovered that if you're using the Material Skin LMS
> interface, you need to make sure the "Fixed volume players" setting on
> its plugin menu is set to "Display standard volume control".
OK. The Material Skin issue was the problem. It looks like the
Jivelite
SamY wrote:
> I'd like to get an idea of how many users of this plugin there are out
> there. I know that, in my case, I was using it for more than a year
> before discovering this forum so it won't be accurate. But, if you're
> seeing this post, just reply and provide a short description of
SamY wrote:
> You might want to read the 'wiki pages'
> (https://github.com/aesculus/denonavpcontrol/wiki) for information on
> how the AVR volume is controlled. In a nutshell, it depends on the LMS
> volume control setting for the player. If it is set to "Fixed at 100%",
> as recommended, the
mctr wrote:
> Oops, I must have misunderstood it. I thought it would adjust the AVR
> volume as you adjust the LMS volume and vice versa. But that is good to
> know.
You might want to read the 'wiki pages'
(https://github.com/aesculus/denonavpcontrol/wiki) for information on
how the AVR volume
SamY wrote:
> What behavior are you expecting from the volume syncing option? All it
> does is resync the player volume to the Denon volume at every track
> change, which is only useful if the volume is frequently changed via
> the Denon remote rather than through an LMS client. Otherwise, it
mctr wrote:
> This version no longer breaks my LMS but I can not get the volume to
> sync. Then again I never had that working on the old version either
What behavior are you expecting from the volume syncing option? All it
does is resync the player volume to the Denon volume at every track
backball wrote:
> I'm trying to start from ground zero and understand the functionality of
> the Denon AVP/AVR plug-in (using v4.3.2) and searching the forum didn't
> show anything obvious.
>
> Here's my setup:
> * 1x Squeezebox Receiver (A) connected to digital in (RCA) on a 4 zone
> Control4
SamY wrote:
> This bug is fixed in v4.3.3 of the plugin, which is now available for
> upgrading.
This version no longer breaks my LMS but I can not get the volume to
sync. Then again I never had that working on the old version either
I'm trying to start from ground zero and understand the functionality of
the Denon AVP/AVR plug-in (using v4.3.2) and searching the forum didn't
show anything obvious.
Here's my setup:
* 1x Squeezebox Receiver (A) connected to digital in (RCA) on a 4 zone
Control4 matrix amp
* 1x Squeezebox
SamY wrote:
> It's a known problem on Windows with the latest v4.3.2 plugin and will
> be fixed in the next release. See 'this post'
> (https://forums.slimdevices.com/showthread.php?60114-Announce-Denon-AVP-Control-Plugin=1040450=1#post1040450)
> for instructions on how to patch it in the
mctr wrote:
> Hello all, having a little weird issue with (I think) this Denon plugin
> --
>
> I'm running LMS on Windows 10 with my squeezelite instance under Volumio
> on a Pi 3. I've installed the Denon AVR control plugin and pointed it to
> a Marantz NR1605 which is on my local network on
Very strange.
As you can probably imagine, if this plugin stopped the host computer
then there would be a lot of complaints.
Does the host Windows machine completely stop working and you have to
use the power switch to get it working again?
Paul Webster
author of \"now playing\" plugins
Hello all, having a little weird issue with (I think) this Denon plugin
--
I'm running LMS on Windows 10 with my squeezelite instance under Volumio
on a Pi 3. I've installed the Denon AVR control plugin and pointed it to
a Marantz NR1605 which is on my local network on a fixed IP. My first
MarSOnEarth wrote:
> Yeah, this rings a bell. Closing the app, though, is semantically
> equivalent to turning off the player, especially if it was the player
> that caused the AVR to be powered on, no?
I suppose it depends on the client app and how you use it. I have 6
players and use two
SamY wrote:
> Maybe it was a change to MS then. The plugin only (and always) powers
> off the Denon when the associated SB player is explicitly turned off. A
> recent change (v4.2) added the condition that the input of the Denon
> currently must be set to the one specified in the Quick Select
MarSOnEarth wrote:
> It used to work (even when just backing out of the app), and then I
> recall a conversation about only turning off AVR if it was turned on by
> the client (player), as someone complained about it happening regardless
> whether the AVR was already on or not. It must had been
SamY wrote:
> Glad to hear. Just to clarify though, quitting a client app should never
> turn off the AVR unless the client has some sort of option to turn off
> players upon exit. If it used to do so, it was a bug. The AVR
> should only be powered off when the player is turned off.
It used
MarSOnEarth wrote:
> Yes, thanks. It all works well with this version except the AVR is not
> being turned off when the player (MaterialSkin web app) is quit.
> Explicitly powering the player off works though.
Glad to hear. Just to clarify though, quitting a client app should never
turn off
SamY wrote:
> Ahh. Got it. Were you able to apply the fix and get the plugin up and
> running again?
Yes, thanks. It all works well with this version except the AVR is not
being turned off when the player (MaterialSkin web app) is quit.
Explicitly powering the player off works though.
MarSOnEarth wrote:
> Right. Too many thoughts about RPis and a bad copy RPis are the
> platforms for player OSs (the squeezelite part), LMS, indeed runs on
> Windows.
Ahh. Got it. Were you able to apply the fix and get the plugin up and
running again?
Sam
SamY wrote:
> Wait a minute. I'm confused. I thought you were running LMS on Windows.
> What am I missing?
Right. Too many thoughts about RPis and a bad copy RPis are the
platforms for player OSs (the squeezelite part), LMS, indeed runs on
Windows.
uudruid74 wrote:
> Hi.
>
> I'm runing the latest picoreplayer and this plugin doesn't seem to work
> at all. I have volumes set to be fixed at 100% because I don't ever
> want to change the data going to my USB DAC. I want volume changes to
> go directly to the AVR. The volume slider is
Hi.
I'm runing the latest picoreplayer and this plugin doesn't seem to work
at all. I have volumes set to be fixed at 100% because I don't ever
want to change the data going to my USB DAC. I want volume changes to
go directly to the AVR. The volume slider is greyed out. What should I
change
MarSOnEarth wrote:
> > > >
- AVR(s): Denon 1300X
- LMS Platform: RPi 4B+
- OS: HiFiBerry Pre+ w/HiFiBerry OS
- Type: squeezelite
- Firmware: v1.9.1-1139
- Client(s) in use: MaterialSkin app on Android
- Number of players using the plugin: 1
> > >
Wait a minute. I'm
MarSOnEarth wrote:
> Hi Sam,
>
> Attached is the server log and the command sequence that created it.
> Sorry it took a while. It's a busy time around here. And yes, in view of
> the results, please revert to the last good version (4.3.1). Thanks, and
> good luck.
I guess you missed my last
MarSOnEarth wrote:
> Hi Sam,
> And yes, in view of the results, please revert to the last good version
> (4.3.1). Thanks, and good luck.
I didn't read all that got posted in the meantime before posting the
test results, and now I see you're on top of it. It was a nice idea ;-)
- AVR(s): Denon 1300X
- LMS Platform: RPi 4B+
- OS: HiFiBerry Pre+ w/HiFiBerry OS
- Type: squeezelite
- Firmware: v1.9.1-1139
- Client(s) in use: MaterialSkin app on Android
- Number of players using the plugin: 1
SamY wrote:
> Okay. I see where the problem is happening and it seems to be specific
> to Windows, which is why it didn't occur during my testing. The plugin
> is basically going into a loop at a certain point. The place where it
> occurs is in a non-critical housekeeping routine that was
SamY wrote:
> As per the update to my previous post regarding this issue, I have
> isolated the problem to a bit of non-standard behavior affecting *LMS
> running on Windows only*.
An update on this. I knew the situation felt familiar and, sure enough,
it's the same problem I ran into when
MarSOnEarth wrote:
> Yes, that will do, Sam. Thanks. And, no problems at all. I know what I'm
> potentially up to. Let me know if you'd need more than just the debug
> log from the plugin.
As per the update to my previous post regarding this issue, I have
isolated the problem to a bit of
- AVR(s): Denon AVR-S740H
- LMS Platform: Netbook Samsung N150 Plus
- OS: Daphile 21.01
- Client(s) in use: Squeezer, Material Skin
- Number of players using the plugin: 1
4.3.2 version with delayed turn on of the receiver working like a charm.
Thank you.
:D
- AVR(s): Denon AVR-S950H
- LMS Platform: HP Microserver GEN8 CPU E3-1220L V2 @ 2.30GHz
- OS: ClearOS release 7.9.1 (linux)
- Client(s) in use: SQB Touch, SQB Radio
- Number of players using the plugin: 1
- LMS : Version: 8.2.1 - 1634705759
-
Patrick
I'd like to get an idea of how many users of this plugin there are out
there. I know that, in my case, I was using it for more than a year
before discovering this forum so it won't be accurate. But, if you're
seeing this post, just reply and provide a short description of your
setup if you can.
MarSOnEarth wrote:
> Yes, that will do, Sam. Thanks. And, no problems at all. I know what I'm
> potentially up to. Let me know if you'd need more than just the debug
> log from the plugin.
Okay. I see where the problem is happening and it seems to be specific
to Windows, which is why it didn't
SamY wrote:
> Sorry for your problems. As usual, I will need a debug log of the
> problem to see what is happening. If I don't see anything obvious, I'll
> get you a zip file of v4.3 to use in the meantime.
Yes, that will do, Sam. Thanks. And, no problems at all. I know what I'm
potentially up
MarSOnEarth wrote:
> Sam, please re-enable the previous version.
>
> Thanks
Sorry for your problems. As usual, I will need a debug log of the
problem to see what is happening. If I don't see anything obvious, I'll
get you a zip file of v4.3 to use in the meantime.
Sam
MarSOnEarth wrote:
> ...
> Here, with this version, LMS playback through Denon is no longer
> possible in my system. BTW, my configuration has changed. Now LMS is
> going into the main zone, preset 2, but that part (power-on and setup)
> works well, FWIW
Sam, please re-enable the previous
SamY wrote:
> V4.3.2 is now available. Please report any problems or questions here.
> Thanks.
Sorry for the long delay.
Sam, there's no good news about this version on my system. Most of the
time the power-on sequence executes but no play is initiated. Most of
the times, when the "play" is
V4.3.2 is now available. Please report any problems or questions here.
Thanks.
Sam
SamY's Profile: http://forums.slimdevices.com/member.php?userid=63495
View this thread:
MarSOnEarth wrote:
> Hi SamY,
>
> Glad you are still at trying to solve "first world" problems and
> polishing what's already is a pretty shinny plugin. As always, sure I
> can give a new version once-over, but there's already something in the
> queue, and maybe that was unintended. I received
Hi SamY,
Glad you are still at trying to solve "first world" problems and
polishing what's already is a pretty shinny plugin. As always, sure I
can give a new version once-over, but there's already something in the
queue, and maybe that was unintended. I received an update to version
4.3.1
Greetings, fellow Denonites. (I have yet to encounter anyone using the
plugin with a Marantz AVR.) I have made a small change in the upcoming
release of the plugin that fixes what I once regarded as a minor
shortcoming. As you may have noticed, when initiating playback of a song
or playlist on a
Ok. So, for now, you have a choice:
1. Leave it in "wife-friendly" mode, enjoying the convenience of not
having to press "play" every time you turn it on and hoping for no power
outages in the middle of the night, or
2. Change it to "Remain stopped at power on", putting up with having to
press
SamY wrote:
> Hi Patrick! Good to hear from you and happy that the plugin is
> performing well in your setup.
>
> I'm assuming that, in your scenario, the machine that LMS is running on
> is not affected by the power outage, i.e. a laptop running on battery
> backup, etc. Otherwise, the
madpatrick wrote:
>
> Is it possible not to turn on the amplifier after the squeezebox has
> restarted?
Hi Patrick! Good to hear from you and happy that the plugin is
performing well in your setup.
I'm assuming that, in your scenario, the machine that LMS is running on
is not affected by the
Hi,
Currently no issues with the plugin. All is working well.
When the squeezebox has been switched off due to, for example, a power
failure, the squeezebox will restart.
The amplifier will of course also be switched on. And Of course this
happens at times you don't want to.
Is it possible
SamY wrote:
> Version 4.3 of the plugin has been published. Following are the changes.
> See the wiki for more details. Note that you must select the "Enable
> audio settings menus?" option (turned off by default) from the player
> plugin menu in order to use the client audio settings plugin
Release 4.3 of the plugin has been published. Following are the changes.
See the wiki for more details. Note that you must select the "Enable
audio settings menus?" option (turned off by default) from the plugin
menu in order to use the client audio settings plugin menu in the
Squeezer and iPeng
DavidBulluss wrote:
> Hi Chris, no issues to report here, all appears to be behaving! But I
> have been interstate and away from the system for a week so haven't been
> able to give it a very good thrashing yet :o
>
> Cheers, David
That's great. Thanks for responding.
Chris
Aesculus wrote:
> Just checking in to make sure that everything being quiet here is a good
> sign. Some of the new features are a bit more subtle but they do improve
> the usability quite a lot.
>
> You can make sure you are on V4.2 by going to the server settings and
> plugin tab and check
Just checking in to make sure that everything being quiet here is a good
sign. Some of the new features are a bit more subtle but they do improve
the usability quite a lot.
You can make sure you are on V4.2 by going to the server settings and
plugin tab and check the value for DenonAVP/AVR
madpatrick wrote:
> No problem to update it manually.
>
> Is it an idea to give the beta version a different number like 4.1.x and
> then jump to 4.2.0 with a new release ?
It's not only an idea, it's exactly what I plan to do the next time. I
always try to learn from my mistakes.
Sam
No problem to update it manually.
Is it an idea to give the beta version a different number like 4.1.x and
then jump to 4.2.0 with a new release ?
-
Patrick
madpatrick's Profile:
madpatrick wrote:
> Hi Sam,
>
> I've currently version 4.2 installed on my LMS, but i had already the
> manual update done this weekend.
> So i can not confirm if the update was carried out, but since the
> version was already 4.2 i think it skipped the auto update
Okay. I was afraid that
Hi Sam,
I've currently version 4.2 installed on my LMS, but i had already the
manual update done this weekend.
So i can not confirm if the update was carried out, but since the
version was already 4.2 i think it skipped the auto update
-
Patrick
It's too quiet out there. Can someone verify that the plugin
has been updated to v4.2 on their LMS? I'm not very familiar with how
the update process works and could use some feedback. Thanks.
Sam
SamY's Profile:
The general release of v4.2 is now available. The changes include:
- The client plugin menu has been expanded to include the following
new functions:
- Channel volume sliders (all zones)
- AVR preamp output level slider when the player is in variable
201 - 300 of 935 matches
Mail list logo
