search

SuperFlyTV / SuperConductor

A playout client for Windows/Linux/macOS that will let you control CasparCG Server, BMD ATEM, OBS Studio, vMix, OSC-compatible devices, HTTP (REST)-compatible devices, and more!
Other
219 stars 12 forks source link

Feature request - OSC control of SuperConductor from external automation program #151

Open Velikyi opened 1 year ago

Velikyi commented 1 year ago

I want to be able to add SuperConductor into a Bitfocus Companion workflow, using SuperConductor as a sort of timeline-based phantom button pusher for Companion, as well as being a (better) bridge to CasparCG

Since we have the ability to control SuperConductor with keybinds and Streamdeck, why not add an option to let it be controlled by OSC, so that other software can use SuperConductor functionality without totally switching automation solutions?

nytamin commented 1 year ago

I like this idea! OSC seems like a perfect fit, since that could both be used trigger things and for analog inputs!

Velikyi commented 1 year ago

Any updates on the possibility of adding this to a close future update?

Velikyi commented 9 months ago

I like this idea! OSC seems like a perfect fit, since that could both be used trigger things and for analog inputs!

Has this been put into motion, either planning or already developed and set for a near future release?

nytamin commented 9 months ago

No movement on this at the moment, no. We're currently focusing our resources in other areas.

Elektordi commented 5 months ago

@Velikyi currently you can do that using the internal API. I have a similar setup.

You have to use the Companion http module. Prefix: http://localhost:5500/api/internal/

Then add actions on buttons: Method: POST Url (for example): playGroup/?rundownId=default.rundown.json&groupId=aa1LYW7C Or: playPart/?rundownId=default.rundown.json&groupId=aa1LYW7C&partId=sPtWQfd9 Leave other fields empty.

You can find all rundownId by going to http://localhost:5500/api/internal/rundowns/

And for others ids, they appear on the UI when you click on group or part.

The only downside for now is not having feedback...

Velikyi commented 4 months ago

@Velikyi currently you can do that using the internal API. I have a similar setup.

You have to use the Companion http module. Prefix: http://localhost:5500/api/internal/

Then add actions on buttons: Method: POST Url (for example): playGroup/?rundownId=default.rundown.json&groupId=aa1LYW7C Or: playPart/?rundownId=default.rundown.json&groupId=aa1LYW7C&partId=sPtWQfd9 Leave other fields empty.

You can find all rundownId by going to http://localhost:5500/api/internal/rundowns/

And for others ids, they appear on the UI when you click on group or part.

The only downside for now is not having feedback...

Thanks! just tested it, can't get the non-grouped parts to play, but group and group parts works. Shame there's no dynamic workflow there though, so have to edit it every time we change anything...

Elektordi commented 4 months ago

Just checked it, it seems that non-grouped parts have a "hidden" group id. You can find all IDs there: http://localhost:5500/api/internal/rundown/?rundownId=default.rundown.json (example with default rundown ID)

Velikyi commented 2 months ago

Hope this will get prioritized soon. The API is lacking documentation and has to be programmed specific for each ID. A more straightforward prev/next approach with OSC is sorely lacking to make this usable in a live setting without using mouse all the time (the Stream Deck solution is not optimal enough for my use). Also, add the cue function to this as well.