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

Enhancement: Separate rgbeffects file into multiple files #888

Open
kmacmaster opened this issue Jul 30, 2017 · 1 comment
Open

Enhancement: Separate rgbeffects file into multiple files #888

kmacmaster opened this issue Jul 30, 2017 · 1 comment

Comments

@kmacmaster
Copy link

Currently, for each config, we have a keybinding, network, and rgbeffects file. On top of that, there is a folder of individual color pallets.

I think it would be helpful to further break down the rgbeffects file so the model data and associated previews are separate from the preset effect data and the application defaults / customizations. Then, if the config would allow us to map each one of these paths, it would allow you to have multiple house configurations / models without having to redo / copy over your networks, keybindings, pallets, and effects, application customizations. Essentially, it would allow you to just switch the house models from say... Halloween to Christmas while not having to copy all of your other files over for each new configuration. This would come in handy when you create a new color pallet or effect and have to copy it over to all of your configurations.

The attached is a screen grab from Sonar Platinum that somewhat demonstrates the breakdown.

untitled

@kppankratz
Copy link

I was about to put in a request for this exact same thing. I'd love to see the presets on a global level versus localized to the current show folder to keep all of the show folders in sync for the presets.

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