New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fetchart plugin does not import cover art when import is run with move
and quiet
enabled
#5167
Comments
Though, unfortunately the cover art file is not imported in quiet mode, see beetbox/beets#5167
It has nothing to do with move or quite group_albums: yes is the culprit. well not culprit exactly because group albums does not care about folders, it is meant to be used when multiple tracks from different albums is in the same folder, and when you use that you are telling beets to group based on albums and not folder, so any images are ignored in the process. set that to no and it will "move quitely" as expected. |
...by not grouping by albums when importing album/collection folders. See beetbox/beets#5167
Ah, thanks @Dr-Blank for clarifying that. I misinterpreted the option. Disabling it makes beets import the |
To avoid leaving album directories within the ytimport directory, each containing only a `cover.jpg` file. See beetbox/beets#5167
However, in case of the ytimport plugin, unfortunately the UPDATE: This is addressed by PR #5244. |
Defer the evaluation of the source removal options (`import.delete` and `import.move`) to the point where the fetchart plugin is actually called instead of evaluating those configuration options on plugin initialization. This is to allow other plugins (such as the [ytimport](https://github.com/mgoltzsche/beets-ytimport/blob/v1.8.1/beetsplug/ytimport/__init__.py#L194) plugin) to invoke the import directly (within the same python process; implicitly invoking the fetchart plugin) with temporarily overwritten configuration options. Relates to beetbox#5167 (comment)
Defer the evaluation of the source removal options (`import.delete` and `import.move`) to the point where the fetchart plugin is actually called instead of evaluating those configuration options on plugin initialization. This is to allow other plugins (such as the [ytimport](https://github.com/mgoltzsche/beets-ytimport/blob/v1.8.1/beetsplug/ytimport/__init__.py#L194) plugin) to invoke the import directly (within the same python process; implicitly invoking the fetchart plugin) with temporarily overwritten configuration options. Relates to beetbox#5167 (comment)
Defer the evaluation of the source file removal options (`import.delete` and `import.move`) to the point where the fetchart plugin is actually called instead of evaluating those configuration options on plugin initialization. This is to allow other plugins (such as the [ytimport](https://github.com/mgoltzsche/beets-ytimport/blob/v1.8.1/beetsplug/ytimport/__init__.py#L194) plugin) to invoke the import directly (within the same python process; implicitly invoking the fetchart plugin) with temporarily overwritten configuration options. Relates to beetbox#5167 (comment)
Defer the evaluation of the source file removal options (`import.delete` and `import.move`) to the point where the fetchart plugin is actually called instead of only evaluating those configuration options on plugin initialization. This is to allow other plugins (such as the [ytimport](https://github.com/mgoltzsche/beets-ytimport/blob/v1.8.1/beetsplug/ytimport/__init__.py#L194) plugin) to invoke the import directly (within the same python process; implicitly invoking the fetchart plugin) with temporarily overwritten configuration options. Relates to beetbox#5167 (comment)
Defer the evaluation of the source file removal options (`import.delete` and `import.move`) to the point where the fetchart plugin is actually called instead of only evaluating those configuration options on plugin initialization. This is to allow other plugins (such as the [ytimport](https://github.com/mgoltzsche/beets-ytimport/blob/v1.8.1/beetsplug/ytimport/__init__.py#L194) plugin) to invoke the import directly (within the same python process; implicitly invoking the fetchart plugin) with temporarily overwritten configuration options. Relates to beetbox#5167 (comment)
Defer the evaluation of the source file removal options (`import.delete` and `import.move`) to the point where the fetchart plugin is actually called instead of only evaluating those configuration options on plugin initialization. This is to allow other plugins (such as the [ytimport](https://github.com/mgoltzsche/beets-ytimport/blob/v1.8.1/beetsplug/ytimport/__init__.py#L194) plugin) to invoke the import directly (within the same python process; implicitly invoking the fetchart plugin) with temporarily overwritten configuration options. Relates to beetbox#5167 (comment)
When I import a directory that includes a
cover.jpg
file into my beets library with bothimport.move
andimport.quiet
set totrue
, the cover art is not imported.When I disable
move
orquiet
, it imports the cover art.(However, when importing the cover art, the fetchart plugin does not use the
cover.jpg
that exists within the album source directory but fetches it from coverartarchive.org. Correspondingly, thecover.jpg
file within the import source directory is not deleted after the import althoughmove
is enabled.)Problem
Imagine I have the import options
group_albums
,move
andquiet
enabled and the following file system structure to import from:/data/ytimport/albums/some artist - some album
01 - First Track.opus
02 - Second Track.opus
cover.jpg
Running this command in verbose (
-vv
) mode:Does not import any cover art.
The log shows that the
fetchart
plugin tries to lookup the cover art within the file system and that it doesn't try the other cover art sources:When I disable any of the
import.move
orimport.quiet
configuration options, it imports cover art - from a non-filesystem source, though.You can get the example data e.g. using the ytimport plugin:
beet ytimport --no-import https://www.youtube.com/watch?v=4D8YPDdsxYU
Setup
--plugins=fetchart
My configuration (output of
beet config
) is:The text was updated successfully, but these errors were encountered: