Presets and Macros

[Pink LD]

I do use presets from time to time but when ever I wish to Macro those presets then I have to have an individual button set to the preset I want for a Macro to give me the Preset I want.
Is it feasible to have one button of all the presets I want and each Macro recall the button and the individually set Presets?
I am aware that priority rules would have to be in place such as LTP or HTP but it sure would reduce the number of buttons I would need for different features (levels) of each channel.
For example on an RGB fixture on a non-Solo Button Page:
Presets for R= 25%, 50%, 75% & 100%
Presets for G= 25%, 50%, 75% & 100%
Presets for B= 25%, 50%, 75% & 100%

I select Red preset of 100% and Macro it on a separate Solo Buttons page.
I then select Red to 50% and Blue to 100% (for a purplish colour) and Macro it putting it on the same Solo Button page.
In this case Priority doesnt matter because I am going from one Solo Button Macro to the other. But in this scenario I can switch between full Red and Purple without having to have built individual buttons with Presets for each level of the three colours. Nor building custom scenes for different colours. I could effectively mix RGB with Macros, as I see fit, with just 3 Preset buttons.

[support]

The Macro does not presently memorize the Preset position.
This is in the TODO list (low priority).

[DHoude]

Sounds like this task woud be better accomplished by a Master intensity slider.

[Pink LD]

I asked about master intensity sliders way back on the V5 forum.And I have made queries about the functions of presets before.
However I am in the process of upgrading and programming to lighting rigs right now so I ask about features to determine how I will invest programming them both for style and effect.
I have in the past made numerous palette based Live boards for all the features I want. Easy enough to do for conventional lights on dimmers but much more complicated for multi channel movers and RGBAW fixtures packed with features...

[support]

Editor, used together with Live, is a good solution to have faders, pan/tilt window and color wheel (using groups).

[Pink LD]

Its too lunky to do it that way. Its easier to have a wing console patched for the features I want and use submasters on the console for complex things. However a wing console has a limited number of faders and the software does not provide me with a way to easily repopulate faders. The last time I used a Chamsys console with PC software and a wing console I used a 8 channel wing and re-populated the wing for each song.
There are a gajillion ways programmers can create and manipulate scenes. There is no one perfect way for all the different designers and various levels of experience. I am just asking so I can create enough flexibility into my approach so that I don't have to make major re-writes for anticipated features. For example I am going to build this rig with presets. I will need multiple buttons to set each value and Macro them. But if you do incorporate a Macro memory of preset positions? I can then go back and do some tweaking and reduce the number of buttons I have.
I just like trying to avoid major re-writes whenever possible.
I am writing 300 minutes of lighting programming for one show in 2 months and 200-300 minutes worth for another show that debuts in late May. So I am largely determining how to build my base structures, palettes as it were, before diving into the custom programming side.

[tomrbland]

The last time I used a Chamsys console with PC software and a wing console I used a 8 channel wing and re-populated the wing for each song.

Don't forget that Chamsys use pallet based programming, Sweetlight/Showxpress isn't designed to be used as a pallet based system.

[Pink LD]

I know that. You know that. But pallette based is what I know best. So I am always trying to wrap my mind around what and how I want to do things...