Camelot 2.5

Camelot 2.5 is not just another update.
It’s a structural shift in how you control your live setup.
For a long time, Camelot made a deliberate trade-off: simplicity over flexibility.
Global positional mapping ensured stability, predictability, and fast setup — especially critical in live performance contexts.
But that approach had a cost.
If you needed deeper control, more nuanced mappings, or scene-specific behavior, you had to work around the system. And the more complex your setup became, the more fragile and harder to manage it was.
Camelot 2.5 removes that limitation — without sacrificing clarity.

This release focuses entirely on Remote Control — how MIDI controllers interact with Camelot, and how you shape that interaction.
The goal is simple:
Give you full control, without forcing you into chaos.
And that’s exactly what 2.5 delivers.
Global Mapping in previous versions was rigid by design:
you mapped positions, not objects.
It worked — but it didn’t scale.
With Camelot 2.5, Global Mapping becomes:
Pickup Mode (finally)
No more parameter jumps. Your hardware only takes control when it matches the current value.
Result: smooth transitions, zero surprises.
Jump Mode (still there)
For when you need immediate response.
Massive Expansion of Mapping Scope
Up to 16 layers per Scene, Song, and Setlist
Up to 8 Items per mapping system
This isn’t incremental — it’s a scale upgrade.
Flexible MIDI Assignment
Not just fixed CC/Program Change anymore
Support for Notes, custom CCs, and alternative mapping strategies
Bidirectional Communication
Your controller is no longer blind.
Camelot sends feedback back to your hardware:
Motorized faders move correctly
LEDs reflect real values
This alone eliminates one of the biggest friction points in live control.


This is the real breakthrough.
For the first time, Camelot introduces Local Mapping — and it changes everything.
Local Mapping lets you define scene-specific control behavior.
Not globally.
Not abstractly.
Exactly where it matters.
You can now:
Local Mapping includes:
This is not a “light” feature.
It’s a full control system — scoped exactly where you need it.


Without this level of control, you are forced into one of two bad options:
Neither scales. Neither survives real live performance pressure.
Camelot 2.5 eliminates that trade-off.
You now have:
Global consistency where needed
Local precision where it counts
If you’re still working with rigid mappings or external workarounds, you’re effectively limiting your own setup — and introducing unnecessary risk on stage.
Here’s the critical point:
This isn’t “more features.”
It’s better control architecture.
Everything in Camelot 2.5 has been designed to stay:
No feature exists in isolation.
Everything is built around live performance reality.
Camelot 2.5 finally delivers what advanced users have been asking for —
but in a way that doesn’t break the system.
This is not an incremental update.
It’s the moment Camelot becomes a fully mature control environment.
If your setup matters, this update is not optional.
Camelot 2.5 gives you control you didn’t have before —
and removes limitations you were probably compensating for without realizing it.
Update now and take full control of your performance.