sorayuki / obs-multi-rtmp

OBS複数サイト同時配信プラグイン
https://sorayuki.github.io/obs-multi-rtmp/
GNU General Public License v2.0
3.45k stars 481 forks source link

Suggestion: Allow a shortcut to be made to start and stop the stream #166

Open LanceLake opened 2 years ago

LanceLake commented 2 years ago

I'd like to be able to use my streamdeck or bot to send a keypress to start and a different one to stop. Can you program in this functionality?

iandouglas commented 2 years ago

If you tell the plugin to start streaming to those platforms when you start broadcasting in OBS, then there's already a plugin to do this.

LanceLake commented 2 years ago

True... However, this doesn't solve my issue.

If I start streaming directly when OBS starts and stops, then the preshow I do (which has youtube videos in it) gets flagged by Youtube. What I'd like to do is to start my normal twitch streaming, then when my intro starts (1:40 of title music, then me live), I would like to automatically trigger YouTube streaming (or whatever else streaming).

Also when I end, because I don't sync it to OBS, I have to wait for the end credits to stop streaming to the other services instead of letting the bot handle it after the outro.

See the problem? :)

iandouglas commented 2 years ago

Yes, I understand your use case.

Stream deck can communicate with APIs, and that does feel a bit out of the design for this plugin. I imagine this could/would end up being a separate project or something. I'll bow out of the conversation and let the author answer. :)

LanceLake commented 2 years ago

It doesn't need to be an API. It just needs to be a shortcut that when a key is pressed, the streams with that shortcut listed start and when you press the other key, the streams with that key selected will stop. :) It's reading the keyboard, not APIs. :)

Ashtlind commented 3 weeks ago

Could we potentially add support for the built in OBS websocket command CallVendorRequest to start and stop targets? That way a whole api is not needed but we can leverage the existing connection made to the OBS websocket.

Like the implementation use by https://github.com/WarmUpTill/SceneSwitcher/wiki/Switching-scenes-for-Aitum-Vertical-plugin

The websocket command would be something like this:

    "op": 6,
    "d": {
        "requestType": "CallVendorRequest",
        "requestId": "someRandomId",
        "requestData": {
            "vendorName": "obs-multi-rtmp",
            "requestType": "start-target",
            "requestData": {
                "target_id": "123456789"
            }
        }
    }

This would allow anything that can currently talk to OBS over websocket to trigger and stop streams.

sorayuki commented 3 weeks ago

it requires the code structure become MVC pattern or something alike, which it currently not be.


From: Ashton Lind @.> Sent: Thursday, August 22, 2024 9:14:19 AM To: sorayuki/obs-multi-rtmp @.> Cc: Subscribed @.***> Subject: Re: [sorayuki/obs-multi-rtmp] Suggestion: Allow a shortcut to be made to start and stop the stream (Issue #166)

Could we potentially add support for the built in OBS websocket command CallVendorRequest to start and stop targets? That way a whole api is not needed but we can leverage the existing connection made to the OBS websocket.

Like the implementation use by https://github.com/WarmUpTill/SceneSwitcher/wiki/Switching-scenes-for-Aitum-Vertical-plugin

The websocket command would be something like this:

{ "op": 6, "d": { "requestType": "CallVendorRequest", "requestId": "someRandomId", "requestData": { "vendorName": "obs-multi-rtmp", "requestType": "start-target", "requestData": { "target_id": "123456789" } } }

This would allow anything that can currently talk to OBS over websocket to trigger and stop streams.

― Reply to this email directly, view it on GitHubhttps://github.com/sorayuki/obs-multi-rtmp/issues/166#issuecomment-2303380188, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AEAUME4SPCTUVDXQCEMJ5Q3ZSU3OXAVCNFSM6AAAAABM5DGFDSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMBTGM4DAMJYHA. You are receiving this because you are subscribed to this thread.Message ID: @.***>