Dune 3 or Arturia Pigments?

[fmr]

I've noticed that some of the presets drive my CPU (AMD FX Vishera 6-core @ 3.5 GHz) up to about 55%. Has anyone found a way to put Pigments into draft mode?

There isn't a draft mode. Pigments is usually light on the CPU. Of course, if you go crazy on the modulations (and it's so easy to do that ) the CPU consumptions starts to go up. There's nothing that can be done about that.

Bear in mind that, when you have Pigments at 55%, if you were using others synths to do the same, they would probably be already at 90%

[Cinebient]

I've noticed that some of the presets drive my CPU (AMD FX Vishera 6-core @ 3.5 GHz) up to about 55%. Has anyone found a way to put Pigments into draft mode?

There isn't a draft mode. Pigments is usually light on the CPU. Of course, if you go crazy on the modulations (and it's so easy to do that ) the CPU consumptions starts to go up. There's nothing that can be done about that.

Bear in mind that, when you have Pigments at 55%, if you were using others synths to do the same, they would probably be already at 90%

Not if they support multiple cores like Dune 3.

[Mythozchtryx]

I've noticed that some of the presets drive my CPU (AMD FX Vishera 6-core @ 3.5 GHz) up to about 55%. Has anyone found a way to put Pigments into draft mode?

There isn't a draft mode. Pigments is usually light on the CPU. Of course, if you go crazy on the modulations (and it's so easy to do that ) the CPU consumptions starts to go up. There's nothing that can be done about that.

Bear in mind that, when you have Pigments at 55%, if you were using others synths to do the same, they would probably be already at 90%

Okay. I had just started it up for the first time and I was exploring a few presets. I imagine some of the presets are probably configured to deeply inspire, and they did use a lot of modulations. I did find some presets that still sounded good and were less taxing on the CPU. Thanks for the response!

[fmr]

I've noticed that some of the presets drive my CPU (AMD FX Vishera 6-core @ 3.5 GHz) up to about 55%. Has anyone found a way to put Pigments into draft mode?

There isn't a draft mode. Pigments is usually light on the CPU. Of course, if you go crazy on the modulations (and it's so easy to do that ) the CPU consumptions starts to go up. There's nothing that can be done about that.

Bear in mind that, when you have Pigments at 55%, if you were using others synths to do the same, they would probably be already at 90%

Not if they support multiple cores like Dune 3.

Multiple cores support is useless when you run it inside a DAW. It may even create conflicts with DAWs own multiple core management.

[Cinebient]

I've noticed that some of the presets drive my CPU (AMD FX Vishera 6-core @ 3.5 GHz) up to about 55%. Has anyone found a way to put Pigments into draft mode?

There isn't a draft mode. Pigments is usually light on the CPU. Of course, if you go crazy on the modulations (and it's so easy to do that ) the CPU consumptions starts to go up. There's nothing that can be done about that.

Bear in mind that, when you have Pigments at 55%, if you were using others synths to do the same, they would probably be already at 90%

Not if they support multiple cores like Dune 3.

Multiple cores support is useless when you run it inside a DAW. It may even create conflicts with DAWs own multiple core management.

Not sure which DAW you use but this works great here in Logic. It‘s the lack of support which makes complex tools useless for me (like Falcon).
I can add a LOT more instances here and also if i make a really wild single patch in one instance which overloads my cpu i have no problem if i turn on mult-core support in these tools.
Things like Kaleidoscope f.e. are even must use it to run (at least on my machine).

[sacer]

Multicore isn't useless inside a daw, best examples are pad patches from repro-5, if u switch to multicore, the cpu consumption decreases from 60% to less then 20% CPU ussage. If I have 10 Instances of repro it also stays under 60%, so I see only advantage of multicore. I have a i7 5860x overclocked from 3ghz to 4,5 and one solo core with 4500mhz is not fast for every patch on repro-5, but my 8 cores have no problems with a lot of repro instances. On dune3 and pigments, i have no high cpu consumption, I wonder how to reach 55%
I sometimes have projects with 30 to 50 instances with diva and repro, and have switched them to multicore, so there is no negative effect on u-he synths or any DAW conflict if you have a power cpu.

[Cinebient]

Dune 3 supports up to 6 cores....just saying.

[zvenx]

Whilst indeed there is a point (a certain number of instances) when multi core in a plugin becomes counterproductive in a DAW. For 1-5 (higher on more modern multicore processors) or so instances it is a heaven sent.
At least in Cubendo.
rsp

[AnX]

I've noticed that some of the presets drive my CPU (AMD FX Vishera 6-core @ 3.5 GHz) up to about 55%. Has anyone found a way to put Pigments into draft mode?

There isn't a draft mode. Pigments is usually light on the CPU. Of course, if you go crazy on the modulations (and it's so easy to do that ) the CPU consumptions starts to go up. There's nothing that can be done about that.

Bear in mind that, when you have Pigments at 55%, if you were using others synths to do the same, they would probably be already at 90%

Not if they support multiple cores like Dune 3.

Multiple cores support is useless when you run it inside a DAW. It may even create conflicts with DAWs own multiple core management.

that would be just cubarse, naturally

the only company who fights against their own standards

[antic604]

Tough choice. Pigments has a really nice workflow, but I wasn't wowed by any of the presets - it sounds pretty cold & digital, with surprisingly high CPU hit. Dune on the other hand has that smooth, silky, punchy sound that I love in The Legend, moderate CPU usage, but the workflow is pretty convoluted.

I got both in the end, but mainly because I got Pigments with V Collection 6 at a good price

[zvenx]

I've noticed that some of the presets drive my CPU (AMD FX Vishera 6-core @ 3.5 GHz) up to about 55%. Has anyone found a way to put Pigments into draft mode?

There isn't a draft mode. Pigments is usually light on the CPU. Of course, if you go crazy on the modulations (and it's so easy to do that ) the CPU consumptions starts to go up. There's nothing that can be done about that.

Bear in mind that, when you have Pigments at 55%, if you were using others synths to do the same, they would probably be already at 90%

Not if they support multiple cores like Dune 3.

Multiple cores support is useless when you run it inside a DAW. It may even create conflicts with DAWs own multiple core management.

that would be just cubarse, naturally

the only company who fights against their own standards

That isn't my experience with Cubase.
I couldn't use many of u-he's plugins without their multicore enabled for instance, and I believe Urs himself has said why it isn't enabled by default is that indeed at some point it becomes diminishing returns.
I am pretty sure that isn't just in Cubase.
rsp

[exmatproton]

They are both very good, imho. I terms of depth (mod possibilities, routing options, FX amount (in Pigments you could use 9 reverbs for instance) and shear OSC mod options), i would choose Pigments. In terms of "workstation", i would choose Dune3.

Sound, options, FX, mods (although i prefer the way Arturia has implement this and more of each (3 lfo's, 3 env's, 3 types of cool random gen's, 3 mseg's and 2 multipliers/combinators), etc...are in both synths very good, if you ask me.

I would like to see more FM (pm, etc...) options in Dune3, but i would like to see osc to osc modulation (audio rate) in Pigments......

[Urs]

I couldn't use many of u-he's plugins without their multicore enabled for instance, and I believe Urs himself has said why it isn't enabled by default is that indeed at some point it becomes diminishing returns.

In think with Repro-5 we cut to the bottom of this. You can set the number of cores and the multicore support is optimized in a way that has next to no overhead with multiple instances. Though, only because we have never observed any doesn't mean they don't exists in other scenarios (CPU, host, whatever).

[Urs]

Of course, if you go crazy on the modulations (and it's so easy to do that ) the CPU consumptions starts to go up. There's nothing that can be done about that.

Hehehe, I'm sorry, but this statement irritates me. Of course modulation sources cost CPU. I.e. a synth should always be lighter if only one envelope is used instead of three. But in my opinion, the modulation itself should not incur extra CPU, no matter if that one envelope modulates two parameters or sixteen. Other developers may have a different view, but I think the best optimization is when you always assume the worst case, if people go crazy, that is. Otherwise things end up with a lot of conditions which make the worst case even more expensive than it needs to be.

[SLiC]

I couldn't use many of u-he's plugins without their multicore enabled for instance, and I believe Urs himself has said why it isn't enabled by default is that indeed at some point it becomes diminishing returns.

In think with Repro-5 we cut to the bottom of this. You can set the number of cores and the multicore support is optimized in a way that has next to no overhead with multiple instances. Though, only because we have never observed any doesn't mean they don't exists in other scenarios (CPU, host, whatever).

All good, but what about the OP's question, Dune 3 or Arturia Pigments?