Announcement

Collapse
No announcement yet.

Announce: Material Skin

Collapse
X
 
  • Time
  • Show
Clear All
new posts

  • Originally posted by cpd73
    Feature release, main changes:
    • 10 Don't allow adjusting volume via mouse wheel in group volume or 'Manage players' dialogs.
    Coding faster than his shadow. Many thanks!

    Comment


    • 2.7.1 Release

      Bug-fix release, main changes:
      1. Translation updates.
      2. Remove any leading slash from xxx_svg.png paths.
      3. Enhance custom action support; add to context menus - artists, albums, genres, years, queue, tracks, playlists.
      4. Fix RadioNet icon mapping.
      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


      • Originally posted by cpd73
        [*] Remove any leading slash from xxx_svg.png paths.
        Thanks - that will help me when I forget in the future.
        Paul Webster
        Author of "Now Playing" plugins covering Radio France (FIP etc), PlanetRadio (Bauer - Kiss, Absolute, Scala, JazzFM etc), KCRW, ABC Australia and CBC/Radio-Canada
        and, via the extra "Radio Now Playing" plugin lots more - see https://forums.slimdevices.com/showt...Playing-plugin

        Comment


        • Originally posted by cpd73
          Bug-fix release, main changes:
          1. Translation updates.
          2. Remove any leading slash from xxx_svg.png paths.
          3. Enhance custom action support; add to context menus - artists, albums, genres, years, queue, tracks, playlists.
          4. Fix RadioNet icon mapping.
          Hey, after updating to 2.7.1 none of the custom actions I created earlier are showing. In chrome devtools when I load material skin it shows the following error... material.min.js?r=2.7.1:216 SyntaxError: Unexpected token ':'
          at material.min.js?r=2.7.1:216
          . When I click this error it takes me to line 216 highlighting the following: {customActions=eval(a.data);

          Hopefully that's helpful.

          Thanks for all you do.

          Comment


          • Originally posted by shinedou
            Hey, after updating to 2.7.1 none of the custom actions I created earlier are showing. In chrome devtools when I load material skin it shows the following error... material.min.js?r=2.7.1:216 SyntaxError: Unexpected token ':'
            at material.min.js?r=2.7.1:216
            . When I click this error it takes me to line 216 highlighting the following: {customActions=eval(a.data);

            Hopefully that's helpful.

            Thanks for all you do.
            Sounds like there is an error in your actions JSON file. Perhaps attach a copy here, and I'll check.
            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


            • Originally posted by cpd73
              Sounds like there is an error in your actions JSON file. Perhaps attach a copy here, and I'll check.
              Here is what's in my actions.json. As I stated this was working before the recent update. Also I copied in full your example from the wiki into a fresh actions.json and it gives the same error without any of the items showing in the menus.

              Code:
              {
                "artist":[
                  {
                    "title":"Random Play Artist",
                    "script":"lmsCommand('$ID', ['dynamicplaylist', 'playlist', 'play', 'dpldefault_zz_CONTEXTMENU_for_selected_artist_a01_songs_random', 'dynamicplaylist_parameter_1:$ARTISTID'])",
                    "icon":"playlist_play"
                  },
                  {
                    "title":"Artist Radio",
                    "lmscommand":["dynamicplaylist", "playlist", "play", "dpldefault_zz_CONTEXTMENU_for_selected_artist_a01_songs_random", "dynamicplaylist_parameter_1:$ARTISTID"],
                    "svg":"dice-list"
                  }
                ],
                "genre":[
                  {
                    "title":"Random Play Genre",
                    "script":"lmsCommand('$ID', ['dynamicplaylist', 'playlist', 'play', 'dpldefault_zz_CONTEXTMENU_for_selected_genre_a01_songs_random', 'dynamicplaylist_parameter_1:$GENREID'])",
                    "icon":"playlist_play"
                  }
                ]
              }

              Comment


              • Originally posted by shinedou
                Here is what's in my actions.json. As I stated this was working before the recent update. Also I copied in full your example from the wiki into a fresh actions.json and it gives the same error without any of the items showing in the menus.
                Are you sure you're on 2.7.1 of MaterialSkin? As I've just copied your example into an actions.json and it appears to work just fine for me. I say appears, as I do not use these plugins but using my browser's dev tools I can see the a JSONRPC command is sent when the action is performed.
                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


                • Originally posted by cpd73
                  Are you sure you're on 2.7.1 of MaterialSkin? As I've just copied your example into an actions.json and it appears to work just fine for me. I say appears, as I do not use these plugins but using my browser's dev tools I can see the a JSONRPC command is sent when the action is performed.
                  Yes I just verified I have Material Skin 2.7.1. I rebooted server > same error, Removed actions.json from prefs/material-skin > same error.
                  I will try removing plugin and re-installing.

                  Comment


                  • Radio > Tune in URL option available?

                    I often use Radio > Tune In URL but can't find it in the Material skin (not the TuneIn plugin, just the tune-to-a-radio-station-by-url functionality).
                    Is it available? (I searched the thread but couldn't find any information).

                    The material skin is impressive. Thanks for all the great work.

                    Click image for larger version

Name:	Screen Shot 2021-10-17 at 11.29.02 AM.png
Views:	1
Size:	94.4 KB
ID:	1573457

                    Comment


                    • Originally posted by coldslabs
                      I often use Radio > Tune In URL but can't find it in the Material skin (not the TuneIn plugin, just the tune-to-a-radio-station-by-url functionality).
                      Is it available? (I searched the thread but couldn't find any information).

                      The material skin is impressive. Thanks for all the great work.

                      [ATTACH]35948[/ATTACH]
                      In the queue tab in a browser click "+" to add a URL. In the mobile layout click the three dots in the queue tab and choose add URL

                      Sent from my Pixel 3a using Tapatalk
                      Living Room: Touch or Squeezelite (Pi3B) > Topping E30 > Audiolab 8000A > Monitor Audio S5 + BK200-XLS DF
                      Bedroom: Radio
                      Bathroom: Radio

                      Comment


                      • Originally posted by shinedou
                        Yes I just verified I have Material Skin 2.7.1. I rebooted server > same error, Removed actions.json from prefs/material-skin > same error.
                        I will try removing plugin and re-installing.
                        Originally posted by cpd73
                        Are you sure you're on 2.7.1 of MaterialSkin? As I've just copied your example into an actions.json and it appears to work just fine for me. I say appears, as I do not use these plugins but using my browser's dev tools I can see the a JSONRPC command is sent when the action is performed.
                        It appears it was a browser cache issue. I cleared my cache and all is showing up now. Sorry about that. Now onto testing.
                        Thanks

                        Comment


                        • Originally posted by slartibartfast
                          In the queue tab in a browser click "+" to add a URL. In the mobile layout click the three dots in the queue tab and choose add URL
                          Ah, perfect. That's a convenient place to have the option. Thanks!

                          Comment


                          • Regarding the Custom menu entries and actions would it be possible to combine multiple commands (actions) into one menu entry either using lmscommand: or script:?

                            Comment


                            • Originally posted by shinedou
                              Regarding the Custom menu entries and actions would it be possible to combine multiple commands (actions) into one menu entry either using lmscommand: or script:?
                              Yes, you could use a script.
                              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


                              • Originally posted by cpd73
                                Yes, you could use a script.
                                OK I was able to get a test script to work that has two commands in it. One thing I have noticed is whatever the first variable is, for example $ID, is not passed onto the second command. I had to use $NAME in the second command to get the script to work. For whatever reason if I use $ID more than once it sends that param blank.

                                Blank Param in request payload...
                                Code:
                                {"id":0,"method":"slim.request","params":["",["dynamicplaylist","playlist","stop"]]}
                                This works...
                                Code:
                                    {
                                      "title":"Artist Radio",
                                      "script":"lmsCommand('$ID', ['dynamicplaylist', 'playlist', 'play', 'dpldefault_zz_CONTEXTMENU_for_selected_artist_a01_songs_random', 'dynamicplaylist_parameter_1:$ARTISTID']); setTimeout(() => lmsCommand('$NAME', ['dynamicplaylist', 'playlist', 'stop']), 10000)",
                                      "icon":"queue_music"
                                    },
                                This does not work...
                                Code:
                                    {
                                      "title":"Artist Radio",
                                      "script":"lmsCommand('$ID', ['dynamicplaylist', 'playlist', 'play', 'dpldefault_zz_CONTEXTMENU_for_selected_artist_a01_songs_random', 'dynamicplaylist_parameter_1:$ARTISTID']); setTimeout(() => lmsCommand('$ID', ['dynamicplaylist', 'playlist', 'stop']), 10000)",
                                      "icon":"queue_music"
                                    },

                                Comment

                                Working...
                                X
                                😀
                                🥰
                                🤢
                                😎
                                😡
                                👍
                                👎