-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
High frequencies get cut? #15
Comments
It looks like all models only output up to 11 kHz. Would be nice to know if this is part of the model or stems from the original training data |
Hey Aarni, Thanks for your feedback. Indeed the default behavior is to cut frequencies above 11Khz but it can be changed in the settings. Read this comment for details. |
@mmoussallam but this still means that the models do not predict masks above 11khz, right? is this hardcoded in a training config? |
@mmoussallam Thank you for the clarification! |
We've just updated the FAQ for making clearer how you can actually perform separation above 11kHz. |
Just a quick follow up, I'm currently running a Mac OSX, Python 3.7.3, I also attempted to reinstall spleeter with the same results. Any idea whats going on here? Thanks, |
Try using this cmd :: python3 -m spleeter separate -i audio_example.mp3 -o output -p spleeter:2stems-16kHz |
Hey 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.where
hot_n_cold.wav
is apcm_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?
The text was updated successfully, but these errors were encountered: