Hello, everyone. This is my first post here on the Squeezebox forums.
I am the owner of a Voco V-Zone music player, as well as a Spotify
Premium user. The V-Zone player is based on the Squeezebox architecture
and works with LMS via the MyVOCOnet plugin, which is installed from the
MyVOCO DEV
Hello, Phillipe. I just installed v1.6.0 of the plug-in, and
am experiencing a new problem where the audio skips forward a few
seconds near the beginning of each track and skips backward a
corresponding interval at the end of the track. The problem is easily
recreated and occurs on every track.
d6jg wrote:
> Phillipe. Although "flow" is mentioned under the *i* it isn't actually
> available to choose.
> 25835
The "Flow" option only appears if you select a Transcode option other
than "none".
SamY's Profile:
d6jg wrote:
> Phillipe. Although "flow" is mentioned under the *i* it isn't actually
> available to choose.
> 25835
The "Flow" option only appears if you select a Transcode option other
than "none".
SamY's Profile:
philippe_44 wrote:
> No update - but you should not have a problem in flac transcode mode and
> Tidal. I don't have anymore a Tidal subscription, so I can't test. Maybe
> you can send me a log (just let additional debugging empty to start
> with)
I will try to get a debug log, Philippe. In the
SamY wrote:
> Okay. I went back to using flac transcoding to get a debug log for Tidal
> streaming and, of course, it works just fine now. ;-)
> I am using the defaults for flac compression quality, resampling rate,
> and sample size, but may have been overriding one or more of th
philippt79 wrote:
> Hello Community,
>
> I am using the CastBridge plugin in LMS on a NAS since a few weeks now.
> Basically the setup of the plugin and first run works great. Many thanks
> for the effort to implement this!!
>
> Anyway, when I am stopping the playback it happens that the next
gianpaoloracca wrote:
> As I said in the title I tried enabling pcm transcoding for my
> chromecast in the plugin settings and everything is just fine.
> It's strange because AFAIR I never did it before and worked without
> issues for months...
> I'll leave it here if anybody has the same
Cali wrote:
> Hi
>
> I installed the plugin but it won't create the castbridge.xml config
> file, so it keeps saying "Configuration file missing".
> I run the program as an administrator.
Are there any errors in your server log? There seems to be a permissions
problem with the latest
nervoteso wrote:
> yes they are empty
>
> if i listen to music from spotify native google nest players audio is
> wonderful, if i play google nest from lms volume and quality sound poor.
> on lms players flac files sound amazing
I had a very similar problem with volume management when setting
slartibartfast wrote:
> Isn't the default setting "Volume controls adjust outputs"?
>
> Sent from my Pixel 3a using Tapatalk
I'm not sure what the default is. Just check and confirm that's what
it's set to.
SamY's
Akyhne wrote:
> I just installed this mod today on my Raspberry Pi (piCorePlayer).
>
> I'm having one big issue. The sound is very low, when my volume on my
> Denon AVR-2400H is set to a level I know how loud should be.
> If I go into LMS settings -> Player -> Audio and change "Volume Control"
Aesculus wrote:
>
> I would assume that in analog mode you would set your Quick Select to
> the loudest volume level you ever want to play from the Squeezebox and
> then use the Squeezebox volume control (or client) to send a % of that
> to the Denon.
I agree with Chris. If you are determined
peterw wrote:
> David, of you occasionally want to use other sources, I don't understand
> why you wouldn't want the Squeezebox output fixed at 100% so that only
> the AVR volume level changes. With SB audio output fixed at 100%, the
> Squeezebox volume becomes this fictional thing, and plugins
Akyhne wrote:
> It can't be a Denon problem, as the plugin from you guys is the only one
> to make this behavior.
It's a Denon problem, whether you think it can't be or not. Go back and
read the previous forum posts. It's not my job to convince you.
Sam
Aesculus wrote:
> Based on this I think there IS a problem with the ZIP file. I'll wait to
> get the latest from SamY, post the new zip and then post here when that
> is done so we can all get back on the same page.
I disagree, Chris. The ZIP file on Github is absolutely correct, as
DavidBulluss wrote:
> Just for comparison of the latest 4.1 beta that I downloaded from Github
> here is a simple log file. Turn lms on, play, volume up... vol down
> turn lms off 34573
>
> Regards, David
The log looks good, David! Did everything seem to perform as you
expected? I wonder
Good news for fans of muting support in the plugin. The next release of
Squeezer, of which I have obtained an advance copy, will include a mute
button on the volume control screen, and I am happy to say that it works
great with the plugin. The developer also plans to add optional support
for
MarSOnEarth wrote:
> As suggested, set the player volume control to fixed
> [(...)Settings->Player->(...)->Extra Settings->Audio->Volume Control =>
> 'Output level is fixed at 100%'], but then also set server-side setting
> of Material Skin to ignore that setting and allow for passing the
DavidBulluss wrote:
> That would be a great solution. You are correct that I have the app set
> up for Z2 and I do control Z1 using the remote as I am near the amp
> while using Z1.
One more question, David. When you are listening in Z1, what do you do
about the fact that Z2 is also on? Do you
DavidBulluss wrote:
> Yes, I understand that logic, but for may set-up the missing part of the
> puzzle is that I sometimes run Z1 on the same amp I am running Z2 and I
> always set Z1 manually (it has the main household TV etc. running
> through it and source gets changed unpredictably by
DavidBulluss wrote:
> other times I just turn Z2 off if we are moving inside from being
> outside.
So do you turn Z2 off with the Denon remote, or do the Z2 speakers have
their own on/off switch? You can't power it off with the LMS client app,
since that would stop playback in both zones.
Akyhne wrote:
> Yeah, I want to run with 100% fixed volume. I just didn't think the mod
> would adjust two different volume controls at once.
That only happens now when using variable output level. In v4.1, only
one preamp volume control will be in effect at a time -- LMS for
variable output
DavidBulluss wrote:
> What if I am using only one LMS player feeding to both Z1 & Z2 of the
> amp? Both zones are receiving the same signal simultaneously. I will
> have a play with it all as suggested.
>
Okay. Now I understand what you're trying to do. First of all, let's
assume that you are
TBoneCO wrote:
> My 3808 was falling off the network for years, so stopped using this
> plugin and coincidentally stopped listening to Squeezebox except special
> occasions. Replaced WiFi router (my main router) and low and behold my
> Denon is on the network and stable. Started using plugin
madpatrick wrote:
>
> I understand the 100% fixed outpout, but somhow i want also control the
> volume a little bit with LMS.
This is where I feel that you and others have a misunderstanding of what
happens when you use the 100% fixed output level player audio setting.
With this setting, you
DavidBulluss wrote:
> That idea I really like! Again, maybe peculiar to my system is that Z2
> is outside and quite a distance from the amp, and as such the remote
> doesn't work when outside. Yes, I know, set it before you go outside,
> but I usually turn the LMS on with Z2 when already
madpatrick wrote:
> Now i understand it.
> Changed the setting to fixed 100% and by the volume changing in LMS the
> AVR volume is changing
> Great, that it did not see this earlier. Forget my previous posts
>
Lol!!! I wish I could forget them.
Seriously I'm happy that things are working
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
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 ?
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:
> 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
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
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
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
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.
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
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
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
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
Okay. I think this is the one. (Warning: I once said that about my
ex-wife.)
After much thought and a few 'aha!' moments, I have come up with some
significant changes in the communications logic of the plugin that I
think will result in much greater stability and less dependence on the
nature
MarSOnEarth wrote:
> Got it yesterday. Hmm..
>
> Tomorrow.
It was updated today.
Sam
SamY's Profile: http://forums.slimdevices.com/member.php?userid=63495
View this thread:
Aesculus wrote:
> @SamY and @MarSOnEarth: Sounds like you're chasing your tails with my
> zip file. :-)
Indeed. I have deleted the updated modules I uploaded previously in
order to minimize any further confusion. The zip file is now the only
officially recognized source for the v4.
MarSOnEarth wrote:
> I've just posted the first part, but the rest will have to wait 'till
> tomorrow.
The debug log you just posted was not created with the latest v4.1 beta
version. Please install from the zip file on Github. Thanks.
Sam
MarSOnEarth wrote:
> A problem to have in open source; improvements happening at a furious
> pace. ;-)
>
> @SamY: I had time to run one more test, this time using the 'officially
> recognized source for the v4.1 beta' downloaded today. This one is still
> without turning on t
MarSOnEarth wrote:
> Drat! It has been a day for me.
>
> OK then, one more time (with fingers crossed), and sorry about the
> stumbles.
I don't know what version of the plugin created that debug log, but it's
not the one in the Github zip file. In fact, I couldn't match the line
numbers up
MarSOnEarth wrote:
>
> @SamY, @Aesculus: Talk amongst yourselves guys, and then lets try again
> when we're all on the same page/pull.
No need for Chris and I to talk. Your attachments convincingly
illustrate that you have downloaded the correct modules to a directory
on your LM
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
MarSOnEarth wrote:
> So, here's the latest. All looks OK. The QS is still timing out, but
> it's being handled (ignored?).
>
> BTW, I don't know about the others, but for me, because my Z2 is
> dedicated to Music (LMS), and it's so preset, having the QS setting
> enabled or not makes no
Aesculus wrote:
> I updated the beta package file for 4.1 in GitHub with @SamY latest
> fixes.
>
> https://github.com/aesculus/denonavpcontrol/blob/master/src/DenonAvpControl_4_1.zip
Thanks Chris. I would like to ask @MarSOnEarth and @DavidBulluss to
refresh the 4.1 beta from the
Hello all. I have been using this plugin for a couple of years now and
love the functionality it offers. Coincidentally, I have recently been
testing some changes to plugin.pm which fix both problems reported by
DAR. The simpler of the two, which takes care of the occasional log
message "Can't
Aesculus wrote:
> I am interested in what you have done. It works OK on iPeng but I have
> also had issues with Squeezer on Android using 100% volume. Maybe this
> will help.
>
> BTW one of the options in the plugin will resync the player with the amp
> after every track. Not sure if that
Aesculus wrote:
> OK. Is it worth having Squeezer fixed? I supposed we could put some
> brackets into the value Squeezer gives that makes it more stable.
The way I see it, the problem isn't in Squeezer. It's in Plugin.pm. The
good news is it's an easy fix. I'm actually not sure why it doesn't
Aesculus wrote:
> This looks good to me. I will try it out this weekend with the web
> browser, iPeng and Squeezer.
>
> Thanks for doing this.
You might want to hold off on your testing for a bit, Chris. I just ran
into the situation you are having with the volume going to 100% using
Squeezer
Aesculus wrote:
> Well the problem does not occur with the web interface or iPeng.
>
> The other "client" that has this problem is the UI on the Touch when set
> to 100%. I never pursued that but maybe your fix will help there too.
Attached is my latest version of Plugin.pm, which contains
DavidBulluss wrote:
> I have renamed the previous plugin.pm to pluginOLD.pm and dropped your
> version into the folder. Have restarted but not yet tested, will do this
> evening after work. Thanks for your effort, I imagine it will work
> well!
>
> Regards, David
Hi David. Please download the
DavidBulluss wrote:
> Will do! When I tested your original one I was disappointed that
> changing the volume on my phone using Squeeze CTRL didn't sinc the
> player controls to the same level, is that what you have fixed?
>
> David.
Sort of. It fixes a problem where the client volume can
edwin2006 wrote:
> Would it be possible to add this plugin into the 3rd party plugin
> library of LMS?
It's already there. Look for:
"DENON AVP/AVR Control (v2.0)"
Sam
SamY's Profile:
MarSOnEarth wrote:
> Here it is, but barring more adjustments the user experience is
> diminished vs. the previous settings. For one, the usable volume range
> has been compressed into the upper quarter of the total, and it's
> logarithmic; so, nothing, nothing, something, and L O U D. No
edwin2006 wrote:
> Really feeling very silly...
> Installed plugin but now what?
> Where to config?
> Searched high and low and plugin says installed plugin, restarted lms
> multiple times the same for the underlying picoreplayer.
The config settings are done in the Player section of the LMS
MarSOnEarth wrote:
>
> ... I tried to switch to fixed on the client, but that is not workable
> for one major reason; one cannot use a browser for playback on a
> smartphone. To clarify, this setting disables the volume bar, and
> browsers have no access to the hardware buttons; hence, no
Okay, David and Mars. Are you feeling lucky? Here is the latest version
of the beta, with actual support for the Quick Select command in Zones 2
and 3. I have done all the testing I can without actually having a Zone
2 or 3, included actually sending Z2QUICKn commands to my receiver
without any
MarSOnEarth wrote:
> I see what happened, and it's the best argument against setting initial
> volume on power-on. The plugin read the clients 100% setting and applied
> it the the AVR.
Okay. Sorry about waking the neighbors. Let me make sure I understand
what is happening though. I see the
MarSOnEarth wrote:
> Ill test the new version later. Earlier in the day I did run a
> sequence of tests for which a log, and the associated settings are
> included.
The log file shows that the plugin has been upgraded to v3.0, replacing
the beta code I uploaded earlier. Actually, I have
MarSOnEarth wrote:
> A brief look at the log confirms your hope/effort being realized. Two
> logs this time, the *1155 is with still with the player's output set to
> variable, and in the *1205 to fixed, all else as before. More comments
> later in DM, but so far it's all looking good. Thanks!
SamY wrote:
> Those logs look almost perfect. The only negative I can see is that
> apparently the Denon doesn't like getting volume commands telling it to
> change the volume to the setting it's already at, which can happen with
> small +/-1 or 2% changes. It doesn't both
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
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
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
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'. ;-)
> 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
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
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
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
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 --
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
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
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
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:
> 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'l
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
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 :-)
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
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
Aesculus wrote:
> FWIW on Squeezer I use both the physical volume control and the digital
> spinner. Both work well for me.
It appears that the Squeezer app is more conservative in sending
"analog" volume changes to LMS. It probably does some caching of its own
in the UI as the dial is
SamY wrote:
> It appears that the Squeezer app is more conservative in sending
> "analog" volume changes to LMS. It probably does some caching of its own
> in the UI as the dial is rotated, whereas Squeeze Ctrl seems to send
> every volume change in individual increme
Aesculus wrote:
> Note if you make changes you have to restart the LMS.
I've found through experience that, while this may be true for some of
the settings, most changes take place immediately without having to
restart LMS.
Sam
Aesculus wrote:
> I am still upset that the menu's in the Plugin don't get set properly on
> the first viewing. You have to go into the menu, see nothing has been
> set, leave and come back, or select something.
Hmmm... I never noticed that. Does it only happen the first time after
the plugin
madpatrick wrote:
> The plugin is working nicely and i learning every day how handle my new
> Denon Receiver.
>
> Is it possible to set the volume of the squeezebox at a fixed start
> level.
> Now my receiver is set to a start volume level and also the squeezebox,
> but this is too low at
MarSOnEarth wrote:
> On the one hand, I see so much of new activity here, and on the other, I
> don't get to use that particular player that's hooked up to our Denon
> often, but now I tried it after quite a while, and the power on/off
> sequence no longer works. It all used to work quite
MarSOnEarth wrote:
> This may, or may not be so, but either way, not available as an option
> (this house's backbone is all powerline), and a different conversation.
> Mine is hoping that Sam can find a way to code around such absurdly off
> numbers.
I wouldn't get my hopes up. The latest
MarSOnEarth wrote:
> Just checked, the 'install.xml' does say 2.3; so, I'm good there.
All I can tell you is that the line numbers in the debug log correspond
to v2.1 and not v2.3 so that's a mystery to me.
In any case, if you would feel comfortable doing it, I would like you to
try running
Aesculus wrote:
> So now someone needs to contact the Squeeze Ctrl author to ask them to
> pass the requests through to LMS to make this work there also.
According to the author's comment in the link I posted, there is already
an option in Squeeze Ctrl to do this. However he doesn't specify
DavidBulluss wrote:
> 100% fixed LMS volume, amp not responding to volume changes from my
> android remote app (squeezectrl) which I use to control LMS 99% of the
> time.
Looks like it's working correctly with "Volume control adjusts outputs".
However the log shows no volume change requests
Aesculus wrote:
> Do you think this is when the settings were changed on SqueezeCtrl to
> 100% volume?
I do. I believe that the app was adjusting the volume higher in a
(misguided) effort to reflect the "fixed at 100%" setting. You may have
noticed that the first volume command sent to the
DavidBulluss wrote:
> Not sure which app and/or plugin is responsible!
It's a combination of both. The plugin caches volume change requests
that are received within .25 seconds of each other in order to avoid
overloading the AVR with a continuous stream of small changes. From the
log, I can
DavidBulluss wrote:
> Log attached. I set the app to use phone vol buttons for vol adjustment.
> There is a setting for amount of volume change per press, I set that at
> 2. Doesn't all work as well as I would hope for, amp volume was adjusted
> along with LMS volume, but when I was in the 90's
DavidBulluss wrote:
> I may be best to turn of screen swiping and rely on the on screen vol
> buttons in that case.
If you end up doing that, I would be curious to see the debug log
showing what volume increment the app is sending to LMS when the up/down
buttons are pressed. Thanks.
Sam
David and MarSOnEarth:
Here is a new version of the beta code for you to try. If the client
reports its volume as 0 during power on, it will set it to 25%. This is
a temporary fix and there is actually a chance that it will work as
originally planned due to a change in how the client volume is
1 - 100 of 432 matches
Mail list logo
