Feature Request: OSC trigger column by ID
Posted: Tue Nov 25, 2025 04:41
In the REST API we have the ability to trigger column by column index or column ID. Example:
/api/v1/composition/columns/1
/api/v1/composition/columns/by-id/1762404410103
Will trigger the same column in my current Resolume show.
However, if I insert a column before column 1, referencing
/api/v1/composition/columns/1
will reference the newly inserted column whereas referencing
/api/v1/composition/columns/by-id/1762404410103
will always reference that specific column regardless of where it goes.
Both these behaviors are desirable but for OSC we only have access to the column reference.
Considering both the REST API and OSC have the same URI format, it doesn't seem that far fetched to implement the "by-id" method of referencing for OSC as well.
It doesn't need to be fancy, keeping the implementation exactly the same but adding
composition/columns/by-id/#ID_HERE
Would be fine, we already have ways of finding specific IDs and it can just be an "advanced user" thing.
/api/v1/composition/columns/1
/api/v1/composition/columns/by-id/1762404410103
Will trigger the same column in my current Resolume show.
However, if I insert a column before column 1, referencing
/api/v1/composition/columns/1
will reference the newly inserted column whereas referencing
/api/v1/composition/columns/by-id/1762404410103
will always reference that specific column regardless of where it goes.
Both these behaviors are desirable but for OSC we only have access to the column reference.
Considering both the REST API and OSC have the same URI format, it doesn't seem that far fetched to implement the "by-id" method of referencing for OSC as well.
It doesn't need to be fancy, keeping the implementation exactly the same but adding
composition/columns/by-id/#ID_HERE
Would be fine, we already have ways of finding specific IDs and it can just be an "advanced user" thing.