Announcement
Collapse
No announcement yet.
Announce: Material Skin
Collapse
X
-
That's not a bug per se - it's intentional. There is no way I'm going to support the multitude of track formats the web UI supports. However, I guess I could check if TRACKNUM is in the format, and use, otherwise don't. Currently disc number is not used, so probably need to support that too (again by checking if its used).
Sent from my SM-G900F using TapatalkLiving Room: Touch or Squeezelite (Pi3B) > Topping E30 > Audiolab 8000A > Monitor Audio S5 + BK200-XLS DF
Bedroom: Radio
Bathroom: RadioComment
-
Material debug: 1. Launch via http: //SERVER:9000/material/?debug=json (Use http: //SERVER:9000/material/?debug=json,cometd to also see update messages, e.g. play queue) 2. Open browser's developer tools 3. Open console tab in developer tools 4. REQ/RESP messages sent to/from LMS will be logged here.Comment
-
Living Room: Touch or Squeezelite (Pi3B) > Topping E30 > Audiolab 8000A > Monitor Audio S5 + BK200-XLS DF
Bedroom: Radio
Bathroom: RadioComment
-
Living Room: Touch or Squeezelite (Pi3B) > Topping E30 > Audiolab 8000A > Monitor Audio S5 + BK200-XLS DF
Bedroom: Radio
Bathroom: RadioComment
-
Material debug: 1. Launch via http: //SERVER:9000/material/?debug=json (Use http: //SERVER:9000/material/?debug=json,cometd to also see update messages, e.g. play queue) 2. Open browser's developer tools 3. Open console tab in developer tools 4. REQ/RESP messages sent to/from LMS will be logged here.Comment
-
I'm running Material 0.1.0 against a couple of SB Classics that have their volume controls fixed at 100% in LMS.
(I control the volume via my stereo using the IRBlaster plugin that issues Volume up/down infrared to stereo when LMS receives Volume up/down commands)
Under Material this works fine in the Manage Players dialog screen. The volume bar sits at 100%, but I can still volume up/down and the commands go through to LMS (and therefore IR blaster)
On the Volume Pop-over (?) dialog screen, the volume bar sits at 100%, I an do a volume down and it goes through to LMS, but the volume ups don't appear to work. Maybe there's slightly different volume up handling code in there than your Manage Player dialog, but it's as if the Volume Up is not being issued if volume is at 100%.
Is it possible to change these so it's the same as volume handling on Manager Players?
Thanks.Comment
-
Sent from my SM-G900F using TapatalkLiving Room: Touch or Squeezelite (Pi3B) > Topping E30 > Audiolab 8000A > Monitor Audio S5 + BK200-XLS DF
Bedroom: Radio
Bathroom: RadioComment
-
Material debug: 1. Launch via http: //SERVER:9000/material/?debug=json (Use http: //SERVER:9000/material/?debug=json,cometd to also see update messages, e.g. play queue) 2. Open browser's developer tools 3. Open console tab in developer tools 4. REQ/RESP messages sent to/from LMS will be logged here.Comment
-
Comment
-
I'm running Material 0.1.0 against a couple of SB Classics that have their volume controls fixed at 100% in LMS.
(I control the volume via my stereo using the IRBlaster plugin that issues Volume up/down infrared to stereo when LMS receives Volume up/down commands)
Under Material this works fine in the Manage Players dialog screen. The volume bar sits at 100%, but I can still volume up/down and the commands go through to LMS (and therefore IR blaster)
On the Volume Pop-over (?) dialog screen, the volume bar sits at 100%, I an do a volume down and it goes through to LMS, but the volume ups don't appear to work. Maybe there's slightly different volume up handling code in there than your Manage Player dialog, but it's as if the Volume Up is not being issued if volume is at 100%.
Is it possible to change these so it's the same as volume handling on Manager Players?
Thanks.
Basically, if I'm understanding correct - you want volume up to be send even if volume is 100% Do ANY other controllers allow this? This seems like an invalid scenario.
[Edit] I've now fixed the bug in the manage players dialog (for the next release). But, this is the opposite of what you want. I can change it so that volume is sent past 100%, but not sure this is really a valid scenario.Material debug: 1. Launch via http: //SERVER:9000/material/?debug=json (Use http: //SERVER:9000/material/?debug=json,cometd to also see update messages, e.g. play queue) 2. Open browser's developer tools 3. Open console tab in developer tools 4. REQ/RESP messages sent to/from LMS will be logged here.Comment
-
Sorry, what? (Its late at night here - so perhaps I'm being a bit thick...) Material shows the volume as 100%, but you want it to then also do a volume up? That makes no sense. I see that there is a bug in the manager players dialog, where it is checking the wrong setting - so sending the volume up where it should not.
Basically, if I'm understanding correct - you want volume up to be send even if volume is 100% Do ANY other controllers allow this? This seems like an invalid scenario.
[Edit] I've now fixed the bug in the manage players dialog (for the next release). But, this is the opposite of what you want. I can change it so that volume is sent past 100%, but not sure this is really a valid scenario.
The default Logitech player web-interface always sends a Volume-up command even when the Classic volume is set at 100% - but the web display always shows the volume bar full to 100%.
So, as per your Edit - I need a volume up command to be issued, even when we're at 100%. Probably don't want to change the % that is displayed (it will probably return to 100% anyway next time you retrieve the current volume from the player - it does this if I turn the volume down via Material, the displayed volume % will drop, but after 0.5 seconds it will return to being displayed as 100% as I assume it gets refreshed/retrieve from the player's current volume setting.)
Thanks.Comment
-
Thanks!
Just adding my name to the list of folks who appreciate all the work you have done on this. It looks great, and I eagerly await updates, THANKS!Location 1: ReadyNAS Ultra 2 4TB > RPi3 > piCorePlayer > LMS 7.9.2 > Squeezebox Touch >NAD 326BEE > BeoLab 4000
Location 2: Squeezebox Touch, Audio Engine A2+
Controller: Asus Tablet > Orange Squeeze
Music: Ripping (FLAC) dbpoweramp, Tagging: mp3tagComment
-
Sorry, what? (Its late at night here - so perhaps I'm being a bit thick...) Material shows the volume as 100%, but you want it to then also do a volume up? That makes no sense. I see that there is a bug in the manager players dialog, where it is checking the wrong setting - so sending the volume up where it should not.
Basically, if I'm understanding correct - you want volume up to be send even if volume is 100% Do ANY other controllers allow this? This seems like an invalid scenario.
[Edit] I've now fixed the bug in the manage players dialog (for the next release). But, this is the opposite of what you want. I can change it so that volume is sent past 100%, but not sure this is really a valid scenario.
Essentially what this means is that even though some players have a volume fixed to 100%, incremental volume commands still work on them
You won't know that's player's real volume in this case.---
learn more about iPeng, the iPhone and iPad remote for the Squeezebox and
Logitech UE Smart Radio as well as iPeng Party, the free Party-App,
at penguinlovesmusic.com
New: iPeng 9, the Universal App for iPhone, iPad and Apple WatchComment
-
Announce: Material Skin
>> Music & Artists Info plugin: when I use the "other" menu option for a
>> track in the queue list, I see an option to access local text files, as
>> expected. However, attempts to access both .txt and .html files throw
>> this error: "I'm sorry, this file type is not supported on your device."
>> Pdf files seem to work, though.
>
> Michael: Any idea what's wrong here? How do I inform MAI that text and
> html files are acceptable?
It might be a MAI issue. I do have some code there trying to figure out
whether the controller application can handle web links or not. This
might be failing here. I'll look into this.
--
Michael
Michael
"It doesn't work - what shall I do?" - "Please check your server.log and/or scanner.log file!"
(LMS: Settings/Information)Comment
Comment