High frequencies get cut?
See original GitHub issueHey there!
Kudos for the project – the results are pretty impressive already!
However, I noticed the default 2-stem model and the 5-stem model seem to cut higher frequencies from the material, like a (Nyquist?) knife really. I ran spleeter
on a certain US pop star’s song about temperature differences, i.e.
spleeter separate -i hot_n_cold.wav -o . -c wav
where hot_n_cold.wav
is a pcm_s16le, 48000 Hz, stereo, s16, 1536 kb/s
stream, then jury-rigged this A/B test environment in FL Studio where one can compare the original version and the summed stems. You can probably tell from the spectrogram in the below screenshot where I flipped the crossfade slider over to the Spleetered (Spleeted?) version.
The output stems are pcm_s16le, 44100 Hz, stereo, s16, 1411 kb/s
, so it’s not like the file itself is at fault here.
Is this expected? Can this be tuned/changed somehow?
Issue Analytics
- State:
- Created 4 years ago
- Comments:8 (4 by maintainers)
@khaleelyo
Try using this cmd :: python3 -m spleeter separate -i audio_example.mp3 -o output -p spleeter:2stems-16kHz
We’ve just updated the FAQ for making clearer how you can actually perform separation above 11kHz. Notably we pushed alternate configuration files (
spleeter:2stems-16kHz
,spleeter:4stems-16kHz
andspleeter:5stems-16kHz
) that perform separation up to 16kHz and explained how you can set upper separation frequency in the config file if you need another value.