Any reason why changing a MA Trick value/s (fast & delay) which is assigned to a sequence (solely doing colour) does it affect the fade and delay times in my programmer? for example position and colour in programmer
BECOME PART OF THE COMMUNITY - Sign up here
Going to need more information about what you're doing and what you're seeing.
I have also experienced a similar behaviour in my busking showfile. It appears as the following:
I have a few sequences running in the background, containing cues with my position presets. I also have macros, which modify one MAtricks pool item("Position MAtrick"), changing its fade and delay timing. "Position MAtrick" is assigned to all cues in all of my position sequences.
Now, with an empty programmer, I select a group, apply a position preset, and even though MAtricks are empty in the programmer and I do not have any preset timing applied, the lights fade to the new position, with the fadetime that I currently have in "Position MAtrick". If I activate Programmer Time, it overrides this fadetime with whatever timing I have set it to. As soon as I turn it off again, the fixtures return to fading. There is absolutely nothing in the programmer that would prompt this kind of behaviour.
I have traced the phenomenon to two macros I use. One just toggles "Position Matrick" between a 1, 2, and 5 second "FadeFromX" and "FadeToX" "None". If I use this macro to change the values of "Position MAtrick" the above described phenomenon does NOT happen. Only when I use my other macro, which allows me to set a custom "FadeFromX" value causes this to happen. This macro is very similar to the one in the startshow, but here is the full thing:
Set MAtricks 1000 "FadeToX" "None"
Set MAtricks 1000 "FadeFromX" (Position Fadetime?)
Assign Appearance "Fade INPUT Active" At Macro "Position FadeToX Input"
Off Macro "Position FadeToX"
Assign Appearance "Fade OFF" At Macro "Position FadeToX"
(Please ignore that macro is called "Position FadeToX" while it actually changes the FadeFromX Value)
Would love to hear your thoughts about what might be causing this.
That is a feature atm. All active individual fade and delay times are brought to programmer when a attribute is activated. You can overrite this with prog.time. and yes I hate it too.