Really weird: If I don't use the chroma plugin everything works fine (albeit matches are not as accurate). If I use the chroma plugin, beet finds the right track and all (I can see a chroma reference when I use the verbose option), but when it's time for me to choose apply/abort or what not, any input I click with the keyboard doesn't show on the terminal (or affects anything). It's as if the keyboard is stuck. So beet is just stuck waiting for my input and I can't give it to it...
I'm on a headless Debian stretch. -- You received this message because you are subscribed to the Google Groups "beets" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
