full composition websocket messages generated on clip changes
Posted: Sat Sep 27, 2025 08:26
Hello,
When creating a websocket connection to Resolume and a new clip is triggered, a full composition state message is delivered to the client. According to https://resolume.com/support/en/websocket-api, the full composition state should only be delivered upon initial connection or 'when there are structural changes'.
In a composition with many layers with frequently changing clips, the volume of these messages can slow down the websocket client (i.e. TouchDesigner) as the json payload size can be significant and occur multiple times per second.
Is this a bug, or if by design is there a way to disable/throttle it?
Please let me know if you would like any additional info.
Thanks
Joe
When creating a websocket connection to Resolume and a new clip is triggered, a full composition state message is delivered to the client. According to https://resolume.com/support/en/websocket-api, the full composition state should only be delivered upon initial connection or 'when there are structural changes'.
In a composition with many layers with frequently changing clips, the volume of these messages can slow down the websocket client (i.e. TouchDesigner) as the json payload size can be significant and occur multiple times per second.
Is this a bug, or if by design is there a way to disable/throttle it?
Please let me know if you would like any additional info.
Thanks
Joe