Problem with Pigments to FL Studio

Software Instruments Pigments
#1

Hello,

I’m encountering a persistent issue with Pigments inside an FL Studio project, and I’d like to provide as much technical detail as possible.

I recently built a new PC, transferred my FL Studio project files, and reinstalled all my plugins. Everything works correctly except for one specific project where Pigments fails to initialize its GUI.

Issue description

When I open the project in FL Studio 25 (latest version), Pigments loads and produces sound, but its interface cannot be opened. FL Studio displays an error message (see screenshot), and the Pigments window never appears. The instance remains active in the mixer and plays back normally, but the UI is completely inaccessible.

If I load a new instance of Pigments in the same project, it works as expected. Only the original instance saved in the project is affected.

What I have already tried

  • Restarting FL Studio and Pigments
  • Full system reboot
  • Verifying Pigments installation (Arturia Software Center shows latest version)
  • Loading other projects containing Pigments (they work normally)
  • Adding a fresh Pigments instance to the problematic project (works normally)

Additional notes

  • The issue only affects the Pigments instance stored in this specific project file.
  • The plugin is active and renders audio, but the GUI fails to initialize.
  • No other plugins in the project exhibit this behavior.
  • The crash log from FL Studio reports a division by zero originating from Pigments.vst3.

Screenshot description

Left: Pigments instance from the original project (GUI cannot be opened) Right: Newly added Pigments instance (GUI works normally)

Question

Is there any way to recover the original Pigments instance and its parameters, so I don’t lose the sound design work stored in the project? I would like to avoid rebuilding the patch from scratch if possible.

Thank you in advance for your help.

Note (1) : Version Pigments : 7.0.0.6447
update to Arturia Software Center

Note :

Log Error to FL Studio :

FL Studio (25.2.4.5242) [64Bit] r55571 has encountered an error and needs to restart.

Crash log saved to C:\Users\narut\Documents\Image-Line\FL Studio\Support\Logs\Crash\ folder.

Please use Ctrl+C to copy this message and report to support.

OS Version:
Windows 11 (Version 25H2, OS Build 26200.7840, 64-bit Edition)

Exception:
Division by zero

Callstack:
00007FFAC1150000:00007FFAC1D39CC8: Pigments.vst3
00007FFAC1150000:00007FFAC1D3A0E8: Pigments.vst3
00007FFAC1150000:00007FFAC1D342CB: Pigments.vst3
00007FFAC1150000:00007FFAC1D32692: Pigments.vst3
00007FFAC1150000:00007FFAC1D42FB2: Pigments.vst3
00007FFAC1150000:00007FFAC1D420A1: Pigments.vst3
00007FFAC1150000:00007FFAC1D3530D: Pigments.vst3
00007FFAC1150000:00007FFAC1D2ECD9: Pigments.vst3
00007FFAC1150000:00007FFAC192F06E: Pigments.vst3
00007FFAC1150000:00007FFAC192E6B3: Pigments.vst3
00007FFAC1150000:00007FFAC193D725: Pigments.vst3
00007FFAC1150000:00007FFAC193BE30: Pigments.vst3
00007FFAC1150000:00007FFAC192E5C0: Pigments.vst3
00007FFAC1150000:00007FFAC192F051: Pigments.vst3
00007FFAC1150000:00007FFAC192E6B3: Pigments.vst3
00007FFAC1150000:00007FFAC193D725: Pigments.vst3
00007FFAC1150000:00007FFAC193DC83: Pigments.vst3
00007FFAC1150000:00007FFAC193CAB3: Pigments.vst3
00007FFAC1150000:00007FFAC193BE30: Pigments.vst3
00007FFAC1150000:00007FFAC192E5C0: Pigments.vst3
00007FFAC1150000:00007FFAC192E06B: Pigments.vst3
00007FFAC1150000:00007FFAC192A2D2: Pigments.vst3
00007FFAC1150000:00007FFAC192DDE1: Pigments.vst3
00007FFAC1150000:00007FFAC192EEE4: Pigments.vst3
00007FFAC1150000:00007FFAC192E6B3: Pigments.vst3
00007FFAC1150000:00007FFAC193D725: Pigments.vst3
00007FFAC1150000:00007FFAC193BE30: Pigments.vst3
00007FFAC1150000:00007FFAC192E5C0: Pigments.vst3
00007FFAC1150000:00007FFAC192463C: Pigments.vst3
00007FFAC1150000:00007FFAC1923910: Pigments.vst3
00007FFAC1150000:00007FFAC183A2CD: Pigments.vst3
00007FFAC1150000:00007FFAC17A652D: Pigments.vst3
00007FFAC1150000:00007FFAC17A6E81: Pigments.vst3
00007FFAC1150000:00007FFAC16B3B89: Pigments.vst3
000000005D4D0000:000000005D6574C7: QuickFontCache_x64.dll
000000005D4D0000:000000005D65A18C: QuickFontCache_x64.dll
000000005CB60000:000000005CFAFBF1: Fruity Wrapper_x64.dll
000000005CB60000:000000005CFAFEE6: Fruity Wrapper_x64.dll
000000005CB60000:000000005CEEE19B: Fruity Wrapper_x64.dll
000000005CB60000:000000005CEF0405: Fruity Wrapper_x64.dll
000000005CB60000:000000005CFCB7E1: Fruity Wrapper_x64.dll
000000005D6E0000:000000005E171BCF: FLEngine_x64.dll
000000005D6E0000:000000005E171D09: FLEngine_x64.dll
000000005D6E0000:000000005DA24283: FLEngine_x64.dll
000000005D6E0000:000000005DA24443: FLEngine_x64.dll
000000005D6E0000:000000005D8B3422: FLEngine_x64.dll
000000005D6E0000:000000005D9FCBA9: FLEngine_x64.dll
000000005D6E0000:000000005D9FC1A4: FLEngine_x64.dll
000000005D6E0000:000000005D8B35AD: FLEngine_x64.dll
000000005D6E0000:000000005D8B3625: FLEngine_x64.dll
000000005D6E0000:000000005D6F00D4: FLEngine_x64.dll
000000005D6E0000:000000005D8B2D3A: FLEngine_x64.dll
000000005D6E0000:000000005D8B2855: FLEngine_x64.dll
000000005D6E0000:000000005D8B92A1: FLEngine_x64.dll
000000005D6E0000:000000005D8B993F: FLEngine_x64.dll
000000005D6E0000:000000005D8B8F6C: FLEngine_x64.dll
000000005D6E0000:000000005D808626: FLEngine_x64.dll
00007FFB896B0000:00007FFB896C6B46: USER32.dll
00007FFB896B0000:00007FFB896C459D: USER32.dll
000000005D6E0000:000000005DB21C56: FLEngine_x64.dll
000000005D6E0000:000000005DB21CC8: FLEngine_x64.dll
000000005D6E0000:000000005DB2219A: FLEngine_x64.dll
000000005D6E0000:000000005E545BCF: FLEngine_x64.dll
000000005D6E0000:000000005E5467E9: FLEngine_x64.dll
00007FF62F730000:00007FF62F8100DC: FL64.exe
0000000000000000:00000000000000C0: 

Modules:
Pigments.vst3: C:\Program Files\Common Files\VST3\Pigments.vst3
QuickFontCache_x64.dll: S:\FL Studio 21\Shared\QuickFontCache_x64.dll
Fruity Wrapper_x64.dll: S:\FL Studio 21\Plugins\Fruity\Generators\Fruity Wrapper\Fruity Wrapper_x64.dll
FLEngine_x64.dll: S:\FL Studio 21\FLEngine_x64.dll
USER32.dll: C:\WINDOWS\System32\USER32.dll
FL64.exe: S:\FL Studio 21\FL64.exe


Undo:
Ajustement de potentiomètre (amp inverted)
Ajustement de potentiomètre (finisher)
Ajustement de potentiomètre (finisher mode)
Ajustement de potentiomètre (finisher on/off)
Ajustement de potentiomètre (stomp box)
Ajustement de potentiomètre (stomp box mode)
Ajustement de potentiomètre (stomp box on/off)
Ajustement de potentiomètre (pickup)
Ajustement de potentiomètre (drive)
Ajustement de potentiomètre (amp)
#2

Hi,

It sounds very much like a corrupt project as additional Pigments instances and all other plugins work ok.

In Logic, I can select a track and create a copy of it with the same plugin and patch. Can you do this in FLS?

Have you tried saving a copy or version of the project?

Have you tried deleting the plugin and then using UNDO?

I know its a long shot but can you try adjusting the screen resolution and make sure you video driver is up to date in case this is some weird graphics problem.

Its all a process of elimination and obviously contacting FLS or a forum to see if they have suggestions would be advisable.

#3

Thanks for the suggestions.

Cloning the track was a good idea, but unfortunately it results in the exact same error, the original Pigments instance still refuses to open its GUI.

Regarding the project itself, it was created a bit more than a year ago and hadn’t been opened since then. It’s possible that something in the stored state of that specific instance is no longer loading correctly, even though Pigments is fully up to date on my system.

I also tried the steps you mentioned, including deleting the plugin instance and using UNDO, but the issue persists.

As for screen resolution, that shouldn’t be the cause. I’ve always used the same WQHD setup, and all peripherals remain unchanged. The only major difference is the hardware: I moved from an Intel/Nvidia configuration to a full AMD system.

Thanks again for taking the time to look into my issue.

#4

Do you still have access to the old system and if so, can you try it there.

Its been a long time since I used a Windows setup but I remember having weird problems at time that were video driver related. For the sake of elimination, I would try it.

#5

You can’t see the GUI. But is it possible that you in a state where the plugin should be open and active can be clicked on and then save the preset using CTRL+S? I suggest you try. Check if the preset have been saved. Open a new instance on a new track and also copy the midi informations too the track.

Otherwise i agree it look like a project issue.

FYI: Please keep in mind, that posting in the community is’nt the same as contacting Arturia support.

#6

@Funtmaster Thanks for taking the time to reply. Unfortunately, I no longer have access to the old system. I assumed that backing up my entire FL Studio folder would be enough to preserve everything, but apparently that wasn’t the case. Luckily, only one plugin out of the twenty used in the project is affected, so it could have been much worse. There’s a chance I wrote down the sound design settings in a notebook, but I can’t seem to find it anymore.

@LBH When I press CTRL+S on the problematic instance, it simply saves the FL Studio project itself — nothing else happens, and no preset file is created. Before posting here, I contacted Image-Line technical support to understand the issue. They advised me to reach out to Arturia, as they didn’t have a solution to offer beyond updating Pigments (which I already did). I’m aware this isn’t the official Arturia support channel; I just wanted to check whether anyone had encountered this issue before I escalate it to the support team. Thanks for the reminder.

#7

In that case Pigments is’nt in focus.

#8

Did you try using Pigments VST2, rather than VST3?
You could do a direct replacement in the FL project.

That said, it does rather sound like a corrupt file. Did you check your storage and RAM for errors?