Skip to content
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

Initial DC offset in output files from Spleeter 1.5.1 #392

Closed
boy1dr opened this issue May 23, 2020 · 3 comments
Closed

Initial DC offset in output files from Spleeter 1.5.1 #392

boy1dr opened this issue May 23, 2020 · 3 comments
Labels
bug Something isn't working

Comments

@boy1dr
Copy link

boy1dr commented May 23, 2020

Description
Using Version 1.5.1 of Spleeter, the output files generated using 2, 4 & 5 stem modes begin with a DC offset. The result of which is a pop when the output audio is played back.
Spleeter V1.4.3 does not exhibit this issue.

Step to reproduce
Install Python3.7
Run "python -m pip install spleeter"
Run "python -W ignore -m spleeter separate -i song.mp3 -o c:\temp -p 2stems.json"
No errors observed.
Check output files using audacity, files begin with DC Offset.

Output
Processing C:\Users\chris\Desktop\original.mp3
INFO:spleeter:File C:\temp\original/accompaniment.wav written succesfully
INFO:spleeter:File C:\temp\original/vocals.wav written succesfully

Environment
OS: Windows10 pro 64bit
Installation type: Python3.7 (pip) (tensorflowCPU)
RAM available: 32GB
Hardware spec: AMD Ryzen 5 3600 / GTX1660Ti

Additional context
The JSON config file can be viewed here
https://makenweb.com/2stems.json
An image of the DC Offset problem can be viewed here
https://makenweb.com/spleeter_1.5.1_dc_offset.png

@boy1dr boy1dr added bug Something isn't working invalid This doesn't seem right labels May 23, 2020
@mmoussallam mmoussallam removed the invalid This doesn't seem right label May 23, 2020
@mmoussallam
Copy link
Collaborator

Hi @boy1dr ,

Indeed I can reproduce with the Librosa backend (used by default in 1.5.1). You can circumvent this by adding -B tensorflow in your command until we fix it. Thanks for pointing that out.

@mmoussallam
Copy link
Collaborator

Hi @boy1dr

We've made some changes that should have fixed this issue. Let us know if you still encounter it.

@boy1dr
Copy link
Author

boy1dr commented Oct 19, 2020

@mmoussallam Version 2.0 is clean as, seriously good work :)
Thanks for letting me know!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants