Skip to content

Show Outputs in Multisync #2100

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

Open
cybercop23 opened this issue Jan 1, 2025 · 4 comments
Open

Show Outputs in Multisync #2100

cybercop23 opened this issue Jan 1, 2025 · 4 comments

Comments

@cybercop23
Copy link
Contributor

More a nice to have support feature.... with folks misconfiguring their controllers, it will be nice if the Multisync page will show some indicator for the all FPP based controllers if they have Outputs configured. Most of the time that's a miss-config and it will make it easier to identify and fix vs having to go to each FPP based controller to check.

Bouus if we show if Inputs are enabled, or better yet.. default Inputs to On.

@OnlineDynamic
Copy link
Collaborator

Bit confused.. this talks of inputs as well as outputs? Are you after both? And are you talking about all output types? And are you wanting to check that there is just something entered in an output and it's enabled? Or are we trying to compared configuration against something like a channel map?

@cybercop23
Copy link
Contributor Author

I didn't recall exactly what Dan or Darryl or was it Scott, said about why Enable Inputs doesn't default to checked/on/yes.
But we see issues with both inputs and outputs not being configured correctly.
So the idea is to show two icons, or some sort of indication, that the controller has Inputs enabled and if any Outputs are checked, doesn't matter if defined - are they actually enabled, show an icon indicating it has enabled outputs. So I'm most cases with the exception of the player, all others won't have any outputs enabled.

@dkulp
Copy link
Contributor

dkulp commented May 16, 2025

I didn't recall exactly what Dan or Darryl or was it Scott, said about why Enable Inputs doesn't default to checked/on/yes.

If the inputs are not enabled, we stick listeners on the ports that will then warn the user if they receive data. This helps catch all kinds of configuration issues like masters sending data to remotes and such. If the inputs ARE enabled, we assume that's what the user actually wants so if data arrives, it's actually processed like data (and there are use cases for it) and that can result in weird flickering and such if not properly setup.

@cybercop23
Copy link
Contributor Author

Ahh yes, thanks Dan for reminding me. I guess we can look at stats to see the % of folks that have it on, or maybe somehow alert in xLights when doing 💡. But that's just for the default option setting.
The indication on the multisync should show

Image. or

Image

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

4 participants