Arturia Pigments 4 has landed

[wilkins_micawber]

I had problems with Pigments while my system was overclocked that disappeared when i returned to my default clock. It was the first overclock issue Ive ran into in 2 years. Now im always at stock (plus default auto boost) intel chip

[Teksonik]

I'm going to try it on both Windows/Mac VST/AU today.

Edit:
I've tried several presets in Live and FLS (both the latest) on Windows both VSTs and couldn't hear anything when I disable the engines and filters. It still calculates the same CPU I guess.

It seems to happen when this filter routing is selected:

Pigments 121822-3.png

What Arturia's support did say?

If I can't find the steps to reproduce the issue all I'll get (from any developer's support) is "that doesn't happen here".

[EnGee]

I'm going to try it on both Windows/Mac VST/AU today.

Edit:
I've tried several presets in Live and FLS (both the latest) on Windows both VSTs and couldn't hear anything when I disable the engines and filters. It still calculates the same CPU I guess.

It seems to happen when this filter routing is selected:


Pigments 121822-3.png

What Arturia's support did say?

If I can't find the steps to reproduce the issue all I'll get (from any developer's support) is "that doesn't happen here".

Yes you are right. Let's find a way to reproduce it

[Teksonik]

Ok some progress today. I tried the VST 3 version and the issue occurs there as well so it's not a version issue.

I got the issue to occur in just a couple of minutes again this morning. Engine 2 was still producing sound even though the light was off. Saving and reloading the patch corrected the issue.

Try this patch:

Error 11.zip

Then repeatedly click on/off the Engine 2 I/O light. Eventually I can get it to either stick on and make no sound or stick off and still make a sound.

To me it's just a graphics issue where sometimes the light can get "confused" and stop showing the proper status of the switch. The question remains whether it's just an issue with my system or is this an actual bug.

If others can reproduce the issue then I'll pass along what I have so far to Arturia support.

EDIT: I've managed to reproduce the issue on this system as well but it took more clicks to trigger it so that would tend to point away from a system specific issue.

[aShane]

I had problems with Pigments while my system was overclocked that disappeared when i returned to my default clock. It was the first overclock issue Ive ran into in 2 years. Now im always at stock (plus default auto boost) intel chip

Wow, you're lucky the overclockXpigments didn't blow the cpu into ember. I remember doing this about 5 years ago, now I think it's better not to play with this on new device

[Fannon]

Try this patch:

Error 11.zip

Then repeatedly click on/off the Engine 2 I/O light. Eventually I can get it to either stick on and make no sound or stick off and still make a sound.

Couldn't reproduce it, but maybe I haven't clicked often enough? I assume you need to play a sound and then click it off repeatedly?

[EnGee]

@Teksonik:
Great! I'll test it with my two setups when I come home.

[Teksonik]

Try this patch:
Error 11.zip
Then repeatedly click on/off the Engine 2 I/O light. Eventually I can get it to either stick on and make no sound or stick off and still make a sound.

Couldn't reproduce it, but maybe I haven't clicked often enough? I assume you need to play a sound and then click it off repeatedly?

Yes just hold down a note and click the lights on/off.

Sometimes it takes 20-30 times and sometimes it happens without even trying while just making a patch and sometimes I can't get it to happen at all. Bizarre...

@Teksonik:
Great! I'll test it with my two setups when I come home.

Excellent. Let us know how it goes.

[Teksonik]

Here's a few presets. I still want to tweak them some more but think I'll give Pigments a rest for awhile.

Anyway at least they're free. No sign ups, no "add to cart"........

[tactile_coast]

Just had some time to catch up with 4 and where its not noticeable on my main PC the CPU performance on my old laptop has massively improved to the extent I can start using Pigments on it again, albeit with careful preset selection. Plus I really enjoyed the play view which is great for quick sound design and found the quick filter scrolling is an easy way to put a new spin onto some of the old presets.

[EnGee]

Try this patch:
Error 11.zip
Then repeatedly click on/off the Engine 2 I/O light. Eventually I can get it to either stick on and make no sound or stick off and still make a sound.

Couldn't reproduce it, but maybe I haven't clicked often enough? I assume you need to play a sound and then click it off repeatedly?

Yes just hold down a note and click the lights on/off.

Sometimes it takes 20-30 times and sometimes it happens without even trying while just making a patch and sometimes I can't get it to happen at all. Bizarre...

@Teksonik:
Great! I'll test it with my two setups when I come home.

Excellent. Let us know how it goes.

I couldn't import it in Windows 11! Even if I change the file name to Error 11.pgtx! It says importing is successful but there is nowhere to find! (I have the other preset that you said it consumes a lot of CPU which it did, and it could be imported normally after changing the extension to .pgtx).

[cb8rwh]

I am hoping this is just something I have overlooked and is actually easy, but how do you modulate the coarse pitch precisely, e.g. if I assign aftertouch to modulate the pitch by 2 semitones up. I know I can quantize the modulation, but then it steps through the values one semitone at a time, whereas I want it to do so smoothly.

When you assign a control etc to the coarse pitch the range is -1 to +1 - which does not lend itself to accurate pitch modulation.

Hope that makes sense and is something that is easy to do.

[Sampleconstruct]

I am hoping this is just something I have overlooked and is actually easy, but how do you modulate the coarse pitch precisely, e.g. if I assign aftertouch to modulate the pitch by 2 semitones up. I know I can quantize the modulation, but then it steps through the values one semitone at a time, whereas I want it to do so smoothly.

When you assign a control etc to the coarse pitch the range is -1 to +1 - which does not lend itself to accurate pitch modulation.

Hope that makes sense and is something that is easy to do.

1 octave equals 0.17, 0.5 would be 3 octaves so that's a rounded value.

[cb8rwh]

Thanks for that. I have just worked out a way to get it pretty accurate using the combinate - here's a crappy explanation.

Totally hacky and difficult to explain - you have to use Combinate to modulate the coarse pitch, use the multiply type and set the amount to 0.167 - that value is basically 1 divided by 60 (the total semitone range of the coarse pitch). That 0.167 is really 0.1666 recurring.

Now when you drag the COMB source onto the Coarse pitch knob, set the number of semitones using the decimal value - so 1 semitone is 0.01, 2 semitones is 0.02 etc

Would be so much easier if they allowed +/- semitones when modulating the coarse knob.

[liv]

Is it possible to save a picture to a custom bank?