Closed diejung closed 4 years ago
@diejung
cd
command), then run python check-install.py
spleeter -h
show in CMD.exe?if you need help with any of this feel free to ask in the spleeeter max channel in discord: https://discord.gg/x5YjA9
also if you copy the command in max console that starts with spleeter separate -i...
, paste it in CMD.exe, then hit enter, what happens?
Sorry for the late reply, this is what happens when I run my check install after actually installing the script, I'm not terribly knowledgeable on github or coding / scripting in general.
this is spleeter -h:
this is with spleeter separate -i no variables changed through just cmd as admin -
this is what happens when i run cmd in the install folder and do the same command -
I tried adding in what i thought would be the correct command for a random reference track and this is what it spat out:
@diejung your last command is almost correct, just replace the ${} symbols. should look like this:
Took a little bit of time to try and get the VST up and running and that was even more confusing, I ran it and it seems it correctly sent the stems to the spleeter-native folder i have installed.
I am in the discord btw if that makes troubleshooting easier! I'm die jung.
something new that comes up when I try to re-run it in Ableton:
something new that comes up when I try to re-run it in Ableton:
that's usually fixed by step 3 of https://github.com/diracdeltas/spleeter4max/tree/feature/native-spleeter#windows-steps.
if .JS is already removed from PATHEXT, i'm not sure what could be wrong here.
js seemed to have reinstalled itself after trying to get the VST up and running, so I cleared that again so it no longer shows up in PATHEXT and rebooted. Tried again in Max with a different reference track and this is what came up:
Maybe I have to just go the cmd route? Was hoping that I could just make it easy via the m4l plugin, but maybe my computer doesn't want me to do that for whatever reason.
WAIT! I found another troubleshooting tip to have spleeter.exe run as admin and now it's working fine and dandy. Thank you so much for the help! I think this can be closed now.
great!
After a LOT of tinkering, I was able to actually get everything installed correctly (or so I thought) and I'm still having issues with getting this up and running. I'll run it in ableton and it'll do the "Spleeter is running, this may take a minute" with no luck. I've tried replacing the spleeter separate function with Python -m spleeter separate, no luck. I have both spleeter and the files im trying to split on the same drive, my python and ffmpeg are on my OS drive, no dice. Tried deleting the execSync variable, no luck. I tried installing the checker (where my spleeter is installed) and it gives me this below:
Here are some more screenshots showing where everything is set up, including my file directory path, CMD prompt verifications, etc.
I'm kind of at a loss as to where to go from here, as I've spent the past day or so trying to get this to work and doing self-troubleshooting with no luck getting past this point. Any help would be greatly appreciated.
Max Console Screenshots
Info: