philippe_44 wrote:
>
> It's a bug in LMS where negative volume ended-up being reverted. As you
> can see below, there is no protection in the look-up table to negative
> volume. I've submitted a PR
Wow! That was quick. I just installed the new 8.1.2 nightly build and
tested your fix. It
philippe_44 wrote:
> Trying to still have a life...
>
> It's a bug in LMS where negative volume ended-up being reverted. As you
> can see below, there is no protection in the look-up table to negative
> volume. I've submitted a PR
I apologize for my impatience, Philippe. ;-) Thanks for the
Is this thread still active? Philippe?
Sam
SamY's Profile: http://forums.slimdevices.com/member.php?userid=63495
View this thread: http://forums.slimdevices.com/showthread.php?t=104614
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
There seems to be a problem with squeeze2cast handling the LMS muting
function. A "mixer muting" CLI command results in the volume being
incrementally decreased from its current value down to 0 using
CastSetDeviceVolume, which is fine. However, it then immediately follows
that with another
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
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
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
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
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
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
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
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
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 --
> 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:
> 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'. ;-)
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
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:
> 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:
> 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:
> 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:
> 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:
> 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:
> 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
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!
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:
>
> ... 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:
> 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:
> It's all looking good here, Sam; the on/off commands work reliably now,
> and so are the volume changes.
Glad to hear that.
> ...the AVR displays "-3dB" (the hard limit that's been set), and all the
> volume changes are under software (your plugin) control. I'm guessing
>
MarSOnEarth wrote:
> Here it goes,
> Thanks
Okay. So the AVR volume synchronization with the client at power on is
now working properly. That is good news. However, all of the volume
change commands sent to your AVR continue to time out which, as I said
before, is not necessarily a problem in
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
DavidBulluss wrote:
> Squeezer works quite nicely, but turning on the zone 2 volume sets at 0
> still.
Yep. I can see that in the log file. I'm not sure why it happens with
your system (and with MarSOnEarth too) but not with mine. Maybe it's
something specific to running with a non-main zone.
MarSOnEarth wrote:
> Hi Sam,
>
> Here are my results.
>
> Thanks
Well that's a "good news / bad news" scenario if I ever saw one. The
good news is that the response times for everything except the volume
changes are dramatically improved, presumably due to the AVR reset.
However, every one
DavidBulluss wrote:
> Log file attached. What I have noticed is that when first turned on and
> track played that there is no volume. Turning up volume brings it
> suddenly to life and volume is probably as it was when last played
> before being turned off. No waking of neighbors :-) The other
MarSOnEarth wrote:
> Hi Sam, I've been timing things out after resetting my AVR. Here are a
> few data points with your newest code:
> >
Code:
> > P-off: 1.1926 P-on: 0.1833
> 1.0956
MarSOnEarth wrote:
> Hi Sam, I've been timing things out after resetting my AVR. Here are a
> few data points with your newest code:
> >
Code:
> > P-off: 1.1926 P-on: 0.1833
> 1.0956
DavidBulluss wrote:
> It would be a pleasure, bring it on! Very happy to test the beta.
>
> Cheers, David
Okay, David. Here you go. As I mentioned before, this intermediate
release does not actually contain support for the Quick Select command
in secondary zones but there are significant
madpatrick wrote:
> SamY,
> If needed im willing support with testing.
> Ive not yet setup different zones but maybe it helps with the quick
> select function.
> Since ive just a few days the receiver, im still learning all
> functions :)
Thanks. I'll let you know. The pr
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
DavidBulluss wrote:
> Yep, the next time I was replacing the files with the beta ones I saved
> them elsewhere as a backup :-)
Hey David. I have a question. Now that you know to back up your plugin
files in a safe place when beta testing :), I wonder if you would be
interested in testing some
MarSOnEarth wrote:
> Thanks, and glad to do it. Two server logs; they are both of just power
> on/off commands from my desktop (W10P, FF w/ Material UI), though I also
> use Material app on Android (10) phone. The second (+net) log also
> includes debug from network.asynchttp. Hope you find it
DavidBulluss wrote:
> Interesting that you suggested to rename the old files. That was also
> what I did before placing the new files into the folder on the
> assumption they would still be there if I needed to revert. Next time I
> looked the renamed files had disappeared!
>
> Cheers, David
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
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
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
Oh. Okay. That whole part of the plugin code is a black box to me as the
only Apple products I have ever owned were an Apple II (actually two of
them) and an iPod Touch 4th gen. I still have the iPod in a drawer
somewhere. Maybe I should give it a charge and see if it will run iPeng.
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
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
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:
> 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
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
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
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:
> I just gave the Squeeze Ctrl settings as suggested a run... volume
> jumped straight up to 100% (wishing now I had tweeked the limit to -10!)
> and interestingly when I tried to turn it down it seemed to affect the
> LMS volume marginally and took it down to 93%. I didn't
DavidBulluss wrote:
> Thanks for the heads up about Squeeze Ctrl behaviour, will just continue
> with "volume control adjusts outputs", I probably had worked out years
> ago that it didn't work with "fixed at 100%"
Sounds good. Alternatively, you could use the Squeeze Ctrl preferences
option
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
DavidBulluss wrote:
> ALmost deaf now! LOL The new Plugin.pm caused the amp volume to be
> adjusted but unfortunately as I still have vol fixed at 100% in LMS it
> took the amp straight to 100% and kept it there! I will change the LMS
> setting so that the volume is controlled and see how that
DavidBulluss wrote:
> Short answer is no I did not have LMS vol fixed at 100%. I have now set
> it to be fixed at 100% and run a debug log. Amp volume did not adjust.
Thanks, David. I see the problem. Attached is a new version of Plugin.pm
that should take care of it. Unfortunately, the
Aesculus wrote:
> Once you get that done and tested I suggest we call it 3.0 and wrap it.
> I am already poised for that as the latest version is running in my
> system as 3.0. :-)
After spending some time looking at the code last night, the changes
required for supporting quick select in
DavidBulluss wrote:
> Nothing untoward has popped up in my trials, seems all good!
Glad to hear that, David. Maybe I'll go ahead and start on quick select
support for zone 2 & 3 to make things more "interesting". If so, I'll
need your help in testing it as I only have one zone set up at the
At the risk of jinxing it, I have not experienced even the slightest
hiccup in my testing of the latest code drop (the sound you hear is me
knocking on wood). In fact, after spending so much time coding and
debugging over the previous week or two, I'm getting bored. I see that a
few people have
Slash303 wrote:
> Does this plugin also work if my PiCore player is outputting audio
> through HDMI?
It certainly should, as long as the other end of that HDMI cable is
connected to one of the inputs of a network-capable Denon or Marantz
AVR. Give it a try!
Sam
Aesculus wrote:
> Nope. Seems to work fine for me.
I have uploaded what I hope will be the final updates for v3.0. The
changes from the previous version are minor:
1. Incorporate updates to the copyright info and change log
2. Remove the enforcement of a minimum 1 sec delay before power on
Aesculus wrote:
> I set it to 3 seconds and that worked. Good enough for me.
Ok. The fact that a 1-second delay works for my 11-year-old AVR should
mean that it will be fine for most users. Have you had any other
problems since installing the new changes?
Sam
Hey, Chris. Have you had a chance to run any tests using lower quick
select delays to see what the minimum value is that works for you? Or do
you think that we should just go ahead with enforcing a minimum of 1
second in the code and assume that your case is an outlier? I could see
going either
Aesculus wrote:
> Another successful fix without a line of code being changed. :-)
Lol!! Yeah. We're getting pretty good at this, huh?
Sam
SamY's Profile: http://forums.slimdevices.com/member.php?userid=63495
View
DavidBulluss wrote:
> I do use other sources from time to time on that zone but not regularly.
> Probably not a priority, but if you do want to give it a go I am more
> than happy to beta test.
Sounds good, David. Thanks.
Sam
DavidBulluss wrote:
> Bingo! An overlooked setting on that amp, but for some reason I had it
> correct on the other amp! Thank you very much for sorting that one out
> for me, very much appreciated. One less life aggravation to put up with!
> LOL
>
> Cheers, David
Glad to help. Now the
DavidBulluss wrote:
> I hope the attached file is the correct one!
>
> David
>
> file:///E:/Downloads%20E/server.log(3).zip33608
The receiver is not responding to a request for the power status of the
Zone 2 amp. Since the plugin does work if the receiver is already turned
on, and powers it
cjfreitag wrote:
> Figured it out! The IP address on my receiver had changed by one digit
> and so the plugin setting wasn't working. Changed the IP setting and it
> is working again. I suppose what I will need to do is assign the AVR a
> static IP address so this doesn't happen again.
Sam
cjfreitag wrote:
> Since moving to 2.3 the plugin has stopped working for me. I've tried
> enabling/disabling the plugin in individual players as well as
> disabling/enabling the plugin altogether.
>
> Any suggestions for other things to try?
What exactly is happening? No functionality at
Is there anyone out there who has a need for using the Quick Select
function in a zone other than the main zone? If so, would you be willing
to be a beta tester for this feature? The code changes should be minimal
but I thought I'd check to see if there is a need before spending any
time on it.
Aesculus wrote:
> This would require a UI change.
I did a quick test of the plugin menu and it seems to accept selecting a
Quick Select for zones other than the Main Zone, although it would be
ignored in the runtime code. What sort of UI change would be required?
My biggest concern is how the
Aesculus wrote:
> AVP-A1HDCI is a preamp only and was made in 2008. There was a hardware
> upgrade that was installed in 2012 that added 3D video and extra Audessy
> support.
>
> And yes, I never even noticed (or cared) about the QS setting volume
> before. You made me look. :-)
>
> I'll
Aesculus wrote:
> Must have missed that. Debug2.txt is what you asked for. Debug3.txt is
> an experiment where I set the QS delay to 10 seconds from 1 second.
>
> You will notice the QS volume is correct in Debug3.txt. So the answer
> appears to be that the logic (or slow processor) in my AVP
> None of the D+M Android apps will connect to my AVP. Probably too old.
Wow. That's weird.
> I am not sure what log you are requesting? I captured the debug when I
> did the power on test that you looked at up thread that you spotted the
> -40 on.
I asked for another debug of the power on,
My AVR works exactly like that, as do all of them as far as I know. What
you are seeing is exactly what is supposed to happen except that the
volume setting on your AVP for some reason is not being set correctly by
the MSQUICK1 command. In your test, the plugin correctly synched your
player
Aesculus wrote:
> After everything is fired up both the front panel and Denon remote will
> cause the volume to go to the correct level (-40 in my case) for the
> Quick Select the Touch is assigned to.
>
> Here are the logs:
Well, that's strange. According to the log, everything looks
SamY wrote:
> No. In fact, that's one of the issues that the new changes are supposed
> to correct. Can you send me a debug log of the "power on" process?
> Thanks.
I reread your post and my previous statement is not fully accurate. This
really has nothing to do with the plu
Aesculus wrote:
> I tested all of this and it seemed to work well. Of course some of it I
> cannot attest to because I did not observe the problems before.
>
> I do have one question: My AVP has a default On volume of -30. My
> Quick Select for the Touch is set to -40. When my device powers
Aesculus wrote:
> Mine updated too.
>
> Don't look for any changes since 2.1 :-)
Mine also updated this morning.
Sam
SamY's Profile: http://forums.slimdevices.com/member.php?userid=63495
View this thread:
Aesculus wrote:
> Version 2.3 posted and should (hopefully?) resolve the issues.
Sorry to be the bearer of more bad news but LMS won't load the new
version. Now I get the following log message when I try to upgrade:
Code:
[21-02-25 22:12:20.1978]
Aesculus wrote:
>
> And look how quick I was to fix the Zone issue. :-)
Sam
SamY's Profile: http://forums.slimdevices.com/member.php?userid=63495
View this thread: http://forums.slimdevices.com/showthread.php?t=60114
cjfreitag wrote:
> The solution was for me to stop being an idiot! It was working properly
> all along. I am not usually in the room where the receiver is when only
> Zone 2 turns on, and I didn't realize that the receiver SEEMS to be
> starting the main zone before starting Zone 2. But in fact
cjfreitag wrote:
> Got the Zone 2 issue sorted out.
>
If you don't mind my asking, what was the solution?
Sam
SamY's Profile: http://forums.slimdevices.com/member.php?userid=63495
View this thread:
cjfreitag wrote:
> Got the Zone 2 issue sorted out. Now I am having a different problem. I
> keep getting prompted to update the plugin (I have 2.1 installed). I got
> to settings, enable the 2.2 version, click apply, restart the server,
> and...get the prompt to update the plugin to 2.2.
>
>
Aesculus wrote:
> Confirmed that Version 2.2 appears. :-)
Hey, Chris. I'm having a problem with Version 2.2. It doesn't show up
on my plugin list but it is installed. However, it is re-installed every
time I restart LMS. Here is a portion of the LMS startup log with INFO
debugging turned on
Aesculus wrote:
>
> I'll look at from any UI changes that may be required but it sounds
> pretty transparent. Maybe just adding the new features to the
> repository.
Sounds good. The only UI changes I can think of would be to enforce the
minimum of 1 second for the delays and to add an option
Aesculus wrote:
> Confirmed that Version 2.2 appears. :-)
I guess that means it's time for 2.3, eh, Chris? ;-)
Seriously, I am ready for beta testing of the changes I have been
working on which I outlined previously. Here is a short list:
1. Synchronize the volume of the player client to the
Aesculus wrote:
> Confirmed that Version 2.2 appears. :-)
Sam
SamY's Profile: http://forums.slimdevices.com/member.php?userid=63495
View this thread: http://forums.slimdevices.com/showthread.php?t=60114
301 - 400 of 432 matches
Mail list logo
