Often times, artwork is stored in a separate folder (usually called /Artwork). If the "Import cover from file" script worked recursively, it would have more success rate. Thanks!!
Could you give a real example?
AFAIK you can specify a cover file name which includes an absolute or relative path component.
see e.g. this path:
As I import music to my music library that is gathered from many different sources, I run scripts to match those imports to my preferred configurations. One of the scripts is "Import cover from file". My goal here is to locate any file in the directory that work as a cover (e.g. cover*.png or even *.png as a worst case). Often times, these folders will have artwork located within a separate Artwork folder. Therefore, my script fails to locate any covers.
Thanks for asking. I should have been more clear.
I don't know how often in the life of a file a cover has to be imported from such varying paths.
So I would think that simply an action group with 2 (or more) actions that import covers from various folder depths would be a good way.
... and that such a folder is
does not seem to be true as the linked thread looks for covers in
I see in your suggestion the problem that you would have to switch on an off that recursion if you want to get the desired hits if you have several picture files in different folder depths.
And if you do that, you could alternatively adapt the path ...
So I think until your request becomes a feature, there are a number of workarounds
That is a great workaround that I haven't considered. I'll add a few additional lines to my script to predict some folders (like "\Cover and \Artwork). Thanks @ohrenkino.
Would be a good feature for the future nonetheless.
please note the 2 dots in front of the backslash as only they will move up one directory in a relative path.