Minilab Mkii Not Responding Correctly in Pigments within Studio One

Software Instruments Pigments
#1

Hi all,

I’ve been using Pigments more and more as of late and am seeking to use it in pieces and songs I create. However, I’ve run into a couple of snags along the way. It seems when I open Pigments within my DAW, it doesn’t respond correctly to my Minilab Mkii.

Pigments does not respond to any knobs that I turn and also the mod strip. Resetting the Minilab doesn’t seem to work, the settings in Pigments all seem okay (it’s set to receive MIDI on all channels, which seemed to work for some people). In Studio One, the settings are all correct also.

Clicking on MIDI learn in Pigments when open in Studio One also doesn’t seem to help, since Pigments doesn’t even register any of my knobs turning. The only work around I managed to find was to link different parameters with my knobs manually in Studio One (it’s a Studio One feature). However, this seems to be a stop gap measure I find I need to remap the knobs to the different parameters every time I change a preset in Pigments.

What is particularly strange is that when I try to open Pigments in standalone mode, everything seems to work fine. MIDI learn works swell and I’ve even saved a preset of my personal MIDI mapping for convenience. The knobs and mod strip works fully too.

This strange behaviour doesn’t happen with any other non-Arturia VST within Studio One, only Pigments. I’m on a PC by the way.

Would anyone be able point in the the right direction or let me know what might be going on here?

Thanks in advance everyone. It’s much appreciated!

#2

Hi @Betterman. Welcome to the community.

I have Studio One 6 and Pigments 6.
I don’t have a MiniLab.

This make no sense to me.

If you have’nt filtered out midi messages in the MiniLab setup in Studio One, then it should work. And the messages can’t be filtered out, if everything works with other third party instruments.

Also Studio Ones Control Link system can work in different ways like use Local and Global mapping. But it’s not preset based.

I think i need more precise informations to perhaps be able to help.

Are you using your own MiniLab and Pigments midi CC mapping that work in standalone mode?
Which Studio One do you use?
Can you post the External Device setup for you MiniLab in Studio One?
Have you mapped any MiniLab Controls for Studio Ones Control Link System? By that i mean mapped the controls from the controller it self to the Control Link system - and not to plugins. Such Mapped controls can only be mapped to plugins using the Control Link system. That is if nothing has changed in Studio One 7 and you use that. I believe it work like my Studio One 6.

But again - if “normal” midi CC learning work in other plugins, then it should work in Pigments Midi Configs too.

#3

Hi LBH, thanks for your response. Believe me, I was thinking the exact same thing.

Well I have good news, when I opened up Studio One 6 Pro today and opened up a plugin version of Pigments inside it… suddenly everything is responding normally again. Go figure? The mod wheel responds correctly and all the knobs stay assigned despite changing presets.

I have no idea what the heck happened yesterday but I no doubt am happy things are finally working again.

Thanks again and I really appreciate the response LBH.

#4

Hi again @Betterman ,

Sometimes strange things happens.
Glad it work now.

#5

Thanks again LBH! Have a great week!

#6

Hey! I’ve run into something pretty similar before with my Minilab Mk3 — in my case, it happened while using Ableton Live. What worked for me was deleting the device entirely from the MIDI settings, then reconnecting it and letting the DAW re-detect it from scratch.

Not sure if Studio One handles devices the same way, but it might be worth a shot! Sometimes the mapping just gets “stuck” and needs a clean reset.

Hope that helps a bit!