Closed Chris230291 closed 4 years ago
It looks like you haven't attached the error to your original post?
woops. Just added it, thanks
Could you please provide the full command you ran and the output with beets in verbose mode? (e.g. beet -vvv import ...
)
Right, sorry for the delay but it has been running away with no issues. I have disabled deezer, replaygain and spotify... I think the issue is with the spotify plugin. I have always had the deezer plugin disabled because that causes issues for sure. Its still running now.
I can live without the spotify plugin.
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
reopening this, as I have exactly the same error, running beets in docker and the ticket got closed by a bot...
Plugins used: chroma copyartifacts discogs edit embedart fetchart fromfilename fuzzy info inline lastgenre mbsync replaygain scrub web zero
I have this problem when using the spotify module. The problem isn't consistent. I am attaching a file showing output from "beet -vvv import ..."
Plugins enabled: embyupdate info spotify
Let me know if you need anymore information.
Interesting! Even if it's not consistent for every album, can you force it to happen by using the same album match from Spotify?
Hello. When the tagger is running I get the following error.
My configuration (output of
beet config
) is:Any ideas?
Thanks, Chris