Arturia Pigments 7

[chk071]

IIRC, they use some pretty heavy frameworks for their plugin development. That's probably the (unfortunate) reason.

I also found out some time ago (by someone posting about it here, never checked myself) that all their FX plugins introduce latency. That's bad as well, especially as it stacks up when you use a few of them in the plugin chain.

You know, I liked Arturia, but, they certainly have to work on these things.

[Teksonik]

All Arturia plugins take forever (like 20-30 seconds or so) to load the GUI the first time on my PC (Windows 10, Cubase 15).

So I wonder why it takes a long time for some users but not all users? There must be a reason, system hardware configuration or whatever the cause. Everyone is using the same plugin.

Finding out what that reason is might help Arturia fix the issue if they are motivated to do so.

As for the memory issue even loading an empty preset with both main engines set to Analog (no large samples) it still uses over 2 gigs of memory.

For comparison, Nexus 5 set to INIT only uses about 200 megs of memory and it's a much larger and more involved GUI at my preferred settings. So I can't see a logical reason why Pigments needs to use so much.

[Teksonik]

Okay after testing a little deeper, the memory issue seems like it could be related to the "Visualizer" presets found on the Play tab. Changing them does cause the memory to vary a bit between one or the other so it's possible that those visualizers and their assets are pre-loaded.

To be honest I never go to the Play tab and I absolutely hate the concept of a "visualizer" in an audio plugin. It's an utter waste of CPU/GPU cycles and quite possibly memory as well. It's a synth, not a video game.

It should be something that people have to opt in to for whatever reason, not something that is active and using resources by default.

It's just a theory but it wouldn't surprise me if the Visualizer and it's graphics presets are the cause of at least some of the memory usage.

[Examigan]

It's just a theory but it wouldn't surprise me if the Visualizer and it's graphics presets are the cause of at least some of the memory usage.

I think you're on to something there, but when I click Disable Visualizer, it seemed like it was almost the same memory usage. I guess if they are pre-loaded that would make sense, as maybe it just means it's turning off the animation part of it. (?) I wish it would also dump them from memory when you click that button.

[Examigan]

All Arturia plugins take forever (like 20-30 seconds or so) to load the GUI the first time on my PC (Windows 10, Cubase 15).

So I wonder why it takes a long time for some users but not all users? There must be a reason, system hardware configuration or whatever the cause. Everyone is using the same plugin.

It took my first instance about 6 or 7 seconds to load.

Windows 11 and using Sonar (latest free version).

[chk071]

To be honest I never go to the Play tab and I absolutely hate the concept of a "visualizer" in an audio plugin. It's an utter waste of CPU/GPU cycles and quite possibly memory as well. It's a synth, not a video game.

I dislike that on Massive X as well. Silly stuff.

[exmatproton]

To be honest I never go to the Play tab and I absolutely hate the concept of a "visualizer" in an audio plugin. It's an utter waste of CPU/GPU cycles and quite possibly memory as well. It's a synth, not a video game.

I dislike that on Massive X as well. Silly stuff.

Yeah..though MX takes it a step further. Over here that thing takes between 15 and 20 seconds load completely. Insane for a wt synth. Pigments is taking long as well, but around half of MX's loading time (initial loading times ofcourse. The second instance loads within 1 second, both P and MX)

[chk071]

Yeah, MX also takes some time to load the GUI. Not 10 to 15 seconds here though.

Maybe it depends on the GPU?

[Teksonik]

It's just a theory but it wouldn't surprise me if the Visualizer and it's graphics presets are the cause of at least some of the memory usage.

I think you're on to something there, but when I click Disable Visualizer, it seemed like it was almost the same memory usage. I guess if they are pre-loaded that would make sense, as maybe it just means it's turning off the animation part of it. (?) I wish it would also dump them from memory when you click that button.

I think disabling the Visualizer just cuts CPU/GPU demand. I don't think it unloads the graphics assets or at least the memory usage doesn't go down here either. There's no "empty" visualizer background I can find.

I don't know what's going on but Pigments uses a lot more memory even with a totally empty patch than any of the other synths I've tested and those synth are as complex in both sound and range of sounds or even more so than Pigments.

I don't ever get close to running out of RAM but 3 instances of Pigments adds up to about 6 gigs so it seems to have costs that don't really add any appreciable benefits in operation.

[Teksonik]

To be honest I never go to the Play tab and I absolutely hate the concept of a "visualizer" in an audio plugin. It's an utter waste of CPU/GPU cycles and quite possibly memory as well. It's a synth, not a video game.

I dislike that on Massive X as well. Silly stuff.

Yeah..though MX takes it a step further. Over here that thing takes between 15 and 20 seconds load completely. Insane for a wt synth. Pigments is taking long as well, but around half of MX's loading time (initial loading times ofcourse. The second instance loads within 1 second, both P and MX)

Some synths scan their databases on first startup (wavetables, samples, presets) and that's why they load much faster on second load.

Maybe it depends on how much content a user has? How many preset packs, sample sets, etc? Maybe it is GPU related.

[HcDoom]

Ok, whos gonna report this to the support?

[bjm4tt]

Got this today from support: "Unfortunately this issue is not fixed yet, but it's logged on our side for further investigation. Our responsible teams are working on it."

In Arturia terms this usually means that nobody cares and nobody is aware of anything and nobody is working on it.

[Maccaroni]

I love how people still pay for that.

[IvyBirds]

Mine loads in 4-5 seconds on multiple PCs

On one of my PCs I literally have every single plugin Arturia makes installed. All of them from the V Collection, Effects collection and Pigments. On another I only have a few, that doesn't seem to make any difference