Announcement
Collapse
No announcement yet.
Announce: Material Skin
Collapse
X
-
Living Room: Touch or Squeezelite (Pi3B) > Topping E30 > Audiolab 8000A > Monitor Audio S5 + BK200-XLS DF
Bedroom: Radio
Bathroom: Radio -
I deleted the browser cache and cookies.
Now it works on my Android phone and on my pc with ms edge.
But curiously it doesn't work with the Brave (chrome) browser.
But the 'add' button now works with Brave (chrome), only the 'play' button doesn't work yet.Comment
-
Hi, Is it possible for the Android App to be visible in Android Auto? I gather it would just use the normal USB out on the phone to send the audio via the player app. So LMS would just be the controller.
ThanksComment
-
I am trialling using an older iPad as a controller but mostly as a 'Now Playing' kiosk type display.
This is probably documented somewhere but I can't find it - is there way to fix the expanded now playing view to always use the side by side approach:
​
Rather than the top to bottom view (there there is a smaller album image, that then the artist/album/song info underneath it in much smaller version) - it seems to randomly swap between the two views and I can't work out why or get it to swap from one to the other.
Many thanks for your help!Comment
-
I am trialling using an older iPad as a controller but mostly as a 'Now Playing' kiosk type display.
This is probably documented somewhere but I can't find it - is there way to fix the expanded now playing view to always use the side by side approach:
Rather than the top to bottom view (there there is a smaller album image, that then the artist/album/song info underneath it in much smaller version) - it seems to randomly swap between the two views and I can't work out why or get it to swap from one to the other.
Many thanks for your help!
Server - LMS 8.4.0 RPi4B 4GB/NanoSound ONE case/pCP 8.1.0 - 75K library, playlists & LMS cache on Sata SSD (ntfs)
Lounge - DAC32 - AudioEngine B2
Office - RPi 3B+/HiFiBerry DAC HAT/RPi screen - Edifier D12
Bedroom - Echo Show 8
Spares - 1xSB Touch, 1xSB3, 4xRPi, AVI DM5 speakersComment
-
Commands look fine to me. I suggest you do some digging to see why LMS does not accept the album command.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
-
Material set to "All", player set to another library view, single track plays, Album doesn't appear to do anything.
If I set the Default or Classic skin to "All", then Albums play using Material.
Server - LMS 8.4.0 RPi4B 4GB/NanoSound ONE case/pCP 8.1.0 - 75K library, playlists & LMS cache on Sata SSD (ntfs)
Lounge - DAC32 - AudioEngine B2
Office - RPi 3B+/HiFiBerry DAC HAT/RPi screen - Edifier D12
Bedroom - Echo Show 8
Spares - 1xSB Touch, 1xSB3, 4xRPi, AVI DM5 speakersComment
-
However, seeing as Material is sending the library ID to LMS this should override any player-set library ID. If this is not happening, as appears to be the case here, then it sounds like an LMS bug to me - in which case you should report this on LMS's github page. There is nothing more Material can do.
The reason Material acts this way is so that I can have user X seen only their tracks, and play to any player, and user Y see only their tracks - even when about to control the same player. This is also the same for the browse modes.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
-
When you set it with Material it is only using it to limit the tracks you see when browsing. When adding a track it also send the library ID to lms - e.g. play album X using virtual library Y. Now if the player has virtual library Z set (via Default, Classic, iPeng, Squeezer, player itself, etc.) then this will affect what is shown when browsing on the hardware's UI, or with iPeng/Squezer, etc, and also affect things like random play.
However, seeing as Material is sending the library ID to LMS this should override any player-set library ID. If this is not happening, as appears to be the case here, then it sounds like an LMS bug to me - in which case you should report this on LMS's github page. There is nothing more Material can do.
The reason Material acts this way is so that I can have user X seen only their tracks, and play to any player, and user Y see only their tracks - even when about to control the same player. This is also the same for the browse modes.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
-
Server - LMS 8.4.0 RPi4B 4GB/NanoSound ONE case/pCP 8.1.0 - 75K library, playlists & LMS cache on Sata SSD (ntfs)
Lounge - DAC32 - AudioEngine B2
Office - RPi 3B+/HiFiBerry DAC HAT/RPi screen - Edifier D12
Bedroom - Echo Show 8
Spares - 1xSB Touch, 1xSB3, 4xRPi, AVI DM5 speakersComment
-
Living Room: Touch or Squeezelite (Pi3B) > Topping E30 > Audiolab 8000A > Monitor Audio S5 + BK200-XLS DF
Bedroom: Radio
Bathroom: RadioComment
-
Server - LMS 8.4.0 RPi4B 4GB/NanoSound ONE case/pCP 8.1.0 - 75K library, playlists & LMS cache on Sata SSD (ntfs)
Lounge - DAC32 - AudioEngine B2
Office - RPi 3B+/HiFiBerry DAC HAT/RPi screen - Edifier D12
Bedroom - Echo Show 8
Spares - 1xSB Touch, 1xSB3, 4xRPi, AVI DM5 speakersComment
-
One last post about this before I give up on it and just ignore it. I checked json response for the cases where an album plays and fails and to me it looks like the response terms are returned in a different order. Is that relevant?
albumnotplaying.txt
albumplaying.txt
Living Room: Touch or Squeezelite (Pi3B) > Topping E30 > Audiolab 8000A > Monitor Audio S5 + BK200-XLS DF
Bedroom: Radio
Bathroom: RadioComment
-
One last post about this before I give up on it and just ignore it. I checked json response for the cases where an album plays and fails and to me it looks like the response terms are returned in a different order. Is that relevant?
[ATTACH]n1631643[/ATTACH]
[ATTACH]n1631644[/ATTACH]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