cpd73 wrote:
> Most odd. Just tried in "Duck duck go" browser, and still works as
> expected for me. Which android version? And which version of WebView
> (should be able to find this in Play store)? I'm on Android 13 with
> WebView 108.0.5359.128
I'm on Android 13 with WebView 108.0.5359.128
cpd73 wrote:
> It -should- only take you back to the browse view. e.g. If You were
> browsing 'My Music / Album Artists / AC-DC', go to queue page, a
> long-press (or short) on 'Browse' should take you back to the browse
> view - which should still be showing AC-DC's albums. At least that's the
Ron F. wrote:
> I apologize for the extremely late response ... I was preoccupied with
> other things.
>
> I see this behavior on my new Pixel 6a running Android 13, APK 0.3.0. I
> fired up my old Pixel 3a running Android 12, also APK version 0.3.0 -
> and with Android 12 the "Cache will be
kidstypike wrote:
> Your screenshot shows you're on the "Home" page, a log press on the
> Browse button when you're on this page does nothing, press and hold when
> any another page takes you straight back to the "Home" page.
Yes, photo and my description may bea little mis-leading. When in
cpd73 wrote:
> Yeah, I can see that if I run in a browser. Never noticed before as I
> always use the APK. Anyhow, I'll fix this for the next release, as its a
> bit annoying! It only happens on the 'Browse' button as that uses an SVG
> for its icon.
>
> BTW, you can also click on the text in
slartibartfast wrote:
> Weird. It is letting you download or open the browse icon.
>
> Sent from my Pixel 3a using Tapatalk
The download commenced but was reported as "failed". Opening in a
browser window revealed a blank page, screencap below
39486
Cheers, David
slartibartfast wrote:
> I was using the Material APK but I just tried using Chrome and it works.
> Can you show a screenshot of what you see?
>
> Sent from my Pixel 3a using Tapatalk
I just tried using Samsung internet app and I had same result, only a
different looking browser menu for
slartibartfast wrote:
> You could be long pressing slightly above the browse icon and long
> pressing an album or artist instead. Try lower or use the "back" icon
> instead.
>
> Sent from my Pixel 3a using Tapatalk
Nup, I have tried and tried so carefully but all I get is the browser
download
w3wilkes wrote:
> Yes, the back button to My Music. Just long press it, either mouse click
> on a PC or long press on your touch device.
I must be doing something wrong, on my android phone a long press on
BROWSE just brings up a browser menu to Download the image etc. What
have I missed?
SamY wrote:
> No problem, David. Glad you are enjoying the multi-zone functionality.
> Take care.
>
> EDIT: I just looked at the debug log and it appears that the AVR power
> off is actually being initiated from the plugin in response to a player
> "power off" command from LMS approximately
SamY wrote:
> I found the following in a Denon AVR forum post. If it applies to your
> model, it could explain what you are seeing and the solution would be,
> as you said, to turn off Auto Standby for Zone 2.
>
> "The Denon manual says that in Main Zone, the Auto Standby fuction will
> switch
SamY wrote:
> I'll take a look at the log but, in the meantime, could you try changing
> the Auto Standby value to 1 hour and seeing if that changes when the
> Zone shuts off? I can't think of anything in the plugin that would cause
> the behavior.
Set to 60 minutes, still turned off and play
SamY wrote:
> I'll take a look at the log but, in the meantime, could you try changing
> the Auto Standby value to 1 hour and seeing if that changes when the
> Zone shuts off? I can't think of anything in the plugin that would cause
> the behavior.
Will reset it now and report the effect.
Hi Sam. I have noticed that after about a half hour of play the Denon
amp switched off and music play is paused when using Z2. Controlling via
MS on android. If Z1 is also on then Z2 shuts off and Z1 remains on.
Touching PLAY on the MS interface turns the amp back on and it reverts
to my preset
SamY wrote:
> Your debug log looks fine, David. The network response time between the
> plugin (LMS) and the AVR seems to be very good also. I would suspect a
> response lag between MS and LMS, but I have no means of verifying that
> from the log file. Is the MS client running on your phone or
Hi Sam, I have been noticing the slide up/down volume interface when
using MS very jumpy and sometimes non-responsive then it jumps to a
different volume. I have increments set at 2%, could possibly just be
lag in my system? All while using Denon receiver. Have attached a debug
in case you feel
SamY wrote:
> And... it works!! Just tried it out and, after pausing the player and
> waiting 15 minutes (value used for testing purposes), it turned off the
> player, thus triggering the Denon plugin to power off the AVR. This is
> really a nice feature because the Denon plugin will only power
mctr wrote:
> Here's a strange error I'm getting. Seems to happen when I power off my
> Squeezelite and thus Marantz AVR while something is playing. As far as I
> can tell if I stop playing first, it doesn't happen.. Errors starting at
> line 43 and repeats endlessly, I am having to kill the
SamY wrote:
> Glad to hear. Here's a little tip for you. Go into Material Skin's
> "Settings->Player" menu while your Denon player is active and scroll to
> the bottom where you should see the "Denon/Marantz AVR Settings" menu
> option. Press and hold that option for a second or so and it will
SamY wrote:
> No. It works great for me, as I said before. You probably need to set
> Material Skin's "Fixed volume players" plugin option in "Server
> settings/Plugins/Material Skin" to "Display standard volume control",
> which is documented in the Denon AVP/AVR Control plugin's wiki pages,
>
SamY wrote:
> Good idea. However, if you like the swipe up/down volume control method,
> you should check out the Material Skin app/plugin. It has the smoothest
> implementation of it that I have seen. I encourage you to give it a try.
Hi Sam, I am using the V4.7 of Denon plugin still, and
SamY wrote:
> Good idea. However, if you like the swipe up/down volume control method,
> you should check out the Material Skin app/plugin. It has the smoothest
> implementation of it that I have seen. You have to both install the
> plugin and side load the Android control apk to use it, but
SamY wrote:
> Okay, David. It sounds like everything is working as expected. I also
> have observed the behavior you're seeing with Squeeze Ctrl but I can
> assure you it has nothing to do with the plugin. You might want to
> download the Squeezer app for comparison. If you do, you'll notice
SamY wrote:
> Sounds good. Did you get the "Power on volume" for Zone2 set up and
> behaving the way you want?
I haven't had a very long testing session yet, access to Z1 of the Denon
has been limited due to it being wet here and others deciding they want
to use it!
In the brief sessions that
SamY wrote:
> Just want to make sure you saw the edit to my previous post, David.
Yes, pretty sure it wasn't me, have checked my download folder and both
files were downloaded. I have deleted the .txt from both and installed,
but haven't had a decent chance to test properly yet, maybe later
SamY wrote:
> I didn't say that, David. I said you can do it on *_Zone_2_*, as shown
> in the manual. You just have to find the right menu. Do you have the
> manual? If not, it's easy to find online.
>
>
>
> Congratulations! You found one of the bugs fixed in the next revision,
> which is
SamY wrote:
> David, I can assure you that the initial volume for Zone 2 can be set in
> the menu of your AVR-X3000. Below is a portion of page 173 of the
> manual, which specifically documents the Zone 2 audio settings. As I
> said, the Quick Select settings have nothing to do with it. Once
SamY wrote:
> Upon further reflection, I will not be changing this behavior. Just set
> the Denon's Zone 2 "Power On Volume" according to your liking. Note that
> it can be set to "Last", meaning where it was set when it last powered
> off, which is what I would recommend in your situation. You
SamY wrote:
> You did something wrong but the server log is not helpful. Check that
> you correctly renamed Plugin.pm.txt to Plugin.pm (case sensitive) in the
> plugin directory. If you can't spot the problem, send me a "ls -l"
> output of the directory contents. In the meantime, you can test
SamY wrote:
> The volume controls in the Squeeze Ctrl app should control the volume of
> whichever AVR zone is currently selected. My bet is that you have
> forgotten to turn on the rather cryptically named Squeeze Ctrl settings
> option "Preferences->Controls->Volume Options->Fixed Volume Send
SamY wrote:
> It sounds as though you don't have the player's audio settings set
> correctly. See the notes from my previous post:
>
> > > >
- The player's "Volume Control" LMS Audio option must be set to
> "Output level is fixed at 100%" for the Zone menu to appear.
> > >
> This
DavidBulluss wrote:
> Intalled and ready to try it out but it may be tomorrow before I can.
>
> Cheers, David
Have just manage a quick play. I commenced with the receiver turned off
for both Z1 & Z2. I am using Squeeze-CTRL. I navigated to settings -
Denon/Marant
SamY wrote:
> Here it is, David (and anyone else who is interested). As usual, copy
> the attached perl modules into the DenonAvpControl plugin directory
> after renaming the old ones, e.g. Plugin.pm->Plugin.pm.save, and restart
> LMS. Oops! The Plugin.pm file is too large. I had to rename it
y testing using my Denon
> AVR-3311ci. However, I currently have no secondary zones set up. Since a
> few users have requested this feature in the past (I'm looking at you,
> @DavidBulluss), I am hopeful that one or more of you might be willing to
> assist with the testing effort. Whi
SamY wrote:
> Hi, David! It's been awhile since you've posted here. Glad you're still
> finding the plugin useful and thanks for mentioning Squeeze Ctrl as
> another client app that supports the AVR Settings menu, although its
> inability to handle slider controls means that the Channel Level
>
SamY wrote:
> Thanks for the positive feedback, @SMC. It is greatly appreciated.
> Sometimes it feels as though Chris and myself are the only ones who use
> the plugin, especially when it comes to the Audio Settings menu
> functions. I'm happy to hear that you are taking advantage of the
>
Hi again, it still failed using cache but then persistent mode appears
to work. Thanks both for your help.
Cheers, David
Paul Webster wrote:
> Settings/Advanced/Network/Streaming Mode For HTTP(S)
>
> However, you need a relatively recent (1 year?) LMS for the option to be
> available.
Hi Paul, thanks for that. Have found the setting and I have gone Cache
initially, now to go and try it out!
Cheers, David
Paul Webster wrote:
> Settings/Advanced/Network/Streaming Mode For HTTP(S)
>
> However, you need a relatively recent (1 year?) LMS for the option to be
> available.
Hi Dennis, thanks for your help on this. What you say makes a lot of
sense. Is the serversettings ---> network within LMS settings? I have
looked through most of the obvious pull downs and can't find it. If you
wouldn't mid pointing me more precisely in the right direction that
would be
Hi Paul. I have only just installed mixcloud plugin and I am
experiencing a glitch. I installed it via LMS Settings - Plugins and
selecting then saving & restarting. I then followed link to API key
which I copied and pasted in to Settings - Advanced - Mixcloud and
saved. Glitch is that podcasts
SamY wrote:
> Absolutely! Quote away! ;-)
>
>
>
> Just to be clear, the slider controls do not work correctly on Squeeze
> Ctrl with any zone. For players using volume fixed at 100%, this affects
> only the Channel Level Adjustment controls. For those using variable
> volume level, it also
SamY wrote:
> Ha ha!! That's exactly what I would have done, David. "Whatever you do,
> don't press the red button!".
>
> Chris and I have not been successful in getting the Squeeze Ctrl
> developer to look into the problem but, if you want to take a look at
> how the slider controls are
SamY wrote:
> V4.4.1 of the plugin is now available.
Thanks Sam, updated and the Zone 2 Quick Select works very well. Just an
aside, as you told me that the Channel Level Adjustment and Preamp
Volume does not work with Squeeze CTRL for Zone 2 I just HAD to try it.
Nil effect on Channel Level,
SamY wrote:
> No need for a log file, David. I was able to recreate the problem here.
> I also found and fixed a few other minor bugs in secondary zone menu
> processing that will be in the next release. I'm assuming you have
> discovered that the menu Preamp Volume and Channel Volume
DavidBulluss wrote:
> Whoops, certainly did miss turning logging on! Would it help if I
> uploaded a real log file? Thanks for the tip on the Song Info plugin. It
> generally behaves but every now and then it has no info, usually on
> obscure tracks.
>
> Cheers, David
Debug
SamY wrote:
> David, if you would like to have it before then, let me know and I will
> upload the changed modules.
>
> P.S. I think you forgot to turn debug on for the Denon plugin
Whoops, certainly did miss turning logging on! Would it help if I
uploaded a real log file? Thanks for the tip
Aesculus wrote:
> I have not looked at the log yet so it may be clear in there. I'll let
> SamY handle that. It may be a quirk wrt the Zone.
>
> If you manually save the QS on the Denon (on my old AVP I just press and
> hold the QS button until the display changes) does it show on the
>
Aesculus wrote:
> Dave: When you press the Save Current Audio Settings can you look at the
> Denon and see if you get a message on that screen that says it's saving
> the Quick Select? It's pretty quick so you need to be in front of it
> when you make the selection on the phone.
Nothing on the
Hi Sam, I am using Squeeze Ctrl on android and am finding that during
play I have increased the Denon volume diectly using remote or other
means from 64 to 75 or so then gone to SETTINGS in Squeeze Ctrl, then
DenonAvpAvrControl, Quick Select, and selected Save Current Audio
Settings. Msg appears
Michael, TIDAL is working beautifully with DSTM. And not a Sptify track
in sight! You are brilliant, thank you very much.
Cheers, David
*Server*rpi3 pCP8.1.0 LMS8.2.0
*Media*USB hard drive
*Lounge/dining areas*SBT > Denon AVR2113 > Bose Acoustimass10 / Krix
Seismix3 18" 300w RMS custom
mherger wrote:
> > Is there anywhere that I need to go to to change settings in LastMix
> so
> > that it picks from TIDAL?
>
> No. It would use the first music service available, with lossless being
>
> preferred over lossy. So even if you had Spotify and TIDAL enabled, the
>
> latter should
mherger wrote:
> use the LastMix plugin to create the mix.
Brilliant, I didn't think of that. I have been using LastMix with DSTM
since you created the plugin quite a while ago now. I have the "LastMix
- Don't Stop The Music support using Last.fm box selected in DSTM.
Is there anywhere that
>From what I can see DTSM does not have an option to include TIDAL as it
does with Spotty. Just checking that my conclusion on this is correct
before I give up on the idea. Anyone able to enlighten me?
Cheers, David
*Server*rpi3 pCP8.1.0 LMS8.2.0
*Media*USB hard drive
*Lounge/dining
SamY wrote:
> Okay, here it is. The attached beta plugin files implement the ability
> to update the active AVR Quick Select definition from the client plugin
> menu using the current audio settings. The specific settings that are
> saved with the Quick Select definition seem to vary with
SamY wrote:
> I think I know what's happening with your settings, Giunti. Most of the
> audio settings found in the plugin menu, including the restorer mode,
> are part of the Quick Select definition. Therefore, every time you
> invoke the QS 2, such as when starting up the LMS player, the
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
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
SamY wrote:
> Hi, Patrick. Chris and I have both been pretty busy lately but I wanted
> you to know that this feature has been coded and tested, and will be in
> the next release of the plugin. Thanks for the suggestion.
Sam & Chris, you have been doing an amazing job with this plugin, really
SamY wrote:
> 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.
When moving the "party" completely from Z2 to Z1 I do use the remote to
turn Z2 off.
SamY wrote:
> One more question, David. When you are listening in Z1, what do you do
> about the fact that Z2 is also on? Do you just let it play out there too
> or do you mute it, either in the app or using the Denon remote?
It depends on circumstances at the time. Sometimes I let them both
SamY wrote:
> Coincidentally, however, another plugin user made an enhancement request
> just yesterday to allow for this situation to be supported. The way it
> would be done is to allow for switching zones on the fly via the client
> app menu. So, in your scenario, if you were listening to
SamY wrote:
> At the risk of being redundant...
>
> Running with the Zone 2 LMS player output level set to 100% does not
> mean that you lose the ability to set the Zone 2 AVR volume from your
> LMS client app. And it has absolutely no effect on your main zone
> settings. On the contrary, it
Aesculus wrote:
> But one thing that could possibly be done is to put a menu item in the
> plugin that boosts up (or down) the current Denon volume, but only for
> that session. This would work the same way as you picking up the Denon
> remote and making that change for that Zone. And when the
Aesculus wrote:
> I would think then that the new method in 4.1 that only uses the LMS
> volume would be best then. Before we had two volume reductions going on.
> Now you only have the one.
>
> So in theory your volume with 4.1 set on variable should allow for a
> louder overall volume with a
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
Aesculus wrote:
> @SamY and I have have posted a new beta for version 4.1
>
> https://github.com/aesculus/denonavpcontrol/blob/master/src/DenonAvpControl_4_1.zip
>
> The biggest change in this version is turning off sending volume control
> functions to the Denon AVP/AVR if you are not using
SamY wrote:
> The log looks good, David! Did everything seem to perform as you
> expected? I wonder if you had a chance to try the "double pause" Quick
> Select maneuver? A good way to demonstrate its usefulness is to switch
> the AVR to a different input while you are listening to music and
SamY wrote:
> 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.1 beta.
Just for comparison of the latest 4.1 beta that I downloaded from Github
here is a simple
SamY wrote:
> It's a little hard to see it in the debug log due to all the YouTube
> plugin errors but your Quick Select is still timing out, David. As an
> experiment, try changing the Zone 2 input to something other than your
> Squeezebox player and then turn the AVR off before powering on
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
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
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.
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
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 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. ;-)
>
>
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
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:
> 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:
> 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:
> 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.
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
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 work
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
ot better :o). I have
> changed the Quick Select timeout value to 5 seconds and uploaded the
> current (and hopefully final) version of both changed modules. Thanks
> once again to DavidBulluss and MarSOnEarth for your help and cooperation
> in testing the code changes.
Thank you for
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
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.
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
>
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
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:
> 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
SamY wrote:
> 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
Aesculus wrote:
> @SamY and I have completed our updates to version 3.0 and it has now
> been posted on GitHub.
>
> Look for it in the LMS Settings>Plugins tab over the next six hours or
> so.
Have update to V3.0, will let you know if any issues.
Cheers, David
*Server*rpi3 pCP5.0.1
SamY wrote:
> 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
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 :
SamY wrote:
> Thanks, David. The debug log is very helpful. Unfortunately, the Squeeze
> Ctrl app is letting me down again. For some reason, it is setting the
> client volume to 0 during the "power on" sequence so that is the value
> that the plugin retrieves and uses to synchronize the AVR
DavidBulluss wrote:
> Loaded in, restarted, and... off for some testing. Then I will do the
> log and sent it to you.
>
> Regards, David
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
sudd
SamY wrote:
> Please generate a debug log of a power on followed by playing some
> music, adjusting the volume, and a power off.
Loaded in, restarted, and... off for some testing. Then I will do the
log and sent it to you.
Regards, David
*Server*rpi3 pCP5.0.1 LMS7.9.2
*Media*USB hard
SamY wrote:
> 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 changes I've been working on with regard to
> secondary zone support. Before I move on to the next coding
SamY wrote:
> Oops! Not sure what happened there, David. Maybe the plugin was updated
> during that time but, if that were the case, it should have overlaid the
> new files too. I guess the safest thing to do is to copy the old files
> somewhere else. If you ever need to go back to an older
1 - 100 of 315 matches
Mail list logo
