Results 11 to 20 of 76
-
2019-03-13, 03:29 #11
- Join Date
- Feb 2019
- Posts
- 88
-
2019-03-13, 03:51 #12
CLI interface limitations - workarounds?
>> Any request to the image proxy would accept resizing parameters. But the
>> raw URL you post would not be resized. You'd get that 40MB scan of a LP
>> cover, if that was what the plugin found.
>
> I was specifically asking about the "*Music and Artist Information*"
> images obtained from the plugin (which is great, btw). Is there any
> other way of requesting them, then by using those URLs ?
Which images? Cover art? Artist pictures?
Cover art you can save to your music files, or in the music folder, and
they'd be available through LMS' artwork handler.
Artist pictures - no. That's the URL to use. What's wrong with it? Or
what are you trying to do?
--
Michael
-
2019-03-13, 04:01 #13
- Join Date
- Feb 2019
- Posts
- 88
-
2019-03-13, 04:07 #14
CLI interface limitations - workarounds?
> Artist pictures. The URL is fine, and nothing is wrong (as I said -
> great plugin) I was just wondering if there were server side resizing
> options for it. The pictures you get with the plugin are small, but
> users can add their own images.
Well, then we're back at my first response, which was: you can tell the
imageproxy how large you want to have it. Without any resizing
parameters you'd get the original file. Which can be small, or way
larger than you'd want. That default size really just depends on the
source of the image.
I'd strongly recommend you to configure a local folder where you can
store those images. If you find one you consider too small, just replace
it in there, instead of relying on the plugin to find something useful.
--
Michael
-
2019-03-13, 04:21 #15
- Join Date
- Feb 2019
- Posts
- 88
-
2019-04-01, 08:07 #16
- Join Date
- Feb 2019
- Posts
- 88
I have made progress developping a single web page which displays albums, artists, with a variety of filters and navigation, all based on the CLI interfaces. So far so good...
The limitations of the interfaces do not allow me, however, to easily display relationships between artists. For example: I would like to dispaly all the musicians that have performed on all the albums of a particular artist. This is useful and interesting, especially in Jazz, where the "ecosystem" of an artist can be quite large...
In order to do this, I would have to:
- select all tracks for a given artist
- parse the results of the titles to extract the individual contributing artists (I personally store the contributing artists in the "band" tag, for lack of a better place)
- then querry the contributing artists individually to obtain their "name"
It is possible, obviously, but does not seem very "efficient". Is there any way the CLI interfaces could evolve to provide this information ? Otherwise, could this be dealt through a plugin instead, active during the scan of the database ? Any ideas would be welcome.Last edited by hopkins; 2019-04-01 at 08:20.
-
2019-04-01, 21:50 #17
CLI interface limitations - workarounds?
Did you look into the Music & Artist Information plugin? It offers
information about related artists, credits etc.
If you wanted gather that information based on the metadata in your
files, you'd have to do this yourself.
--
Michael
-
2019-04-09, 02:00 #18
- Join Date
- Feb 2019
- Posts
- 88
Hi again,
Is there any way the musicbrainz_id tags could be included in the CLI interfaces for albums and contributors ?
Related question: for albums, I can get LMS to update the musicbrainz_id tag from my FLAC tags, but have not been able to do so for artists (whether using the MUSICBRAINZ_ALBUMARTIST_ID tag or the MUSICBARINZ_ARTISTID tag. Am I missing something ?
Thanks
-
2019-04-09, 02:18 #19
CLI interface limitations - workarounds?
> Is there any way the musicbrainz_id tags could be included in the CLI
> interfaces for albums and contributors ?
I thought there was - but it seems I was wrong. We do store the value in
the database, but don't expose it.
> Related question: for albums, I can get LMS to update the musicbrainz_id
> tag from my FLAC tags, but have not been able to do so for artists
> (whether using the MUSICBRAINZ_ALBUMARTIST_ID tag or the
> MUSICBARINZ_ARTISTID tag. Am I missing something ?
They should both work. You'd find a mapping here:
https://github.com/Logitech/slimserv...ts/FLAC.pm#L43
Right hand side is what we're using, left hand is tag names which would
be mapped to the right hand.
--
Michael
-
2019-04-09, 02:22 #20
- Join Date
- Feb 2019
- Posts
- 88