Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OBS Meda Cue Plugin #321

Open
DMJC opened this issue Jul 3, 2024 · 2 comments
Open

OBS Meda Cue Plugin #321

DMJC opened this issue Jul 3, 2024 · 2 comments
Labels
enhancement/request Suggestion for new features or improvements

Comments

@DMJC
Copy link

DMJC commented Jul 3, 2024

I've been thinking about this after I found that OBS has a CLI Interface I'm thinking of writing my own plugin and I am curious as to whether anyone else is interested in this. I am a C/C++ Programmer. I want input on UI design from people.

I'm proposing an OBS Plugin that would have username/password/connection details via obs-cli. As well as either a list or grid for putting up to 4 OBS Scenes into the Plugin. In the cue control area on the right this would provide the regular Play/Stop Buttons as well as Fade in/Fade Out Volume. The Volume Fade controls would only bind to one Audio Source in OBS (Still to be researched if this is the best approach, or overall application volume fade in/out of OBS, or an option to select application volume vs 1 source.). This plugin would allow you to bind/switch between 4 scenes in OBS within LSP. You would need to manually enter the scene names within the plugin when you configure it. The layout of the buttons would be based on how many are selected by the user.

One source would provide no button, but would show a label with the scene name in it. (As activating the Cue would trigger it, and the stop button would deactivate it).
Two sources would provide 2 buttons one above the other.
3 sources would provide 2 buttons next to each other and 1 below them which would be double the width of the other 2.
4 sources would create a 2x2 grid of buttons.
All buttons would be labelled with the scene names from OBS.

I'll post a mock up picture later.

@DMJC DMJC added the enhancement/request Suggestion for new features or improvements label Jul 3, 2024
@FrancescoCeruti
Copy link
Owner

FrancescoCeruti commented Jul 3, 2024

Sounds interesting 🚀

I'm not 100% sure I've understood this part:

One source would provide no button, but would show a label with the scene name in it. (As activating the Cue would trigger it, and the stop button would deactivate it).
Two sources would provide 2 buttons one above the other.
3 sources would provide 2 buttons next to each other and 1 below them which would be double the width of the other 2.
4 sources would create a 2x2 grid of buttons.
All buttons would be labelled with the scene names from OBS.

I've a very basic experience with OBS, but why not simply creating multiple cues for each scene?

I've also found that OBS provides a websocket API: https://github.com/obsproject/obs-websocket

@DMJC
Copy link
Author

DMJC commented Jul 5, 2024

I've a very basic experience with OBS, but why not simply creating multiple cues for each scene?

  • I've already done that using the web sockets api. What we found when we used it was we would use one cue for a slideshow or a camera transition but we'd then use OBS directly to jump between scenes (one Camera per Scene). This would allow us to use the right hand control column in lSP to control the camera transitions without having to move to the OBS application. By keeping the focus on LSP it eliminates some issues with control focus changes. The setup I was using had 3 SDI cameras attached to a Blackmagic Decklink card in OBS. By having 4 programmable sources on the one cue in LSP we can eliminate interacting with OBS directly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement/request Suggestion for new features or improvements
Projects
None yet
Development

No branches or pull requests

2 participants