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
Stems write - Format not recognised #19
Comments
thanks for your contributions. I don't really see a difference between the arguments you use and the one used in ffmpeg -y -f s16le -acodec pcm_s16le -ar 44100 -ac 2 -i mix.wav -i vocals.wav -i drums.wav -i bass.wav -i other.wav -map 0 -map 1 -map 2 -map 3 -map 4 -vn -acodec aac -ar 44100 -strict -2 -loglevel error -ab 256000 stems.mp4 maybe you can point me to the relevant changes one would need to make to improve the write functions? |
The difference should be in the codec.
For some reason, using
Do you see any error in what I am doing? |
you mean the output codec ( Lines 79 to 84 in ebbaec8
Are you writing mono files? The STEMS format is stereo only, that is why its hardcoded here. I might need to add a check for this to warn users... |
Yes in this case is mono. |
Hi, sorry if I am reopening the issue. I am saving the audio setting 2 channels as:
Then I am collecting the stems and creating S but the error still pops up.
I also have these warnings. Could the error above be related to those?
|
[UPDATE] |
has this issue been addressed? |
Sorry, I solved using the |
Hello,
As you stated in the documentation the stems write doesn't always work well.
I am using this command with ffmpeg to create a STEM file:
I then tried to read it back using the musdb library and it works well.
I was wondering if this could be included in your library to finally make it work properly.
I unfortunately do not have much time to work more on this and ask for a pull request but I made a simple implementation if could be of any help.
Also check this homebrew-ffmpeg if the right codecs are not installed properly in the official ffmpeg distribution.
The text was updated successfully, but these errors were encountered: