Open pablocouto opened 7 years ago
Good call. See also #673 and #663.
Do you think it makes sense to have this be specific to the replaygain plugin, without going further into https://github.com/beetbox/beets/pull/673 and https://github.com/beetbox/beets/pull/663?
Sure, at least as a first step! We can always generalize it later.
I've been trying to call beet replaygain --threads=32
but only one core is being used, still.
Which backend are you using?
We don't support parallel processing for gstreamer
and audiotools
currently.
I tried gstreamer and then ffmpeg. Both had the same problem. I was running
beet replaygain --threads=32 -a -w -f
The relevant section from beet config
output:
replaygain:
backend: ffmpeg
threads: 16
overwrite: no
auto: yes
parallel_on_import: no
per_disc: no
peak: 'true'
targetlevel: 89
r128: [Opus]
r128_targetlevel: 84
EDIT: nevermind, started the command again and it started spawning more ffmpeg processes than before. It still spawns fewer than 32 and takes a while to ramp up from 0 to more than 1, but it eventually does get there.
Problem
The
replaygain
plugin doesn’t appear to make use of multicore capacities. On my machine, I see increased activity on only one core out of four.In my opinion, it would be useful to be able to configure the plugin to analyze different albums or tracks at the same time.
Setup
My configuration (output of
beet config
) is: