Nikolozi Mela 7.0: undo/redo + deeper control for modular AUv3 on iOS and macOS

Nikolozi has released Mela v7.0 for iOS and macOS, continuing its long-term arc toward a modular “build-your-own instrument/effect/MIDI processor” environment that runs both standalone and as an AUv3 plug-in. The standout change in 7.0 is the addition of Undo and Redo, which sounds mundane until you’ve built a complex modular preset: once you’re experimenting quickly (swapping modules, changing routing, editing lanes), the ability to roll back a bad decision is the difference between fearless iteration and cautious fiddling.

The 7.0 update also generalizes Perform View into remote views, shifting the UI philosophy from “a small performance panel” toward “multiple controllable, mappable views” you can use for live performance or streamlined DAW work. In practice, it’s a step toward treating Mela patches like playable instruments with curated controls—without forcing you to keep the full patch editor open.

Mela in one sentence

Mela is an Audio Unit environment where you arrange modules on lanes and route Audio/MIDI/Pitch signals between them to build polyphonic synths, audio effects, and MIDI processors—then reuse those presets across hosts on iPhone, iPad, and Mac.

What “modular” means in Mela (the useful version)

Mela’s modular model is intentionally pragmatic. Instead of a blank patch-cable canvas, you build by stacking modules in lanes where signals flow top-to-bottom. That structure makes patches easier to understand later—and it maps well to how producers actually work: a chain for a voice, a chain for an effect, and routing between them when needed.

Three signal types are central: Audio, MIDI, and Pitch. Pitch is treated as a first-class signal (a frequency stream) so oscillators can lock to it and pitch processors can transform it. This lets you build instruments that feel “synth-like” without hiding polyphony behind opaque UI layers.

Why undo/redo is a real feature in modular workflows

In modular tools, progress often looks like a series of micro-experiments: “what if this LFO targets the filter instead of amplitude,” “what if I split the lane into parallel layers,” “what if the arpeggiator runs before the chord module,” and so on. Without undo/redo, exploration slows down because every change is risky—especially when the patch is already working and you don’t want to lose your baseline. Undo/redo restores the creative loop: try something, listen, keep or revert—repeat.

Remote views: turning complex patches into playable instruments

As patches get more sophisticated, the “editor UI” becomes the wrong interface for performance. Remote views solve that by letting you expose only the controls that matter: macro parameters, a handful of modulation depths, mix controls, or a performance panel for live tweaking. That’s not just UX polish—it’s how you make a modular patch usable in a session when you’re writing at speed.

Why Mela is interesting on iOS and macOS

Mela matters because it’s one environment across platforms. If you sketch ideas in an iPad host (like AUM/Drambo-style workflows) and then finish in a macOS DAW, portability becomes a force multiplier: the sound design work carries forward. That’s also where remote views help—when a patch moves between devices and hosts, you want the “performance surface” to remain consistent even if the editor layout changes.

What to test if you’re evaluating Mela

• Signal flow clarity: can you understand routing at a glance when a patch is layered?
• Polyphony behavior: do modulators and voice behavior match your expectations when playing chords?
• Host integration: does your main AUv3 host expose parameters in a predictable way?
• Preset portability: can you move patches between iOS and macOS without friction?

Mela’s module library and preset ecosystem matters too: the real value of a modular environment is not just “can I build it,” but “can I build it quickly, repeatedly, and recall it reliably.” As a buying/evaluation heuristic, look for modules that replace entire “multi-plugin” patterns: sequencing (arp + euclid + echo), synthesis building blocks (VA + FM operators), and utility modules that keep patches tidy (mixing, meters, buses).

Finally, test the boring things: does the UI stay responsive when a patch grows? Can you duplicate lanes and keep modulation mappings sane? These are the details that decide whether a modular tool becomes your daily driver or a weekend experiment.

Video

This official Nikolozi “What’s new in Mela” video is a good entry point into the modular philosophy and module evolution across updates.

Discover more

Official product page: https://nikolozi.com/mela/