Closed zitrusgelb closed 1 year ago
so you are missing the name of the scene in the hotkey name? but the hotkey is registered on the scene, so obs_hotkey_get_registerer in combination with obs_source_get_name can be used to get the scene the hotkey is registered too. if OBS-Websocket does not expose this data I would suggest a change in OBS-Websocket instead of a work around in this plugin. in the mean time I am looking into registering the plugin as a vendor in obswebsocket for adding calls to allow to switch scene that way
Yes, I missed that. Thanks for the insight, sadly OBS-Websocket doesn't expose these things, if I'm not blind. Registering as vendor is defenitely the cleanest option. I'm gonna open an Issue over there. Maybe I'm not alone
In master I added 2 vendor requests. You download a test build here
{ "requestType": "CallVendorRequest", "requestData": { "vendorName": "downstream-keyer", "requestType": "dsk_select_scene", "requestData": { "dsk_name": "DSK 1", "scene": "" } } }
{ "requestType": "CallVendorRequest", "requestData": { "vendorName": "downstream-keyer", "requestType": "get_downstream_keyers" } }
also added a vender event called dsk_scene_changed
When using the DSK with e.g. OBS-Websocket you can identify the Hotkey. Previously it always was "Show / Hide on DSK x" now it is "DSK x.sceneName.enable/disable", while maintaining the previous style in the OBS settings (Hotkey Description). Therefore making remote controlling the DSK possible