If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
Did you change the I lookup code for Lyrics when you changed it for Album review ? I have some local lyrics files that are now not displaying but do when you go via More ?
Did you change the I lookup code for Lyrics when you changed it for Album review ? I have some local lyrics files that are now not displaying but do when you go via More ?
Nope! I'll update the code for 0.9.2 to pass just track_id for lyrics and just artist_id for biographies - if these are known for these calls, otherwise I'll pass the strings.
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.
Nope! I'll update the code for 0.9.2 to pass just track_id for lyrics and just artist_id for biographies - if these are known for these calls, otherwise I'll pass the strings.
I'm not sure whether that is the answer so don't change yet. I'll need to do some testing with MAI in the default skin first.
I have now realised that the issue is that MAI finds local lyrics correctly for one variant of a particular album but not always for another and Material does the same.
This all comes from me finding that ChartLyrics has "Derek & The Dominos" listed as Derek and the Dominos and a subsequent discussion with Michael about "and/&" in the MAI code where we agreed that it was unresovable except by creating local lyrics files.
All my variants of Layla and Other Assorted Love Songs are tagged as "Derek & The Dominos" so to overcome the issue I manually created Lyric files for the entire album under a folder named - Derek & The Dominos
MAI finds them for tacks in
Layla and Other Assorted Love Songs (Deluxe)
but only sometimes for
Layla and Other Assorted Love Songs
Layla and Other Assorted Love Songs (Vinyl)
It may also be a caching issue so I will clear and re-test.
I'm not sure whether that is the answer so don't change yet.
Well, as per the ablum review, I looked at the MAI code, and if these parametes are passed for the relevant call it will use them to lookup the actual string values. So, should be safe enough.
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.
Well, as per the ablum review, I looked at the MAI code, and if these parametes are passed for the relevant call it will use them to lookup the actual string values. So, should be safe enough.
Since upgrading to 0.9.1, I seem to be unable to use the "Local artwork" option of MAI from Material. Every attempt to use it produces this error message: "Something went wrong! (Error: Network Error)" and this in the LMS log:
Slim::Web::JSONRPC::requestMethod (486) 00:23:24:0a:e9:a3: request not dispatchable!
Works as expected in the default interface.
Usually running latest beta LMS nightly on Raspberry Pi OS with virtual players (Squeezelite and Airplay bridge). Occasionally using SB Radio, Boom or Classic.
> Since upgrading to 0.9.1, I seem to be unable to use the "Local artwork"
> option of MAI from Material. Every attempt to use it produces this error
> message: "Something went wrong! (Error: Network Error)" and this in the
> LMS log:
>
> Slim::Web::JSONRPC::requestMethod (486) 00:23:24:0a:e9:a3: request not
> dispatchable!
That would happen if the client (Material or other) would request for a
player which is no longer connected to LMS. Most likely this has nothing
to do with Material.
> Works as expected in the default interface.
With the same MAC address? Can you double check you've selected the same
player in both skins?
--
Michael
Michael
"It doesn't work - what shall I do?" - "Please check your server.log and/or scanner.log file!"
(LMS: Settings/Information)
> Since upgrading to 0.9.1, I seem to be unable to use the "Local artwork"
> option of MAI from Material. Every attempt to use it produces this error
> message: "Something went wrong! (Error: Network Error)" and this in the
> LMS log:
>
> Slim::Web::JSONRPC::requestMethod (486) 00:23:24:0a:e9:a3: request not
> dispatchable!
That would happen if the client (Material or other) would request for a
player which is no longer connected to LMS. Most likely this has nothing
to do with Material.
> Works as expected in the default interface.
With the same MAC address? Can you double check you've selected the same
player in both skins?
--
Michael
I see the same. If I tap on "local artwork" I see the first image. If I tap on the artwork to enlarge it I see the second image.
Sent from my SM-G900F using Tapatalk
Living Room: Touch or Squeezelite (Pi3B) > Topping E30 > Audiolab 8000A > Monitor Audio S5 + BK200-XLS DF
Bedroom: Radio
Bathroom: Radio
Squeezebox: Boom x2 (Kitchen and Living Room), Radio x4 (Kids, Play Room and Bedroom), PiCorePlayer (Office) Server: 8.1.0 for PCP Plugins: Spotty | Dynamic Playlists | SQL Playlist | Music and Artist Information | TrackStat Remote: iPhone8/iPad Air running iPeng Music: Last.fm
>
....
> Works as expected in the default interface.[/color]
With the same MAC address? Can you double check you've selected the same
player in both skins?
--
Michael
Same player.
slartibartfast explained it better than I did. I can also see the thumbnails in Local artwork, but when I attempt to select an image, the error occurs.
Usually running latest beta LMS nightly on Raspberry Pi OS with virtual players (Squeezelite and Airplay bridge). Occasionally using SB Radio, Boom or Classic.
I see the same. If I tap on "local artwork" I see the first image.
Yaah, I stupidly removed the section of code that handles this. Oops! Fix for next release...
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.
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.
We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, personalize advertising, and to analyze site activity. We may share certain information about our users with our advertising and analytics partners. For additional details, refer to our Privacy Policy.
By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.
Comment