Home of the Squeezebox™ & Transporter® network music players.
Page 898 of 928 FirstFirst ... 398798848888896897898899900908 ... LastLast
Results 8,971 to 8,980 of 9275
  1. #8971
    Senior Member
    Join Date
    Oct 2014
    Location
    Pittsburgh PA
    Posts
    494
    Quote Originally Posted by cpd73 View Post
    Whilst I cannot be 100% certain, as I do not use Qobuz, but if the selection from the "(...)" menu works then the selection from this list should now too - as I added the artist_id parameter there.

    Please ensure you fully re-load the page. Especially with dev versions the browser likes to load from cache. With Chrome you just need to open the dev tools, press and hold the refresh button, and select "Empty cache and hard reload"
    Having been burned on that before, I'm very careful to clear the cache when testing changes. Meet the new request --- same as the old request (thanks, Pete Townsend...):

    Code:
    [10:18:30 AM] JSON REQ: ["b8:26:eb:c1:71:f0",["browseonlineartist","items",0,25000,"service_id:qobuz","artist_id:undefined","menu:1"]]
    I see the code change you made in line 391 and my guess is that artist_id has not been assigned the proper value prior to its use there. I don't know enough about JS or the flow of the code to know where the problem might be though.
    Sam

  2. #8972
    Senior Member
    Join Date
    Oct 2014
    Location
    Pittsburgh PA
    Posts
    494
    Quote Originally Posted by SamY View Post
    Having been burned on that before, I'm very careful to clear the cache when testing changes. Meet the new request --- same as the old request (thanks, Pete Townsend...):

    Code:
    [10:18:30 AM] JSON REQ: ["b8:26:eb:c1:71:f0",["browseonlineartist","items",0,25000,"service_id:qobuz","artist_id:undefined","menu:1"]]
    I see the code change you made in line 391 and my guess is that artist_id has not been assigned the proper value prior to its use there. I don't know enough about JS or the flow of the code to know where the problem might be though.
    My apologies, Craig. It wasn't the cache that was the problem. For some reason, I decided to just rename the old MaterialSkin plugin directory to MaterialSkin_2.10.2 and leave it in the plugins directory with the development version. Somehow this resulted in it being loaded instead of the dev version. When I removed it, the correct one was loaded. Again, my apologies. I will let you know how further testing goes. Another lesson learned the hard way...
    Sam

  3. #8973
    Senior Member
    Join Date
    Oct 2014
    Location
    Pittsburgh PA
    Posts
    494
    Quote Originally Posted by cpd73 View Post
    Not sure what's wrong with that request, as looks OK to me. If you can, enable network logging on your LMS server and then use Squeezer, or some other controller (not Default skin) to access these items. Doing this should cause the JSONRPC messages to be logged. You should then be able to see what params they pass, and perhaps what Material is missing.
    Okay. Here is the Cometd request generated by Squeezer for the list of artist albums:

    Code:
    [22-08-03 11:04:04.5085] Slim::Web::Cometd::handler (149) Cometd request (192.168.1.12:48574): [
      {
        channel => "/slim/request",
        clientId => "a91ca9cc",
        data => {
              request  => [
                            "cc:cc:4c:51:85:cb",
                            [
                              "browseonlineartist",
                              "items",
                              0,
                              512,
                              "item_id:0",
                              "useContextMenu:1",
                              "menu:browseonlineartist",
                            ],
                          ],
              response => "/a91ca9cc/slim/request/7",
            },
        id => 25,
      },
    ]
    The only difference I see is the '512' vs '25000' and the existence of the 'useContextMenu:1' parameter, neither of which I know the significance. Hope this is helpful.
    Sam

  4. #8974
    Senior Member
    Join Date
    Feb 2011
    Location
    Cheshire, UK
    Posts
    6,739
    Quote Originally Posted by cpd73 View Post
    ...actually it only looks nice in those screenshots. The following (IMHO) looks awful:

    Attachment 38524

    ...think I might just go back to left aligned text. As center aligned there is no nice place to put the cover art.

    Attachment 38525
    yes your long and winding titles fooled us all

    Q. With the progress bar occupying the whole width of the screen how easy is it to navigate right back to the start when it is a continuous stream? Can you actually drag entirely to the start or end position or does the window edges confuse the drag?
    Jim
    https://jukeradio.double6.net


    VB2.4 storage QNAP TS419p (NFS)
    Living Room Joggler & Pi4/Khadas -> Onkyo TXNR686 -> Celestion F20s
    Office Joggler & Pi3 -> Denon RCD N8 -> Celestion F10s
    Dining Room SB Radio
    Bedroom (Bedside) Pi Zero+DAC ->ToppingTP21 ->AKG Headphones
    Bedroom (TV) & Bathroom SB Touch ->Denon AVR ->Mordaunt Short M10s + Kef ceiling speakers
    Guest Room Joggler > Topping Amp -> Wharfedale Modus Cubes

  5. #8975
    Senior Member
    Join Date
    Dec 2006
    Location
    UK
    Posts
    788
    Quote Originally Posted by cpd73 View Post
    There is no explicit mini player - just shrink the window.
    Ha! Of course.

  6. #8976
    Senior Member
    Join Date
    Mar 2017
    Posts
    3,742
    Quote Originally Posted by SamY View Post
    The only difference I see is the '512' vs '25000' and the existence of the 'useContextMenu:1' parameter, neither of which I know the significance. Hope this is helpful.
    So, this would fail?
    Code:
    curl 'http://SERVER:9000/jsonrpc.js' -X POST --data-raw '{"id":4,"method":"slim.request","params":["1c:c1:0c:fa:ae:3d",["browseonlineartist","items",0,25000,"menu:browseonlineartist","item_id:0"]]}'
    What about:
    Code:
    curl 'http://SERVER:9000/jsonrpc.js' -X POST --data-raw '{"id":4,"method":"slim.request","params":["1c:c1:0c:fa:ae:3d",["browseonlineartist","items",0,20,"menu:browseonlineartist","item_id:0"]]}'
    ...and
    Code:
    curl 'http://SERVER:9000/jsonrpc.js' -X POST --data-raw '{"id":4,"method":"slim.request","params":["1c:c1:0c:fa:ae:3d",["browseonlineartist","items",0,25000,"menu:browseonlineartist","item_id:0","useContextMenu:1"]]}'
    ...and
    Code:
    curl 'http://SERVER:9000/jsonrpc.js' -X POST --data-raw '{"id":4,"method":"slim.request","params":["1c:c1:0c:fa:ae:3d",["browseonlineartist","items",0,20,"menu:browseonlineartist","item_id:0","useContextMenu:1"]]}'
    I know the response will not mean much, but if a call works you should be able to see some text that you would expect.
    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.

  7. #8977
    Senior Member
    Join Date
    Oct 2014
    Location
    Pittsburgh PA
    Posts
    494
    Quote Originally Posted by cpd73 View Post

    I know the response will not mean much, but if a call works you should be able to see some text that you would expect.
    They all fail with: "(52) Empty reply from server"

    Is this possibly JSON-specific? I'm lost...
    Sam

  8. #8978
    Senior Member
    Join Date
    Mar 2017
    Posts
    3,742
    Quote Originally Posted by SamY View Post
    They all fail with: "(52) Empty reply from server"

    Is this possibly JSON-specific? I'm lost...
    Is "1c:c1:0c:fa:ae:3d" still a correct MAC address connected to your LMS?
    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.

  9. #8979
    Senior Member
    Join Date
    Mar 2017
    Posts
    3,742
    Quote Originally Posted by Peter Galbavy View Post
    While "useability" gets a mention - I am no UX expert at all either - my expectation on mobile audio apps (every local player I have used) is swipe to change tracks. Would it be possible toggle the swipe behaviour between changes screens (which I personally never use) to back and forward track?
    Material already has an option for this.
    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.

  10. #8980
    Senior Member
    Join Date
    Oct 2014
    Location
    Pittsburgh PA
    Posts
    494
    Quote Originally Posted by cpd73 View Post
    Is "1c:c1:0c:fa:ae:3d" still a correct MAC address connected to your LMS?
    I didn't use that MAC address in my testing. I also verified that other requests, such as the one that was corrected by the last code change to specify the artist_id, completed successfully using the 'curl' command.
    Sam

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •