-
Notifications
You must be signed in to change notification settings - Fork 211
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
Best multithreading setup for large projects #115
Comments
My thoughts on that topic are exactly the same. For Rhubarb 2, I'm thinking of implementing a built-in batch mode that will take a glob pattern of files and process them all using smart multi-threading. Until then, your best bet when it comes to processing speed is to go with your option 2. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi. I have a pretty large project with thousands of audio files, but most of them are quite short. When I look at the documentation, it seems like rhubarb only properly utilises multi-threading with longer audio files. So I'm wondering what would be a good way to do batch processing of large numbers of audio files to most effectively use the multi-threading? I'm thinking:
Curious to hear your thoughts. My current plan is to go with 2. Let me know if that's a good / bad idea. Thanks! :)
The text was updated successfully, but these errors were encountered: