DAW API documentation

l_o

I'd like to use the Reliq as a controller for lighting art installations and shows. For that, I want to hook it up with my TouchDesigner patch to set the appearance of the pads, render content on the display, and of course, react to input on the pads and the controllers. What the Reliq makes so interesting for this use case is the huge amount of pads to trigger things compared to controllers like the APC 40 or Launchpad as well as the big display, But I'd also LOVE to use the actual MIDI capabilities to program and modify sequences and modulations in real time while still being able to access the custom control surface.

However, I couldn't find any documentation of the protocol. Am I overlooking something or is it proprietary?

A quick look at the decompiled pyc files of the Ableton Live CS also indicates that there's no low level graphic rendering engine accessible to draw pixels, shapes or text. Instead it looks like the Reliq generates the content itself and only takes parameters for manipulating certain aspects. Is my observation correct?

Kyriakos-Reliq

Hey @l_o ,
Thanks for sharing this, using Reliq in lighting / installation contexts is super inspiring. As you mentioned, the current Ableton Live and Bitwig scripts expose only the parts of the control-surface API we intentionally built for DAW integration. There isn’t a public low-level graphics protocol for drawing pixels, shapes, or custom UI layouts on Reliq, and at the moment there’s no way to program your own GUI or fully repurpose the grid/buttons/encoders beyond the existing pages.

That said, a User Mode is already on the backlog, the idea is to allow full custom mapping of pads, encoders, and some display elements, both for internal functions and external devices. It’ll take some time to get right, but it is planned.

On the TouchDesigner front: we can’t share much detail yet, but there are definitely some ideas brewing on our side as well 😉 It’s a super interesting use case, and your feedback helps a lot.