--
You received this message because you are subscribed to the Google Groups "Sonospy Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sonospy-deve...@googlegroups.com.
To post to this group, send email to sonosp...@googlegroups.com.
Visit this group at https://groups.google.com/group/sonospy-devel.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to a topic in the Google Groups "Sonospy Development" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/sonospy-devel/jbLZ139gbQc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to sonospy-devel+unsubscribe@googlegroups.com.
To post to this group, send an email to sonosp...@googlegroups.com.
* MARK HENKELIS schrieb am 13.01.17 um 10:30 Uhr:
> The scanner doesn't know that it is an artist folder, it only finds
> tags from music files (it doesn't actually care where they are, the
> folder structure is incidental, the tags are the important bit). If
> there is artwork in the music file or the same folder, then it assumes
> it is album art. So there is no direct linkage between the folder
> name, the album name and the album art.
>
>
> That said, I guess artist.jpg in the same location as the album art
> could work - with a rule to define which takes precedence if there are
> multiples across albums. We'd have to decide how to treat albums with
> multiple artists too, and albumartist vs artist.
Why not look for a folder.jpg in the parent directory when a file
containing tags is found?
Maybe it would be helpful to introduce a new configurarion item like
"relative_artist_art_location" which takes a relative path.
Example values:
- ../folder.jpg (Parent folder of album directory)
- artist.jpg (Same folder as music file)
-Marc
--
You received this message because you are subscribed to a topic in the Google Groups "Sonospy Development" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/sonospy-devel/jbLZ139gbQc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to sonospy-deve...@googlegroups.com.
To post to this group, send an email to sonosp...@googlegroups.com.
Visit this group at https://groups.google.com/group/sonospy-devel.
For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to a topic in the Google Groups "Sonospy Development" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/sonospy-devel/jbLZ139gbQc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to sonospy-devel+unsubscribe@googlegroups.com.
Thanks Martin
To unsubscribe from this group and all its topics, send an email to sonospy-deve...@googlegroups.com.
To post to this group, send email to sonosp...@googlegroups.com.
Visit this group at https://groups.google.com/group/sonospy-devel.
For more options, visit https://groups.google.com/d/optout.
--
Thanks Martin
On Tuesday, 10 January 2017 22:58:16 UTC, Mark Henkelis wrote: <blockquote class="gmail_quote"
--