ffprobe Error

Description

I downloaded homebrew and ffmpeg to run the code. Works fine with the audio_example given, but when I try to use another song from my library I get an ffprobe error. Also I’m putting this song in the same directory as the audio_example.mp3.

Step to reproduce

1. Installed using git clone https://github.com/Deezer/spleeter conda env create -f spleeter/conda/spleeter-cpu.yaml conda activate spleeter-cpu
2. Run as spleeter separate -i spleeter/Home.mp3 -p spleeter:2stems -o output
3. Got INFO:spleeter:Loading audio b'spleeter/Home.mp3' from 0.0 to 600.0 WARNING:spleeter:ffprobe error (see stderr output for detail) error

Output

The code works fine with the original audio given. This would be the output.

INFO:spleeter:Audio data loaded successfully
INFO:spleeter:File output/audio_example/vocals.wav written
INFO:spleeter:File output/audio_example/accompaniment.wav written

Environment

OS	MacOS
Installation type	Conda
RAM available	4 GB
Hardware spec	CPU

Additional context

[SINCd]

ok guys… so I don’t know if this will help anyone or not - but I was researching, installing all sorts of shit (i’m a newbie here) over and over and kept replicating the same problem that we are all having.

I installed via pip, homebrew, and everyway I could follow or find but with no results.

I did the same with ffmpeg using above methods (homebrew etc) still same result.

Then I noticed another folder called spleeter INSIDE the spleeter folder that had been created by the installs. When I shifted my file into that folder ie. ‘/User/###/spleeter/spleeter’ - it worked without a hitch. no more this ffprobe or 0-6.00 errors and the rest. It just worked. Now, maybe this is the way it was meant to work all along, but with respect to the creators/devs, the manual didn’t mention this? (put the file in spleeter/spleeter) or perhaps it did… but with the complicated installs and jumping around webpages… i could have missed it. The odd thing, is that the audio example is still in the top folder… so IDK -wtf is going on. lol. The guide is not easy for newbie people who’ve never used command lines, things like pip or homebrew and terminal concepts. But I did get it working and my troubles were rewarded, but still don’t know if it was luck or a solution…?. hopefully, it may help or steer others and get it working for them. I included a screenshot in hopes it may help… but I’ve done about 10 rips at 2 track and 5 track and its bloody worth the effort. Thank you so much to the developers for this! but… can we make some sort of graphical interface or an easier streamlined process would be amazing!!

Much respect and honour to the devs/users, and i’m crossing fingers this just may work for someone. Cheers.

[stenalpjolly]

Hi

Got the same issue with docker as well

docker run -v $(pwd)/output:/output spleeter:cpu separate -i audio_example_new.mp3 -o /output
INFO:spleeter:Downloading model archive https://github.com/deezer/spleeter/releases/download/v1.4.0/2stems.tar.gz
INFO:spleeter:Extracting downloaded 2stems archive
INFO:spleeter:2stems model file(s) extracted
OMP: Info #212: KMP_AFFINITY: decoding x2APIC ids.
OMP: Info #213: KMP_AFFINITY: x2APIC ids not unique - decoding legacy APIC ids.
OMP: Info #149: KMP_AFFINITY: Affinity capable, using global cpuid info
OMP: Info #154: KMP_AFFINITY: Initial OS proc set respected: 0-3
OMP: Info #156: KMP_AFFINITY: 4 available OS procs
OMP: Info #157: KMP_AFFINITY: Uniform topology
OMP: Info #159: KMP_AFFINITY: 4 packages x 1 cores/pkg x 1 threads/core (4 total cores)
OMP: Info #214: KMP_AFFINITY: OS proc to physical thread map:
OMP: Info #171: KMP_AFFINITY: OS proc 0 maps to package 0 
OMP: Info #171: KMP_AFFINITY: OS proc 1 maps to package 1 
OMP: Info #171: KMP_AFFINITY: OS proc 2 maps to package 2 
OMP: Info #171: KMP_AFFINITY: OS proc 3 maps to package 3 
OMP: Info #250: KMP_AFFINITY: pid 1 tid 1 thread 0 bound to OS proc set 0
OMP: Info #250: KMP_AFFINITY: pid 1 tid 51 thread 1 bound to OS proc set 1
INFO:spleeter:Loading audio b'audio_example_new.mp3' from 0.0 to 600.0
WARNING:spleeter:ffprobe error (see stderr output for detail)