-
Notifications
You must be signed in to change notification settings - Fork 16
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
Any luck with this? #8
Comments
Hello Paul, It depends on which Raspberry Pi you own, spoiler alert, you need a little stronger CPU to run SpleeterRT. This repo uses double spectrogram buffer to enable us to run SpleeterRT(1 second latency) on relatively low power device. What we haven't seen on my Github page is algorithmicly low latency SpleeterRT, the extremely low latency(46.4 ms) of it is currently non-open-source, due to business reason, it won't be open in short term, this one require a lot stronger CPU to run. We are running a startup since then where we've made advancements and offer our technologies for third-party developers, such as realtime ML audio tech (audio reparation, dereverberation, separation and more). You might like to contact [email protected] to initiate talks and I'm sure we can solve your challenges. Best regards, |
Hello James, thank you in advance for any response :) |
Hi, I'm not active in responding to Github issues. ok, here is the thing. The latency figure is 64ms - 10 seconds, the runtime complexity is not ultra demanding, although more demanding than open source counterpart. If you are interested, please contact [email protected] |
Hi James,
A buddy and I are embarking on working on something very similar to what it seems you worked on, getting Spleeter to run in real time on Raspberry Pi (ARM, low latency, real time, etc). Did you ever have any luck with this, or did you hit a wall? Any guidance you could provide would be much appreciated, and if it makes sense to create a consulting arrangement, we'd be interested in discussing that as well. Thanks in advance!
Paul
The text was updated successfully, but these errors were encountered: