-
Notifications
You must be signed in to change notification settings - Fork 2.9k
5. FAQ
- Can i try Spleeter without installing it ?
- Why produced stems are identical with the input sample ?
- Why do i have some stems not written to disk ?
- Why do i have no output produced ?
Yes. You can give it a try using the dedicated notebook through Google Colab.
If produced stems are identical to the input, you may think that no separation has been performed. The problem is that the library didn't found a model for performing separation and thus, do not apply any transformation to the provided sample, resulting in identical output stems.
As mentioned in the dedicated model page, model files are downloaded automatically from GitHub associated release if not found on disk. So if you have identical stems at the end it probably means that the downloading step didn't went well.
We are currently working on this to make model download associated error more reliable. Meanwhile if you can not get rid of the issue a workaround consists in downloading model archive manually from the release page
If no output is produced neither log record indicating that stems has been written to disk, it means that your separation process has been killed or crashed. The most common reason involved is a lack of memory, indeed the used model is memory intensive and requires lot of RAM available. If you can not increase your free memory a workaround is to perform separation on smaller segments of your input file and join resulting stems for each segments.
You can do that by splitting manually your input file with any library or software that allows you to edit audio file. Or you can use -d
option for setting duration :
spleeter separate -i ... -o ... -d your_duration
Which will process first your_duration
second(s) only of your sample. We will soon add a parameter for setting starting offset.
For the same reason exposed before.