Repro's Multi-Core Support

[e-crooner]

We are having a discussion on multi-core support in another thread, specifically whether one is supposed to turn MC support off in a plugin if the DAW itself supports multiple cores, as the DAW developer recommends.

Anyway, when doing tests, I noticed that when I set my DAW to a single thread, Repro's MC support spreads the load on only 4 of my 8 threads (I have a 4-core processor). The other four threads remain idle. And when I add a second instance of the synth, they add to the same 4 threads already in use, instead of using the other 4 threads.

Is it supposed to be that way? Just wondering...

[EvilDragon]

Open the Preferences panel in Repro, there's a setting on how many cores to use.

[e-crooner]

Ah, thanks.
Interestingly there is no difference when setting it to 6 or 8 threads, but setting it to 4 threads leaves two more threads idle.

[X86]

Ah, thanks.
Interestingly there is no difference when setting it to 6 or 8 threads, but setting it to 4 threads leaves two more threads idle.

Has this been fixed yet?

[Urs]

Ah, thanks.
Interestingly there is no difference when setting it to 6 or 8 threads, but setting it to 4 threads leaves two more threads idle.

Has this been fixed yet?

Not sure what to "fix" here. When multiple instances of Repro *share* the threads they render on, they reduce the overhead of multicore support. You get more CPU in general.

Repro's multithreading works on a per-voice base. If Repro doesn't use up all threads, it's probably because you probably need a considerable number of voices - i.e. multiple instances - to keep more than 6 threads busy. A single instance is likely to never use 8 threads, I would not be surprised if it never exceeded 4.

[X86]

Ah, thanks.
Interestingly there is no difference when setting it to 6 or 8 threads, but setting it to 4 threads leaves two more threads idle.

Has this been fixed yet?

Not sure what to "fix" here. When multiple instances of Repro *share* the threads they render on, they reduce the overhead of multicore support. You get more CPU in general.

Repro's multithreading works on a per-voice base. If Repro doesn't use up all threads, it's probably because you probably need a considerable number of voices - i.e. multiple instances - to keep more than 6 threads busy. A single instance is likely to never use 8 threads, I would not be surprised if it never exceeded 4.

Nice, thanks for the clarification!

[e-crooner]

Repro's MC support works very well, without it I could not use Repro in a useful manner because my DAW's internal MC support can't seem to handle the heavy load well, although the developer says one should disable plugins' internal MC support.