Pigments sequencer bug still remains after v6 if used through Analog Lab

Software Instruments Pigments
#1

Hey,
I am happy with v6, which fixed the sequnce triggering bug (the start is delayed by 1 note) inside the Pigments VSTi. I also tried the same preset inside Analog Lab and the problem still persisted there. Can you confirm that the bug is still there if Pigments is used via Analog Lab?
Cheers,
Adam

#2

Hi @Lpneo. Welcome to the community.

That sequencer bug was fixed already in Pigments version 5.0.4.
It should also work in Analog Lab. Are your Analog Lab updated to the current version 5.10.7 that still use Pigments 5?

Pigments 6 is not supported in Analog Lab until Arturias next update/ version of Analog Lab than the current.

#3

Yes,
For me the bug was stil there in Pigments 5, though I only used it in Analog Lab.
My Analog Lab is at 5.10.7 now, so I guess I just have to wait the Analog Lab patch that makes P6 supported.

#4

That’s strange.

Like you can see here some of us users reported the bug fixed in Pigments 5:

It work fine it my Analog Lab.

If you read the release notes for both Pigments and Analog Lab, then they state it’s fixed - and it was. So i don’t understand why you have this issue, if your Analog Lab is fully updated.
I don’t know if it’s worth investigating your issue. Especially if you can wait for Pigments 6 support in Analog Lab.

However - if you wish, then a reinstall of the latest Analog Lab might help you.

#5

I think I encountered the bug in question today. For unrelated reasons, I had just updated to Analog Lab Pro 5.11.1.6049, but when I ran my Bitwig Stepwise sequencer, Analog Lab places notes for a bit, but then stops, and only rendering Analog Lab “inactive” through Bitwig and then re-enabling allows it to play. This is true of all presets I’ve tried so far. One I can confirm will sequence fine through Pigments (“Acid Lord”) fails in the same fashion if used via Analog Lab Pro.

#6

Hi @TruePrism. Welcome to the community.

The bug was about Pigments internal Sequencer was not playing the first note of the internal created sequence.
That bug is’nt there anymore.

You seem to use Bitwigs sequencer. It can be an issue with that.

I don’t have the preset you mention. So i can’t test. It’s always best to name Factory presets.

Please create a new topic, if you still have the issue.

#7

Thanks for being so responsive, LBH. As I mentioned, I experience the bug with all presets and the Stepwise sequencer. It seems to happen on a steep part of an LFO when the LFO rapidly alters the note being played. I will create a new topic.