Subject:
Hi Eos,
I'm currently building a custom controller. The goal is not to replace the console, but to create a dedicated hardware extension with an 8×8 pad matrix, endless encoders and LED feedback that feels like a natural part of the Eos workflow.
While working on the project, I realized that Custom Direct Selects are almost exactly what I need. They already provide a perfect interface for organizing Groups, Palettes, Presets, Macros and other objects in a user-defined grid.
The only thing missing is a way to synchronize them with an external controller.
At the moment, I haven't found any method to retrieve the contents of a Custom Direct Select or detect when it has been modified. OSC Direct Select banks are useful, but they are separate virtual objects and do not reflect the Custom Direct Selects created on the console.
For a controller with LED feedback, this makes true synchronization impossible. Ideally, the hardware would always mirror exactly what the operator sees on the Eos screen. If a Custom Direct Select is edited, renamed, reordered or an item is added or removed, the controller would update automatically.
Would it be possible to expose Custom Direct Selects through the OSC API?
Even a read-only interface would make a huge difference.
For each cell, it would be extremely useful to receive:
- Cell index (1…n)
- Whether the cell is empty or occupied
- Object type (Group, Preset, Color Palette, Macro, etc.)
- Assigned object number or UID
- Displayed label
If the visual position of cells can be customized, returning their row/column or X/Y coordinates would also be extremely valuable. If the layout is always a fixed grid, simply returning the cell index would already allow external hardware to mirror the layout exactly.
It would also be incredibly helpful to receive a notification whenever a Custom Direct Select changes, allowing external devices to stay synchronized without polling.
I believe this would open the door to a new generation of third-party controllers, Stream Deck profiles, Companion modules and custom touch interfaces, all while keeping Custom Direct Selects as the central editing interface inside Eos.
Thank you very much for taking the time to read this. Whether or not this is something you're considering, I'd really appreciate hearing your thoughts.
Best regards
