Spleeter – software to generate “stems” from final mix
- This topic is empty.
-
Posts
-
I didn’t try that program, but I recently installed tensorflow GPU for another project and I had a bit of trouble to make the GPU work too, I just didn’t take the required versions as seriously as I needed. When they say 10.0 for CUDA for example I assumed that 10.1 would work just fine, but I was wrong, 10.0 was explicitely needed. When they say that Python 3 would work just fine, I thought that the new Python 3.8 would, but it didn’t, I had to use Python 3.7. I don’t know if I was the one that can’t read, or if they weren’t precise enough on the TensorFlow website, but yeah, I hope this is your issue. That’s for TF2.0 by the way, so if that software uses TF 1.x, they will most likely require other versions? idk, but triple check that.
Anyone know if this will run on 32 bit Windows 7?
Basically you’re asking if TensorFlow will run on win7 32bit, and this answer will be on the TensorFlow website.
I didn’t try that program, but I recently installed tensorflow GPU for another project and I had a bit of trouble to make the GPU work too, I just didn’t take the required versions as seriously as I needed. When they say 10.0 for CUDA for example I assumed that 10.1 would work just fine, but I was wrong, 10.0 was explicitely needed. When they say that Python 3 would work just fine, I thought that the new Python 3.8 would, but it didn’t, I had to use Python 3.7. I don’t know if I was the one that can’t read, or if they weren’t precise enough on the TensorFlow website, but yeah, I hope this is your issue. That’s for TF2.0 by the way, so if that software uses TF 1.x, they will most likely require other versions? idk, but triple check that.
I know it’s my fault that I’ve been rushing into testing spleeter without paying much attention to requirements and setup, but at this time of the year for various reasons my time for hobby is near-zero… but at the same time the spleeter documentation could really be more helpful than it is.
In my case, when reading the wiki, I checked my NVIDIA control panel and it seemed to me CUDA drivers were already installed. On CUDA website there seemed to be no drivers to download anyway but rather a “toolkit” for developers. The spleeter wiki didn’t make me think I would need to actually write any code, just to have drivers so that the spleeter processing would be redirected to the GPU instead of the CPU, and make everything much faster. But whenever I tried to activate the GPU mode in Conda, spleeter always crashed.
Yesterday I tried to install the CUDA toolkit and see if it made any difference (mainly because I seemed to understand that it also updates the drivers themselves). I made sure to download 10.0 and not the newer ones. That’s a 1.5 GIGAbyte stuff to download and install… and I am not sure it made a difference. Now GPU mode doesn’t crash* but it still takes half an hour to complete.
*actually in one case my PC got completely stuck and I had to power off in the hard way, then it took half an hour just to recover
Then I noticed from here https://docs.nvidia.com/cuda/cuda-quick-start-guide/index.html#windows that CUDA installation instructions also tell me to install Visual Studio and build this “nbuild” project with it. But I don’t get the point, is this just for testing out CUDA or is this actually required when using CUDA from another program (i.e. spleeter)? I do not expect to be required to do any coding for using spleeter…
You shouldn’t need to build anything for CUDA to work fine with TensorFlow. I’m pretty sure you can start python and try to import tensorflow and see if it loads your GPU as expected. If it does, then the issue may be with spleeter? idk at this point to be honest. Assuming you followed the TensorFlow installation instructions for the version you are trying to run (which I believe is 1.5), it should work. The only thing I’d watch is your Python version, it’s not mentionned anywhere on the TensorFlow website but Python 3.8 doesn’t work yet with it so gotta install Python 3.7 (unless that was fixed in the last week, which is totally possible).
The only thing I’d watch is your Python version, it’s not mentionned anywhere on the TensorFlow website but Python 3.8 doesn’t work yet with it so gotta install Python 3.7 (unless that was fixed in the last week, which is totally possible).
Thanks! I definitely need to double-check that… I had Python for a while and don’t remember what version might be.
I am ready to use spleeter-generated tracks to create some custom
” src=”/wp-content/uploads/invision_emoticons/default_SA_smile.gif” />At the moment, spleeter generates 5 separate tracks:
– vocals (including harmonies)
– drums
– bass
– piano
– other (everything else to sum up to the original audio)
If the song doesn’t have real piano, it makes sense to run spleeter in 4-tracks mode, but it doesn’t hurt to still use 5-tracks mode anyway and eventually merge piano+other in Reaper (you should not throw the piano track away even if it seems almost blank, otherwise the sum won’t match the original audio perfectly).
Now the question is what to do with the “other” track in RB3. Depending on the song, “other” may contain guitar(s), keyboard(s) and additional instruments such as harmonica, winds and strings. I think there are mainly two options:
1) The obvious option would be in Magma to map “other” into the background track, and use an empty file for both guitar and keys in-game. This means that the usual “cancellation on a miss/error” feature of RB3 will work for drums and bass, but not guitar and keys.
2) The alternative (especially useful when “other” contains only guitar + keyboard) is to drop the volume of the “other” track in Reaper to half, then use it twice in Magma, once for guitar and once for keyboard. This means that missing notes or making mistakes on guitar/keys will lower their volume but not completely cancel them. However I am not sure if this might sound horrible when using the whammy bar on guitar or bending strip on keys?
Also, generally speaking, the individual tracks sound fairly good but not perfect. This means that, whenever ONE player makes mistakes, the remaining tracks still sound quite good together; but the MORE players make mistakes, the worst the remaining tracks will sound.
I am not sure which of the 2 options I will choose, but I am currently thinking that because of these limitations, I’d rather provide also a single-track version.
I’ve been using RX7 for this and results have generally been good, especially for drums and vocals.
yep i use that for isolating the vocals and the drums for make it good… but i cannot release isolated just to understand that what i could to put a note
” src=”/wp-content/uploads/invision_emoticons/default_SA_biggrin.gif” />I am ready to use spleeter-generated tracks to create some custom
” src=”/wp-content/uploads/invision_emoticons/default_SA_smile.gif” />At the moment, spleeter generates 5 separate tracks:
– vocals (including harmonies)
– drums
– bass
– piano
– other (everything else to sum up to the original audio)
If the song doesn’t have real piano, it makes sense to run spleeter in 4-tracks mode, but it doesn’t hurt to still use 5-tracks mode anyway and eventually merge piano+other in Reaper (you should not throw the piano track away even if it seems almost blank, otherwise the sum won’t match the original audio perfectly).
Now the question is what to do with the “other” track in RB3. Depending on the song, “other” may contain guitar(s), keyboard(s) and additional instruments such as harmonica, winds and strings. I think there are mainly two options:
1) The obvious option would be in Magma to map “other” into the background track, and use an empty file for both guitar and keys in-game. This means that the usual “cancellation on a miss/error” feature of RB3 will work for drums and bass, but not guitar and keys.
2) The alternative (especially useful when “other” contains only guitar + keyboard) is to drop the volume of the “other” track in Reaper to half, then use it twice in Magma, once for guitar and once for keyboard. This means that missing notes or making mistakes on guitar/keys will lower their volume but not completely cancel them. However I am not sure if this might sound horrible when using the whammy bar on guitar or bending strip on keys?
Also, generally speaking, the individual tracks sound fairly good but not perfect. This means that, whenever ONE player makes mistakes, the remaining tracks still sound quite good together; but the MORE players make mistakes, the worst the remaining tracks will sound.
I am not sure which of the 2 options I will choose, but I am currently thinking that because of these limitations, I’d rather provide also a single-track version.
whoa! – i’ve been encounter that… that was i was thinking with that, Harmonix could do this from the music, hmmm… i got the idea…
Thanks!
I can’t get the GPU mode working, which supposedly speeds up the whole processing. The CPU mode still crashes often, generally takes about half an hour to produce results, and in most cases it doesn’t output all the stems, so I have to repeat the stems generation a few times per song. Overall I expect a couple of hours to process one song, but it is really “time consuming” only for my PC, not for me because all I have to do is write a command line and wait for the stems… so despite all the flaws I can accept the situation
” src=”/wp-content/uploads/invision_emoticons/default_SA_smile.gif” />Now the real question is whether the stems produced are usable for RB3 customs. When you listen to the separate stems, they sound pretty bad, so I wonder whether players missing notes in-game for a few seconds will make the audio also sound bad. But if you listen to all stems simultaneously, they definitely add up to the original (good) audio.
did you try spleeter-gpu?
- You must be logged in to reply to this topic.