• State Not Answered
  • Date
    thc_dan
  • Date
  • Replies 8 replies
  • Subscribers 5 subscribers
  • Views 252 views
  • Users 0 members are here

3.1.6 (2773) - Palette Merge not functioning correctly

3.1.6 (build 2773)
2 x H3
2 x DP8k
2 x Monitors

(BEAM is set to SEPARATE PARAMETERS)

If I have a palette with multiple parameters in it (eg a Beam palette with ALL beam parameters in it)....

Then I select some fixtures (that are in the palette), just touch one beam parameter (eg zoom @ 0%) then MERGE it into the existing palette....

.. then it REPLACES the palette with a zoom only palette!

If I select a single fixture and try the same action (touch its zoom, then merge into the palette) then it strips all the other parameters for ALL fixtures in the palette... leaving only ZOOM.

This is a really major bug!
As I am used to Merging Zoom and Focus values into multiple palettes on a daily basis.... or CTO values into all my colour palettes based on camera balancing).

D
Parents
  • 0
    Dan,

    Double check me on this but I believe what is happening is you have a global all types palette with beam info, you then select the fixtures, change zoom, merge into the palette, and what this does is add per fixture and/or per type exceptions to the all types rule in the palette... when you go back to apply this palette to the fixtures they now ignore any of the recorded all types rules because they now have their own per type/fixture exceptions to follow. Does this sound consistent with what you were seeing?

    In none of my testing have I found the palette to lose or throw out info after a merge. Instead it records it based on our exception rules.
Reply
  • 0
    Dan,

    Double check me on this but I believe what is happening is you have a global all types palette with beam info, you then select the fixtures, change zoom, merge into the palette, and what this does is add per fixture and/or per type exceptions to the all types rule in the palette... when you go back to apply this palette to the fixtures they now ignore any of the recorded all types rules because they now have their own per type/fixture exceptions to follow. Does this sound consistent with what you were seeing?

    In none of my testing have I found the palette to lose or throw out info after a merge. Instead it records it based on our exception rules.
Children
No Data
Related

www.etcconnect.com