-
-
Notifications
You must be signed in to change notification settings - Fork 204
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
Comments
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? |
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. |
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.
The text was updated successfully, but these errors were encountered: