Announcement
Collapse
No announcement yet.
Announce: Material Skin
Collapse
X
-
start playlist at track x
Would it be possible to implement a 'Play playlist starting at track' option similar to the 'Play album starting at track' option available for tracks within albums? I was thinking, fancifully perhaps and without any real knowledge of what's involved, that it could apply to playlists as it does to albums 😬Comment
-
Would it be possible to implement a 'Play playlist starting at track' option similar to the 'Play album starting at track' option available for tracks within albums? I was thinking, fancifully perhaps and without any real knowledge of what's involved, that it could apply to playlists as it does to albums 😬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
-
3.0.0 Release
Feature release, main changes:
- Re-designed bottom now-playing bar for desktop layout.
- Hide desktop bottom now-playing bar when no track.
- Add 'Party' mode where certain actions are hidden. Activate via "?party" URL query parameter, or set default skin to "Material Skin (Party)"
- When listing Spotty albums attempt to extract year from "favorites_title"
- Remove options; menu icons, always show track menu, launch player.
- Place 'Cancel', etc., buttons on the right for Windows, or if 'altBtnLayout' (or 'altBtnLayout=true') is passed as a URL parameter.
- Add 'Descending' to album sorts.
- Show icons in navigation menu.
- Default to 'Breeze-dark' if 'desktop=KDE' is passed as URL query parameter.
- Add 'Play starting at track' action for playlists.
- Add 'Show image' action to browse and queue context menus.
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
-
Feature release, main changes:
- Re-designed bottom now-playing bar for desktop layout.
- Hide desktop bottom now-playing bar when no track.
- Add 'Party' mode where certain actions are hidden. Activate via "?party" URL query parameter, or set default skin to "Material Skin (Party)"
- When listing Spotty albums attempt to extract year from "favorites_title"
- Remove options; menu icons, always show track menu, launch player.
- Place 'Cancel', etc., buttons on the right for Windows, or if 'altBtnLayout' (or 'altBtnLayout=true') is passed as a URL parameter.
- Add 'Descending' to album sorts.
- Show icons in navigation menu.
- Default to 'Breeze-dark' if 'desktop=KDE' is passed as URL query parameter.
- Add 'Play starting at track' action for playlists.
- Add 'Show image' action to browse and queue context menus.
Shuffle appears to be broken using a Windows browser and also using Squeezelite-X.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
-
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
-
APK 0.3.0 Release
Changes:
- When adding a URL via Android's share system, show a dialog asking which player to share to and add buttons for play, add, or insert.
- Add option to auto-discover servers when connection is lost (enabled by default).
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
-
Feature release, main changes:
- Re-designed bottom now-playing bar for desktop layout.
- Hide desktop bottom now-playing bar when no track.
- Add 'Party' mode where certain actions are hidden. Activate via "?party" URL query parameter, or set default skin to "Material Skin (Party)"
- When listing Spotty albums attempt to extract year from "favorites_title"
- Remove options; menu icons, always show track menu, launch player.
- Place 'Cancel', etc., buttons on the right for Windows, or if 'altBtnLayout' (or 'altBtnLayout=true') is passed as a URL parameter.
- Add 'Descending' to album sorts.
- Show icons in navigation menu.
- Default to 'Breeze-dark' if 'desktop=KDE' is passed as URL query parameter.
- Add 'Play starting at track' action for playlists.
- Add 'Show image' action to browse and queue context menus.
Sent from my Pixel 3a using TapatalkLiving Room: Touch or Squeezelite (Pi3B) > Topping E30 > Audiolab 8000A > Monitor Audio S5 + BK200-XLS DF
Bedroom: Radio
Bathroom: RadioComment
-
No. The APK is hard-coded to access "SERVER:9000/material/" - so that Material does not need to be the default skin. To use party mode you need to either a) set "Material Party" as the default skin, or access via "SERVER:9000/materialparty" The whole idea of party mode is that you would set "Material Party" as the default skin, and then your guests would just need to access "SERVER:9000" on their browser without needing to install an app.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
-
In Party mode the Radio and Favourites menus are removed but Apps remain. Radio Paradise is removed from apps but TuneIn Radio remains. Is that an oversight?
Sent from my Pixel 3a using TapatalkLiving Room: Touch or Squeezelite (Pi3B) > Topping E30 > Audiolab 8000A > Monitor Audio S5 + BK200-XLS DF
Bedroom: Radio
Bathroom: RadioComment
-
Nicholas
RPi4 / piCorePlayer v8.2.0 /Logitech Media Server Version: 8.3.1/ Hifiberry Digi+
3 Chromecast (2 mini x1 Chromecast Audio) 2 UPNP devices
also use a Gramofon off platformComment
-
Multiple Players and power toggle
Hi Craig;
I noticed an irregularity with regard to multiple players and power on/off states/indicators. I can do some more testing to try to create the exact steps to duplicate, but thought I would post what I am seeing and where I think material (LMS?) gets mixed up (or maybe it's me/my setup).
This is on a pc, I have not tried the android apk, but will.
Basically, with multiple players and the power on/off icons (both in current player and pull down), I am able to get a mismatch of the power state between the icons (both @ player and pulldown), the icon hover text, and the player itself. I should note that I never saw this until I enabled the option to replace the player icon with the power icon next to the player name. Late edit - I just tried with power icon at player turned off, issue still exists.
consider this picture:
1) I start with both the touch and boom on - everything is correct.
2) If I have the boom as the active player, I am able to toggle the power both at the top level, and, through the icon on the pull down. The hovers remain correct, the player states change correctly.
3) If I then choose the touch as the active player, but pull down (with touch highlighted/active as shown), but toggle the boom power icon (in the pull down), it does power off the boom itself, but the icon remains illuminated, and the hover still suggests to "turn off"
4) If I then continue (by clicking on the selected touch), then pull down again (touch is active player), the icon and hover are correct (off, and suggest to turn on)
5) While pulled down with touch as active player (again), and click the power icon on the boom on the pull down, the boom does turn on, but the icon remains dim.
6) Select the boom from the menu, and the icon next to the player is correct.
I have done alot more playing around (not documented) where the icon and the hover can mismatch (icon indicates "on", hover says "turn on"). Also, note that with radio and boom, I may have used the physical button on the player itself.
I also should note that "now playing" is affected. It seems like now playing follows the icon state, not the player. That is, the player can be on and playing, but if the icon is wrong (off) now playing is not active/incorrect.
I guess to summarize, using the power icon in the pull down in material for player B, when another player A is active, seems to work, but not display the result properly. Now Playing is also wrong. If B were active and you change B, everything is fine.
Its also no big deal because it seems like it can be corrected just by selecting player B as active. I am not trying to create work for you, just something i noticed.
JimComment
-
Hi Craig;
I noticed an irregularity with regard to multiple players and power on/off states/indicators. I can do some more testing to try to create the exact steps to duplicate, but thought I would post what I am seeing and where I think material (LMS?) gets mixed up (or maybe it's me/my setup).
This is on a pc, I have not tried the android apk, but will.
Basically, with multiple players and the power on/off icons (both in current player and pull down), I am able to get a mismatch of the power state between the icons (both @ player and pulldown), the icon hover text, and the player itself. I should note that I never saw this until I enabled the option to replace the player icon with the power icon next to the player name. Late edit - I just tried with power icon at player turned off, issue still exists.
consider this picture:
[ATTACH]39168[/ATTACH]
1) I start with both the touch and boom on - everything is correct.
2) If I have the boom as the active player, I am able to toggle the power both at the top level, and, through the icon on the pull down. The hovers remain correct, the player states change correctly.
3) If I then choose the touch as the active player, but pull down (with touch highlighted/active as shown), but toggle the boom power icon (in the pull down), it does power off the boom itself, but the icon remains illuminated, and the hover still suggests to "turn off"
4) If I then continue (by clicking on the selected touch), then pull down again (touch is active player), the icon and hover are correct (off, and suggest to turn on)
5) While pulled down with touch as active player (again), and click the power icon on the boom on the pull down, the boom does turn on, but the icon remains dim.
6) Select the boom from the menu, and the icon next to the player is correct.
I have done alot more playing around (not documented) where the icon and the hover can mismatch (icon indicates "on", hover says "turn on"). Also, note that with radio and boom, I may have used the physical button on the player itself.
I also should note that "now playing" is affected. It seems like now playing follows the icon state, not the player. That is, the player can be on and playing, but if the icon is wrong (off) now playing is not active/incorrect.
I guess to summarize, using the power icon in the pull down in material for player B, when another player A is active, seems to work, but not display the result properly. Now Playing is also wrong. If B were active and you change B, everything is fine.
Its also no big deal because it seems like it can be corrected just by selecting player B as active. I am not trying to create work for you, just something i noticed.
Jim
Sent from my Pixel 3a using TapatalkLiving Room: Touch or Squeezelite (Pi3B) > Topping E30 > Audiolab 8000A > Monitor Audio S5 + BK200-XLS DF
Bedroom: Radio
Bathroom: RadioComment
Comment