Pigments FUNCTIONs are out of sync and FXs sometimes won't turn off

Hello everyone,

After Live 12.1 update the functions on my pigments are out of sync / behaving strangely.

If I have a simple function i.e. “init” (rampdown) it works fine. But if I select a complex one i.e “RHYTHMIC - 5” It won’t loop until the end and will not follow the drawing of the automation.

Also, sometimes effects like Delay and Unison remain on even if I turn them off and let the dry/wet at 0%.

I meant to capture this on a video but recording my DAW audio was a little harder than I imagined. Let me know if you’d like that and I’ll give it another try.

Has anyone experienced anything like it?

I’m on a M2 MacbookPro running Sonoma 14.6.1.

Thanks

Just FYI: Arturia plugins are not yet certified to run on Sonoma officially.

I assume this was not an issue before updating Live?

Does this behaviour occur in standalone Pigments?

Have you tried uninstalling and reinstalling Pigments?

Hey there @Funtmaster, thank you for your response.

I was not aware Sonoma was not yet officially covered, I guess I should have been more careful before updating my OS.

Yes, this issue has started after Ableton auto installed the 12.1 update. This is for the VST version of Pigments.

I tried the standalone Pigments just now and I have not seen these issues.

OK.

So, could you try uninstalling and reinstalling Pigments and in the process see if you can install a VST3 version as well as the VST2 version if thats all that was installed. If you can install both VST2 and 3, test again please.

1 Like

Hi all.
Welcome to the community @tiagoayresnunes.

Just some info.

Sonoma is supported.

This should not be the issue.

It’s the new Sequoia that’s not yet officiel supported:

Hey there @Funtmaster.

I’ve tried reinstalling both from the Arturia Service Center and with a downloaded installer and did not see any improvement. I kept the VST2 but did not see anything different.

There is this screen recording with audio where you can see the issue happening.

https://drive.google.com/drive/folders/1IAQC8JfxulVjtgJsKHnMxJSaQu-VqXfU?usp=sharing

Two werid things is that randomizing the function points and then reverting seem to fix the problem. Also, while using Zoom to capture the screen I noticed that just by using the ZoomAudioDevice to record ableton this issue would go away most of the time.

At any rate, I’m also in contact with support through ticket #1005553

Thanks

2 Likes

My bad - the naming convention is becoming too similar.

No worries @Funtmaster.
Agreed it’s hard to keep up.

@tiagoayresnunes .
Are you just holding a single note all the time in the video? Is that note on beat? The sync is based on when the note is triggered.
I don’t see the function retrigger with the kick, and you have set polyKBD as retrigger. The Function should start over at each keytrigger.

What happens if you trigger a new note on beat after you have changed pattern?

Hello @LBH, thank you for your help.

It’s only one long note on a midi clip playing nonstop. The issue happens until the 22 second mark on the video. There when I randomize the points and then undo this action the function synchrony returns to normal.

Retriggering the note while the issue is happening just retrigger the same out-of-synchrony incorrect pattern that was already playing before. “One”, “Loop” and “Free Running” options seem to give me exactly the same output.

Other than this and the FXs I also noticed that the modulations sometimes are active but not being shown on the user interface. E.g. I can see the modulation light move around but I don’t have the pizza-graph modulation amount to change. It also does not appear on the Matrix. The only way is to re-modulate the parameter and turning it off after.

All these multiple weird artefacts came into life after the 12.1 update so I am guessing these are related.

Thanks again.

Hi agin @tiagoayresnunes ,

This is interesting. Perhaps it tell us, that something in the audio signal route give latency. But i have no idea how, if you have a standard soundcard setup in your DAW. But perhaps check the settings anyway.

I can’t replicate your issue here.

I suggests you contact Arturia support through your account, if you can’t find the cause.