Hi Anome team,

I maintain millumin-mcp, an open-source server that lets AI assistants such as Claude control Millumin through the OSC API. It handles launching columns, setting layer properties and reading feedback well. The gap we keep hitting is transitions.

As explained in this forum thread, /action/launchColumn uses the timings in the column's settings, and no message launches a column with a different transition time. Right now transitions can only be changed in the interface. We could fade opacity from outside, but that would bypass Millumin's transition engine: no stingers, no ISF transitions, and no property animation between columns.

In order of priority, these would help most:

Per-launch override. An optional duration argument when launching, such as /action/launchColumn [index or "name", seconds], with the same option on launchNextColumn, launchPreviousColumn and launchOrStopColumn.
Column transition settings. Read and write a column's transition type and duration, such as /column:3/transition/duration [2.5] and /column:3/transition/type ["Crossfade"], with /? queries for reading them back.
Live transition control. Skip the current transition, pause and resume it, and drive the master column transition slider, such as /action/skipTransition and /masterColumnTransition [0..1].
Feedback. A message when a transition starts and ends, with its duration, such as /millumin/board/transitionStarted [index, "name", seconds].
It would also help to have the same functions in the JavaScript API, such as Millumin.setColumnTransition(indexOrName, type, duration), and to list them in the OSCQuery tree on port 5678. We plan to use that tree to discover addresses.

The address names are only suggestions; whatever fits your conventions is fine. I'm on 5.14 and happy to test a beta build.

Thank you for Millumin!

JP Kelly