Announce: Material Skin

[d6jg]

To use party-mode you can either:

1. Set 'Material Skin (Party)' as the default skin, and the just give users your LMS url (e.g. http: //SERVER:9000)
2. Use http: //SERVER:9000/materialparty/ - this is the URL used by 'Material Skin (Party)'
3. Use http: //SERER:9000/matrerial/?party - which is actual URL, and http: //SERVER:9000/materialparty/ just redirects to this

There is no need to specify a player. However, if you wish to allow your users to only control a single player then you can use http: //SERVER:9000/material/?party&single&player=01:02:03:04:05:06 (player can be ID (MAC) or its name (URL encoded))

Many thanks but slightly confused. I can’t see Player Settings but I can see (and edit) Server Settings. I’m sure that’s not intended

Edit. Scratch that. Must be caching issue

[d6jg]

Now that Craig has given the url info needed for your guests to access a specific player at a party here is what you need to (safely) generate some QR codes.

1. Guests need to access your WiFi. Use https://qifi.org/ to generate a QR code. Unlike other web resources that do this QiFi is entirely JS in your browser I.e. you don’t send your SSiID and WiFi password to some random web server.

2. Open the URL as detailed by Craig in Chrome. Then click the share icon (or the three dots on desktop) where there is an option to generate a QR code.

Print the two QR codes out so your guests can use them!

[wactuary]

Feature request - Repeast/DSTM/finite list

On the player screen above the play list is a toggle that loops between Repeat Track, Repeat Playlist and DSTM (if that plug in is enabled). It would be great if there were a 4th option, the unhighlighted icon, where all repeat functionality is paused. So leave the infinity icon, but shade it grey/disabled, and that would make a finite play list.

Thanks,
wactuary

[nickey]

As a compromise, what about double-click?

Sorry...I haven't been around for a couple of days, but WOW, yes that is awesome! Working great on PC and Android...thanks very much for this!

Cheers, Nico.

[cpd73]

On the player screen above the play list is a toggle that loops between Repeat Track, Repeat Playlist and DSTM (if that plug in is enabled). It would be great if there were a 4th option, the unhighlighted icon, where all repeat functionality is paused. So leave the infinity icon, but shade it grey/disabled, and that would make a finite play list.

Thanks,
wactuary

For this you currently need to set DSTM to 'Disabled' (long press the infinity icon will show DSTM options). The issue is that DSTM has no on/off setting - just a single disabled/mixer_a/mixer_b/etc. setting. So whilst Material could just switch off, to switch back on the user would need to be prompted to select a mixer - and doing that each time you cycle the repeat button would be annoying. Ideally DSTM would be changed to have two settings; enabled and mixer. I might work-around this by having Material remember the last DSTM mixer setting for a player, so you could then cycle repeat off, repeat repeat all, repeat single, dstm, repeat off, etc.

[cpd73]

On the player screen above the play list is a toggle that loops between Repeat Track, Repeat Playlist and DSTM (if that plug in is enabled). It would be great if there were a 4th option, the unhighlighted icon, where all repeat functionality is paused. So leave the infinity icon, but shade it grey/disabled, and that would make a finite play list.

Thanks,
wactuary

I've implemented this in the 3.1 for a future 3.1.0 release (this will probably NOT be the next release). Now the button cycles; off, single, all, DSTM. Long press still opens DSTM options. When changing the 'repeat' from DSTM to repeat off Material will first save the current DSTM setting. When changing from repeat all to DSTM Material will restore the previous DSTM setting.

[wactuary]

For this you currently need to set DSTM to 'Disabled' (long press the infinity icon will show DSTM options). The issue is that DSTM has no on/off setting - just a single disabled/mixer_a/mixer_b/etc. setting. So whilst Material could just switch off, to switch back on the user would need to be prompted to select a mixer - and doing that each time you cycle the repeat button would be annoying. Ideally DSTM would be changed to have two settings; enabled and mixer. I might work-around this by having Material remember the last DSTM mixer setting for a player, so you could then cycle repeat off, repeat repeat all, repeat single, dstm, repeat off, etc.

I hadn't realized the long-press to change mix type (and select disable) was there. This helps, thanks! I also posted a feature request for DSTM because I do think it makes more sense to have on/off separate from mix type. I could understand not wanting to add the extra complexity too, but worth asking the question anyway.

Thanks again!

[wactuary]

I've implemented this in the 3.1 for a future 3.1.0 release (this will probably NOT be the next release). Now the button cycles; off, single, all, DSTM. Long press still opens DSTM options. When changing the 'repeat' from DSTM to repeat off Material will first save the current DSTM setting. When changing from repeat all to DSTM Material will restore the previous DSTM setting.

Wow, that was quick! I'll edit my DSTM request to note this was done and may not be needed.

[Orange]

@cpd73

first of all thank you very much for all your work on this skin.

would it be possible to add "thumbs up" and "thumbs down" buttons on the bottom bar for the pandora plugin?

Best wishes

[cpd73]

@cpd73

first of all thank you very much for all your work on this skin.

would it be possible to add "thumbs up" and "thumbs down" buttons on the bottom bar for the pandora plugin?

Best wishes

These buttons replace the repeat/shuffle buttons - which are not shown in this bar. They are shown in the queue's toolbar, but placing thumb up/down there would make no sense. Sorry, but I don't use Pandora and don't really want to go through the hassle of adding these to the bottom bar.

[Edit] Actually, this was not that hard. I've added these buttons to the right hand side of this bar (where ratings for local tracks would be). This is for 3.1.0

[Lso]

Ish for Material skin

Is there any chance for a raspberry clean shutdown buttom in material skin, i could really use functionality.
Kind regards
Lars

[cpd73]

After updating the Material plugin, (by doing a git pull,) I clear it's cache on my phone, (Android 13.) When I hit the "Tap here to clear cache" option in the APK Settings / Application menu I get a white msg field, but no longer is anything displayed in that area. I suspect the issue is the text saying the cache will be cleared is also white? I tried changing the Interface Theme, but that does not seem to make any difference.

Odd, as I cannot recreate this. The APK's theme is always dark, and the "Cache will be cleared" message is shown by the APK, so is light text on a dark background. Which version of android is this? Even setting my Android phone to use light, I still get a dark background with light text (as I would expect).

[cpd73]

Is there any chance for a raspberry clean shutdown buttom in material skin, i could really use functionality.
Kind regards
Lars

Yes, but you will need to add this yourself via a custom action - see "Custom menu entries and actions" in https://github.com/CDrummond/lms-mat...-Customisation

This is request is too Pi specific to add into the skin itself.

[Redrum]

Odd, as I cannot recreate this. The APK's theme is always dark, and the "Cache will be cleared" message is shown by the APK, so is light text on a dark background. Which version of android is this? Even setting my Android phone to use light, I still get a dark background with light text (as I would expect).

I have seen this, but never thought to report. Here is what it looks like. Pixel 7, Android 13. Material 0.3.0 (according to F-Droid)



Jim

[cpd73]

I have seen this, but never thought to report. Here is what it looks like. Pixel 7, Android 13. Material 0.3.0 (according to F-Droid)

Most odd. Just (today) upgraded my Samsung S20FE to Android 13, and still shows fine for me Perhaps I just need to see if I can hard-code colours for this specific widget.