• State Verified Answer
  • +1 person also asked this people also asked this
  • Date
    Tom Shorrock
  • Date
  • Replies 12 replies
  • Subscribers 186 subscribers
  • Views 4095 views
  • Users 0 members are here

feature request Preset update cue stack update

Would there be a way to add a modifier to update preset that would travel the cue stack and update that change into the preset?

Example: 

Preset 1 contains Channel 1 at full and channel 2 is null.

Record cue 1,2,5, and 10 with preset 1.

It is decided to add channel 2 into preset 1, there is a modifier that will visit cues 1,2,5, and 10 to mark channel 2 as captured by the preset

This way, you do not need to traverse the cue stack to find each instance of the preset and manually reapply the preset.

Parents
  • 0

    Based on what criteria?. Would this modifier be:  If preset 1 is used in any cue, on any set of channels and any set of parameters, add channel 2 as well?

    Thanks!

    a

  • 0 in reply to Anne Valentino

    Anne, while this is currently possible with copy commands it could be a lot more elegant and way less time consuming and error prone.

    i think we would have to consider two cases:

    A) add parameter to existing channels in presets. this is a very common thing when changing fixture types.
    B) add new channels to exisiting presets. which is the case Tom is explaining in this post.

    B would currently be solvable with a simple copy command across all cues in blind, but A is not easily solvable when adding additional parameters to the preset in the first place (out of scope of this post) and is at least just as bad when adding the new parameters to cues.

    i don't think it's a good idea to make this a property of the preset (as MA have done), it should be two functions that would allow us to push either new parameters of exisitng channels (case A) or additional channels (case B) to cues.

    something like:
    Preset 2 {PushParams} or {PushChannels}
    or Blind, Cue 10 Thru 20 Enter. RecallFrom Preset 3 {ExpandParams}/{ExpandChannels}

    ?

    thx, ueli

Reply
  • 0 in reply to Anne Valentino

    Anne, while this is currently possible with copy commands it could be a lot more elegant and way less time consuming and error prone.

    i think we would have to consider two cases:

    A) add parameter to existing channels in presets. this is a very common thing when changing fixture types.
    B) add new channels to exisiting presets. which is the case Tom is explaining in this post.

    B would currently be solvable with a simple copy command across all cues in blind, but A is not easily solvable when adding additional parameters to the preset in the first place (out of scope of this post) and is at least just as bad when adding the new parameters to cues.

    i don't think it's a good idea to make this a property of the preset (as MA have done), it should be two functions that would allow us to push either new parameters of exisitng channels (case A) or additional channels (case B) to cues.

    something like:
    Preset 2 {PushParams} or {PushChannels}
    or Blind, Cue 10 Thru 20 Enter. RecallFrom Preset 3 {ExpandParams}/{ExpandChannels}

    ?

    thx, ueli

Children
Related

www.etcconnect.com