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

0 Chris Muenchow over 13 years ago

Is the original palette global, per type, or per fixture?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 thc_dan over 13 years ago

It only has Mac2000 profiles in it... but has a different focus value for each fixture... all other values are the same.

The merge issue doesn't happen with my colour palettes (that have more than 1 fixture type in them) but does happen with my beam palettes that also have my washlights (as well as the M2k spots) in them.

Do you want me to send a showfile?

D
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Chris Muenchow over 13 years ago

Yes, please upload the show file and I will dig in.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 thc_dan over 13 years ago

Showfile sent.

D
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Chris Muenchow over 13 years ago

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.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 thc_dan over 13 years ago

That does sound consistent....
... selecting all the fixtures, then applying and re-recording the palette once seems to solve the problem and make the palettes behave properly afterwards.
I recorded all these palettes with ALL fixtures of a particular type selected... so it is odd to me that the desk decided that this was a global all-types palette...

I would have thought that it would have applied the global palette to all channels except the ones in the exception.......
... I guess its because I keep beam parameters separate that I have never hit this problem with colour palettes

D
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Chris Muenchow over 13 years ago

It does open an interesting debate on how exceptions are applied to al types rules. I agree there are many times when I would prefer to have the all types rule still apply underneath the exception but in many cases the user just wants to add a new rule to the palette for a group of fixtures but not neccsarily have them follow the same rules as the other fixtures. The good news is that we do give the type options on the merge toolbar when performing the merge... the problem is that it's not always intuitive.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 thc_dan over 13 years ago

I had never even noticed the "More" button when merging..
Thanks for pointing it out.

D
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel