URI Cue Item
Grace Chapel Admin
Member Posts: 21 ✭✭✭
Would like to be able to call a URI from a Cue in Proclaim.
Example 1:
Trigger a Stream Deck Companion button via a Cue by calling http://[IPofCompanion]:8000/press/bank/1/1 to press the first button on the first page. This enables automatic recall of scenes, etc. using command strings already programmed into Companion.
Example 2:
Trigger vMix to start recording by calling a vMix API URI:
http://[IPofvMix]:8088/api/StartRecording
Example 1:
Trigger a Stream Deck Companion button via a Cue by calling http://[IPofCompanion]:8000/press/bank/1/1 to press the first button on the first page. This enables automatic recall of scenes, etc. using command strings already programmed into Companion.
Example 2:
Trigger vMix to start recording by calling a vMix API URI:
http://[IPofvMix]:8088/api/StartRecording
Tagged:
11
Comments
-
This would be a handy feature. It would remove the complexity of routing through MIDI software and running scripts that do the HTTP request.
One potential issue that I see would be synchronizing these items with others. If the URL is publicly accessible (API calls, etc.) then they might get triggered unintentionally. Private addresses (LAN) could also be problematic if users are on the same network or using a VPN.
To make this work reliably there would have to be some sort of control over which Proclaim account or device is able to execute the calls so that they only work when they are supposed to, and where they are supposed to.
In the case of API calls there may also need to be additional security in place so as not to expose credentials to everyone on the presentation team.0 -
This would be a handy feature. It would remove the complexity of routing through MIDI software and running scripts that do the HTTP request.
One potential issue that I see would be synchronizing these items with others. If the URL is publicly accessible (API calls, etc.) then they might get triggered unintentionally. Private addresses (LAN) could also be problematic if users are on the same network or using a VPN.
To make this work reliably there would have to be some sort of control over which Proclaim account or device is able to execute the calls so that they only work when they are supposed to, and where they are supposed to.
In the case of API calls there may also need to be additional security in place so as not to expose credentials to everyone on the presentation team.0 -
Sorry for the double comment. The button didn't seem to respond!0
-
@mikethiessen21-68 As far as I am aware, these URI calls are public (anyone on the network can trigger them) and can be executed just about anywhere (browser, Run dialog, etc.). They technically can be triggered via Proclaim's Web Page item, but they display the results on the screen - would be nice to have a separate item (similar to Cues) that aren't triggered on-screen.
As far as timing/conflicts with other users, that's up to the user to control that, and not anything Proclaim should have to worry about in their implementation (as no other implementation I've seen in other software accounts for this, either).0 -
Update: Companion now requires API commands be sent as POST messages, so this request should include support for POST commands.0
