[Bug] False Intensity Palette Indications

Buzz313thBuzz313th Registered User, Hog Beta
Came across this today at work and it's reproducible on H4PC.

Please test to confirm...

Fixtures previously associated with intensity palettes are still indicating referenced to IPalette in editors and output window after fixtures have changed to raw values and updated...


Steps to reproduce

1. Create new show and patch 100 Desk Channels normally

2. Select 1-10, set intensity to 100% and save to intensity pallette #1... then clear programmer

3. Select 1-10 in programmer and select intensity pallette 1

4. Record to 1/1

5. Set programmer and output to view palettes

6. run 1/1

7. select 1-10 in programmer and suck

8. notice programmer and output indicate correct palette and also indicate correct raw values.

9. clear programmer and select 1-10 and suck. Then change intensity to 50% and update cue 1/1 WITHOUT UPDATING THE INTENSITY PALETTE.

10. Clear programmer

11. change programmer and output window to view palettes

12. select 1-10 in programmer and suck

13. notice that 1-10 still shows a reference to intensity palette 1, when it should only show a raw value of 50%. Change programmer and output window to show values and not palettes. Notice that the raw intensity values are correct, but when you view palettes again, it is still indicating a reference to intensity palette 1.

14. Just to make sure that we didn't accidentally update the palette, open intensity palette 1 and check values for fixtures 1-10. They should still indicate 100%. Then check your output window and programmer and you will see that they are indicating a locked reference to intensity palette 1 even though the onstage raw values are not the same as the values recorded in intensity palette 1.

Sorry for the long winded post, but I figured this might be an important one since the desk is misinforming the "Nut Behind The Wheel".

JB

Comments

  • cmuenchowcmuenchow Registered User, Administrator, HES Staff
    edited December 2012
    Jeff, I see what's going on here. Thanks for the detailed and well written report. What is happening is that the feedback loop is not refreshing palette references for cues that are onstage when the update/merge is performed. What I am seeing is that the feedback does correct itself once the list is reasserted (or played forward). It almost like the feedback loop needs to be reminded that not only did the raw data change but so did the old palette reference. Indeed this is a valid bug and I will get it logged for you (bug 17486). Thanks for the great report!
  • barnes2000barnes2000 Registered User, Hog Beta
    edited December 2012
    Chris,
    I am seeing this issue too on the Hog4, however, Assert is not doing anything. If I hit Goto + Cue #, Enter, It does correct it, but it seems like the Assert key is not functioning.
Sign In or Register to comment.