Is Update reliable?

Hey Scott. I just wanted to answer your question on how we handle autoupdate with multiple fixtures in the programmer and multiple cuelists onstage. You asked what happens if a fixture is in more than one of the cuelists running, but the cuelist have different priority, then which one gets updated? The answer is the higher priority list will always get updated because the lower priority cuelist is not technically controlling output at the time. For example, if you have a studio color at full in list 1 and that same studio color at 60% in list two. If both lists are being played back and list 1 has a higher priority, then as far as playback is concerned only list 1 is effecting stage output. So if you were to put that studio color at 50% in the programmer and then hit update, the higher priority list will be the only cuelist that is offered as an option to be updated. On the other hand, if you were to release the higher priority list and leave the lower priority list playing and then do the same thing, then the lower priority list will be listed as an option for an update since it is now controller the fixture's parameter onstage.

Also remember that when you get the option to update more than one cuelist it's only because parameters in the programmer are effecting parameters that are being controlled by playback on lists other than the currently chosen list. In other words, when you do an auto-update the console looks at all the bits and pieces that make up the current look onstage and tells you where those pieces of the puzzle are coming from. If those pieces are coming from somewhere else other than the currently chose master (list) then you will have the option to update those parameters on their respective lists. If you chose not update those lists, then those parameters don't get updated...anywhere! I hope this information is helpful.

Brendan, as far as updating palettes is concerned I will look into what might be causing this confusion. Are these global pallettes, per type pallettes or per fixture pallettes? There might be a conflict there that the Hog3 is not handling properly.

Hey Scott. I just wanted to answer your question on how we handle autoupdate with multiple fixtures in the programmer and multiple cuelists onstage. You asked what happens if a fixture is in more than one of the cuelists running, but the cuelist have different priority, then which one gets updated? The answer is the higher priority list will always get updated because the lower priority cuelist is not technically controlling output at the time. For example, if you have a studio color at full in list 1 and that same studio color at 60% in list two. If both lists are being played back and list 1 has a higher priority, then as far as playback is concerned only list 1 is effecting stage output. So if you were to put that studio color at 50% in the programmer and then hit update, the higher priority list will be the only cuelist that is offered as an option to be updated. On the other hand, if you were to release the higher priority list and leave the lower priority list playing and then do the same thing, then the lower priority list will be listed as an option for an update since it is now controller the fixture's parameter onstage.

Also remember that when you get the option to update more than one cuelist it's only because parameters in the programmer are effecting parameters that are being controlled by playback on lists other than the currently chosen list. In other words, when you do an auto-update the console looks at all the bits and pieces that make up the current look onstage and tells you where those pieces of the puzzle are coming from. If those pieces are coming from somewhere else other than the currently chose master (list) then you will have the option to update those parameters on their respective lists. If you chose not update those lists, then those parameters don't get updated...anywhere! I hope this information is helpful.

Brendan, as far as updating palettes is concerned I will look into what might be causing this confusion. Are these global pallettes, per type pallettes or per fixture pallettes? There might be a conflict there that the Hog3 is not handling properly.