We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I'd love to see an option for wxmp3gain to use N-number of CPU threads to analyze tracks in parallel to help speed up processing large libraries.
So for example, if the OS reports 8 CPU threads, 8 instances of mp3gain would run to each process a separate mp3 file.
The text was updated successfully, but these errors were encountered:
Or configurable thread count, max would be actual CPU thread count.
Sorry, something went wrong.
Yes, more flexible with a sensible max.
What should default be? I prefer the idea of using all threads by default... Perhaps N-1 to keep the system more responsive?
Alternatively, you can spawn the processing threads with BelowNormal priority across all N threads and you won't even feel it running at all...
Sensible default is usually (at least most of the times, what I've have seen) calculated: Thread count/2
No branches or pull requests
I'd love to see an option for wxmp3gain to use N-number of CPU threads to analyze tracks in parallel to help speed up processing large libraries.
So for example, if the OS reports 8 CPU threads, 8 instances of mp3gain would run to each process a separate mp3 file.
The text was updated successfully, but these errors were encountered: