Crash importing some files
- Dominant language
- Python
- Stars
- 15.7k
- Forks
- 2.1k
- Avg merge
- 4d 21h
- Merged PRs (30d)
- 31
Description
### Problem
I'm having a hard time importing my collection into beets as it churns for a long time and then crashes with just this message:
`python: /build/chromaprint/src/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.`
I've inspected my music with `ffprobe` and indeed found some damaged audio files that reported 0 channels (beets should report them instead of crashing), but I also have some 5.1 music (so 6 channels) that are quite ok and still make beets crash.
Running this command in verbose (`-vv`) mode:
```sh
$ beet -vv (... paste here ...)
```
Led to this problem:
```
(paste here)
```
Here's a link to the music files that trigger the bug (if relevant):
I don't think I can legally upload it! Ask if you need more details
### Setup
* OS: Archlinux
* Python version: 3.11.8
* beets version: git commit b09806e0df8f01b9155017d3693764ae7beedcd5
* Turning off plugins made problem go away (yes/no): I don't know
My configuration (output of `beet config`) is:
```yaml
(paste here)
```
Contributor guide
Research direction
Start by reproducing the import with the affected files using the issue's `beet -vv` command, then retry with `--plugins=` to check whether a plugin is involved. Compare the damaged zero-channel files with the valid 5.1 files and inspect the beets path that invokes chromaprint. Done means these files are reported without the import crashing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100