Hue/Sat on Subs

I reported the issue a couple of years ago. The only workaround I found was to null out the unwanted parameters after loading.  It can be done with a macro. Maybe with a second report it will get bumped up the list. 

sk7rs_dad, I'm not seeing this issue in 2.1.  Since you are beta testing, can you try this and tell me if you see it.  I don't recall this issue - there was no SCR  in the 2.1 builds that addresses it.

Thanks!

a

I am still seeing the issue. With build 67 I did this:

• Group 201 Full Full
• Group 201 Hue 359 Enter
• Group 201 Saturation Full Enter
• Group 201 Hue Record Sub 12 Enter
• Group 201 Saturation Record Sub 13 Enter
• Group 201 Intensity Record Sub 14 Enter

In blind,

• Sub 12 shows values for both Hue (359) and Saturation (0)
• Sub 13 shows values for both Hue (0) and Saturation (100)
• Sub 14 show values for Intensity (100)

 I then nulled out the unwanted zeroes on Sub 12 and 13 to have values only for Hue and Saturation, respectively using @ Enter in Blind.

Saved and reloaded the show file. The unwanted zeroes are back for Sub 12 and 13.

P.S. I went hunting for my original report and couldn't find it either. It might have been by e-mail or tacked onto another marginally related thread by somebody else.

I am still seeing the issue. With build 67 I did this:

• Group 201 Full Full
• Group 201 Hue 359 Enter
• Group 201 Saturation Full Enter
• Group 201 Hue Record Sub 12 Enter
• Group 201 Saturation Record Sub 13 Enter
• Group 201 Intensity Record Sub 14 Enter

In blind,

• Sub 12 shows values for both Hue (359) and Saturation (0)
• Sub 13 shows values for both Hue (0) and Saturation (100)
• Sub 14 show values for Intensity (100)

 I then nulled out the unwanted zeroes on Sub 12 and 13 to have values only for Hue and Saturation, respectively using @ Enter in Blind.

Saved and reloaded the show file. The unwanted zeroes are back for Sub 12 and 13.

P.S. I went hunting for my original report and couldn't find it either. It might have been by e-mail or tacked onto another marginally related thread by somebody else.

Hmmm... still not seeing this.  I tried this both saving to the showfile and only making the change in persistent storage.  Can you email me the showfile you are seeing this on?  And I can assume group 201 has the channels involved.  Am wondering if it is fixture related in some way.

Thanks much!

a

I get the same behaviour using Selador Desires and Blizzard Pucks. Group 201 is 16 Vivids in HSIC+Str mode.

I see this on the Vivids in HSIC mode (it appears to be related to devices in modes with only HS and no native controls).  I patched a couple of different versions of Pucks... but they all have native mixing.  Can you tell me exactly which version of Blizzard fixture?  (Just to make sure it IS only devices with only HS settings?)

Thanks!

a

Mea culpa.  I lied about the Pucks. I should have retested before including them. The issue does appear to manifest with only the Vivids and Lustr+s in the rig, alll patched as HSIC.

Thanks for the confirmation.  Has been SCR'd.

Appreciate the help!

a