Improve chroma logging on fatal errors

[JOJ0]

When I execute a command

beet im -C -w -a -p .

I'm getting the following output:

Resuming interrupted import of /media/sda3/Music
python3: /usr/src/debug/chromaprint/chromaprint-1.5.1/src/audio_processor.cpp:148: virtual void chromaprint::AudioProcessor::Consume(const int16_t*, int): Assertion `length % m_num_channels == 0' failed.
[1]    936677 IOT instruction (core dumped)  beet im -C -w -a -p .

I think it misses critical information: which file it happened on. I could probably fix or delete the file, but currently, the application crashes and there is no way to find out which file it happened on.

Do you think it's something worth improving?

Originally posted by @asm0dey in #5601

[JOJ0]

I agree that this makes sense to include in the log for an easy quickfix like deleting the file. Do you happen to find the time to file a quick PR for it @asm0dey? That would be 🚀

[asm0dey]

@JOJ0 sorry I didn't have a single clue how to do it