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

separate instances for control and display (connected via network) #279

Open
mathisdt opened this issue Jun 22, 2023 · 0 comments
Open

separate instances for control and display (connected via network) #279

mathisdt opened this issue Jun 22, 2023 · 0 comments

Comments

@mathisdt
Copy link
Owner

mathisdt commented Jun 22, 2023

In some installations it is difficult to run the display cables from the computer at the control desk (in the back of the room) to the displays and projectors (at the ceiling in the front of the room). It would be easier if the connection could work via WiFi network. Also, at least on Windows, some graphics cards (or their respective drivers) have problems displaying everything correctly, so a separate SDB instance running under Linux would make sense.

To make this possible, it would be necessary to add special operation modes and some configuration for it ( ⚠️ 🛑 maybe this doesn't solve the problem - presentations apart from SDB are not possible using this setup):

  • split mode, control part: the SDB doesn't use the configured display settings at all (especially it doesn't open any windows to display the lyrics) but it communicates over network what should be displayed, and how (including scrolling etc.)
  • split mode, display part: the SDB doesn't show the control window but only one or two lyrics windows - the content is received via network
  • configuration (via command line parameter or config file entry) for split mode, control part: under which hosts / ports / prefixes are the displays reachable? and with which authentication?
  • configuration (via command line parameter or config file entry) for split mode, display part: on which port (and with which prefix) should the SDB listen for commands? and which authentication is used?

The listening part should provide an authenticated REST-like API so things can be scripted (even without having a SDB controlling what's displayed). The authentication can be a pre-shared token, there seems to be no need for something elaborate like OAuth2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant