Lemur Alternative: Where Lemur Stands, and What Else to Use

What actually happened to Lemur

Lemur has one of the more unusual histories in computer music, and the confusion around it is the reason this search term exists at all. The short version:

• Hardware first. Lemur began as a dedicated multitouch hardware surface before the idea moved to tablets and phones as software.
• September 2022 — removed from the stores. The app disappeared from sale. For anyone who had built a rig around it, that looked like the end, and much of the discussion online froze at this point.
• 2023 — acquired by MIDI Kinetics. The product changed hands rather than dying, and development resumed under a new owner.
• Early 2025 — back on the App Store. Lemur returned to sale and has kept receiving updates since, alongside desktop builds.

So the honest framing is: Lemur is available and maintained again, but it spent roughly two and a half years off the shelf. Users who moved on during that window built new habits, and many are now deciding whether to move back or to pick something simpler.

NueCtrl vs Lemur at a glance

Lemur details are summarised from MIDI Kinetics' own product pages as of July 26, 2026, and are stated in general terms because vendors change specifics. Check midikinetics.com for the current platform list and licensing before you decide.

Two different answers to the same wish

Lemur and NueCtrl both start from "I want my phone or tablet to control my DAW", and then take opposite routes. Lemur says: here is a canvas, a widget library, and a programming language — build the exact surface your work needs. NueCtrl says: here is one thing done deeply — your hand becomes the fader.

That is not a small distinction. A Lemur template is a piece of software you author; it can hold logic, react to state, and drive a whole scoring workflow. A NueCtrl preset is a mapping, not a program. In exchange, NueCtrl asks nothing of you before you make a sound, and its core gesture is something a touch template structurally cannot do: continuous, eyes-free movement of a parameter through a long physical arc while both hands stay in playing position.

If your Lemur usage was one fader you kept reaching for during takes, the canvas was never the point — the movement was. That is the case NueCtrl is built for, and it is covered in more depth in our guide on making MIDI sound human.

Migrating: what carries over and what does not

The most common migration worry is losing years of template work. Be realistic about what moves:

Does not carry over

• Template files. Lemur projects have no import path into NueCtrl. There is no converter, and building one is not on the table — the two apps do not share a document model.
• Scripts and custom logic. Anything conditional in your template has no equivalent.
• OSC destinations. If a template drove OSC targets, NueCtrl cannot reach them at all.

Carries over completely

• Your DAW-side mappings. Every CC number and MIDI channel you assigned inside Logic Pro, Cubase, Ableton Live or your sample libraries stays valid. Both apps send standard MIDI, so a new source pointed at the same CC just works.
• Your muscle memory for the parameters. CC1 and CC11 behave the same regardless of what is sending them.
• Your connection method. If your machine was already set up for Network MIDI or Bluetooth MIDI, that plumbing is unchanged.

A pragmatic migration, then, looks like this:

1. List the controls you actually touched last year. Most people find the honest list is far shorter than their template.
2. Separate set-and-forget from performed. Transport, track selection and keyswitches are set-and-forget. Expression, modulation and filter sweeps are performed.
3. Keep a template for the first group if you still need one. Lemur being back on sale means this is a real option again, not a fallback.
4. Point NueCtrl at the second group. Set the CC number and range per fader in Edit Mode, save a preset, and perform it.
5. Check for collisions. If both are running, give them different MIDI channels so the DAW never sees two sources fighting over one CC.

When Lemur is still the better choice

• You depend on scripting. Conditional logic, custom widget behaviour, and state-aware templates have no NueCtrl equivalent.
• You have a working template library. Especially in film scoring, where templates manage keyswitches, articulations and DAW key commands, rebuilding that is weeks of work.
• You need OSC. NueCtrl sends MIDI only.
• You want a desktop or tablet surface. Lemur runs on macOS and Windows as well as iOS; NueCtrl is an iPhone app.
• You need many controls visible at once. A large multitouch grid is a different ergonomic problem from a single expressive axis.

When NueCtrl is the better choice

• Expression is the job. Riding CC11 and CC1 by hand is what produces dynamics that read as human rather than drawn.
• You do not want to maintain a template. Presets ship ready; there is nothing to keep up to date after an OS update.
• You want stability of setup. Bluetooth advertising starts on launch and there are no drivers to install, so the connection step is short and repeatable.
• You want resolution. Motion sensing runs at up to 500Hz in Max Mode, with roughly a 128° tilt range mapping to the full MIDI value range — a longer effective throw than a 10 cm hardware fader.
• You want to evaluate it for free. The app is free; Pro is a one-time in-app purchase if you later want Max Mode, unlimited faders and unlimited presets.