LeCoqRoti
The 7.0.1 update brings a trio of new filters — Rage, Ripple, and Reverb — alongside the Corroder effect, 150 factory presets, and fresh wavetable, sample, and noise content. These additions slide naturally into a working session.
A session path: four typical stations
- Sketching on an instrument track. Load Pigments onto a software instrument track. The redesigned Play Page offers macro controls and a curated view of the six underlying engines: a quick place to twist a sound before committing to deeper editing.
- Building the patch. Move to the full interface when the idea needs a custom timbre. Combining engines — wavetable with granular, say — yields movement that a single architecture cannot. The new Rage and Ripple filters add aggressive and liquid textures early in the chain.
- Processing on a bus. Send audio to a bus with Pigments inserted as an effect. The built-in effects section, now including the Corroder for degraded, lo-fi colour, can treat external signals with the same modulation depth as the internal oscillators.
- Polishing the arrangement. Automate parameters across the timeline. A slow shift on the Reverb filter’s cutoff or a Corroder mix ramp can glue a transition without touching a separate effects rack.
Integration: how Pigments speaks to the rest of the studio
Pigments does not sit in isolation. Its modulation system responds to MIDI CC messages directly: right-click any parameter, choose a controller number, and an external knob or fader takes over. This matters when a project already leans on hardware — a MIDI controller mapped to the Ripple filter cutoff can perform a sweep that feels more organic than drawing automation.
On the macOS side, the plugin reports its parameters to the host in a structured, predictable way. Logic Pro’s Smart Controls and Ableton Live’s Configure mode both see every exposed destination, which means a Push or Launchpad inherits the same mapping without duplicate work. Audio Unit and VST3 formats are supported; the AU version plays well with Logic’s multi-output routing if you want to split the three main buses — engine one, engine two, and the effects return — onto separate mixer channels for independent processing.
Sidechain input is available in the effects section. A compressor or the Corroder can listen to a kick drum from another track, letting the synth patch breathe in time with the rhythm without an external sidechain plugin. This is a small detail that newcomers overlook, but it turns Pigments from a sound generator into a reactive element in a mix.
Beginner mistakes: three habits that slow you down
The colour-coded interface is clear, but clarity does not prevent certain missteps that appear again and again during the first weeks with the synth.
Over-modulating before listening. It is tempting to wire every LFO and function to a dozen destinations immediately. The result is often a patch where no single movement is audible because everything cancels into a blur. A better discipline: assign one modulator, dial its depth while the sequence plays, then add the next. The modulation matrix grows with intention rather than chaos.
Ignoring the effects as sound-design tools. Many treat the built-in effects as an afterthought — a bit of reverb at the end of the chain. Pigments allows effects to be placed in the insert path before the filter section, or modulated by the same sources driving the oscillators. The Corroder, for instance, can be set to degrade only the attack portion of a note via an envelope, leaving the sustain clean. That kind of movement is difficult to replicate with external plugins.
Staying on the Play Page too long. The redesigned Play Page is excellent for performance and quick tweaks, but it shows only a curated subset of parameters. A beginner who never ventures to the full editor misses the dual filter routing, the per-engine unison controls, and the tuning tables hidden in the wavetable engine. The Play Page is a launchpad, not a replacement.
From init patch to first custom sound in three sessions
After installation, resist the urge to scroll through all 150 new presets in one sitting. Instead, try this order over two or three sessions:
- Load an init patch and build one sound from scratch. Choose a single engine — wavetable is a good starting point — and shape an amplitude envelope, a filter, and one modulation routing. Save it. This teaches the signal flow faster than deconstructing complex presets.
- Audition the new filters in isolation. Take the simple patch and swap between Rage, Ripple, and Reverb filters. Drive the Rage filter hard with resonance to hear how it saturates differently from the standard ladder models. The Ripple introduces a phase-shifted character that works well on plucked sounds; the Reverb filter blurs the line between filtering and spatial effect.
- Run through the in-app tutorials. The 7.0.1 release added guided walkthroughs accessible from the top bar. They cover the redesigned Play Page and the new effects sequentially, which saves the time spent hunting for features in the manual.
- Map four macros to a MIDI controller. Assign cutoff, Corroder mix, a wavetable position, and reverb decay to four physical knobs. Play a simple chord progression and twist. Macros are the fastest route to understanding how Pigments responds to performance gestures.
- Explore the new sample and noise content alongside the existing library. The 30 samples and 20 noises added in this version sit inside the granular and sample engines. Combining a new noise — a textured field recording, perhaps — with a classic analog-model waveform yields hybrid textures that neither engine produces alone.
Comparisons: where Pigments sits among its peers
Three synthesizers occupy a similar space on a producer’s hard drive. Each approaches the hybrid concept differently.
Xfer Serum established the visual wavetable workflow that many now expect: drag a waveform into the editor, see it rendered in 3D, and modulate it with an LFO system that feels immediate. Pigments matches this clarity — its wavetable display is equally responsive — but adds the virtual analog, granular, and harmonic engines that Serum leaves to external processing. Serum’s effects rack is solid; Pigments’ is deeper, especially with the Corroder and the new filter types arriving in 7.0.1. The trade-off: Serum’s single-minded focus on wavetable synthesis makes it marginally quicker for that specific task, while Pigments asks the user to decide which engine a sound needs before committing.
Native Instruments Massive X offers a sprawling semi-modular architecture with a darker, more industrial character. Its routing possibilities rival Pigments, and its performer and tracker modules provide a different flavour of modulation sequencing. Where Pigments pulls ahead is interface legibility: Massive X’s dense panels can feel opaque during a first encounter, whereas the colour-coding in Pigments — red for filters, blue for modulation, yellow for envelopes — reduces the time spent searching for a parameter. Both handle CPU-intensive patches with reasonable efficiency on Apple Silicon, but Pigments’ new Play Page gives it an edge for live performance scenarios where screen real estate is limited.
u-he Hive 2 takes the opposite approach: it is deliberately lean, built for low CPU usage and fast patch creation. Hive’s modulation matrix is simpler, its effects are more utilitarian, and its wavetable engine is less graphically detailed. It excels as a workhorse subtractive synth that loads instantly. Pigments cannot match Hive’s frugality with processor cycles — six engines and deep modulation impose a cost — but for sound design sessions where a patch evolves over minutes rather than seconds, the extra headroom Pigments demands is justified by the results.
In short: Pigments moves easily from a self-contained sound source to a modulated effects processor, slotting into every stage of a project.
Correspondence 0
Take a chair or join the table to send a letter.
No correspondence on this note yet. Letters are read before they appear.