So I have created FX stop cues with times on my exec window. For example cues with 0sec, 3sec and 10sec FX stop values. After watching your video I am curious if there is a way to create FX release cues in 0sec, 3sec and 10sec so that I can add those to my exec window also?
Another discovery is that CMY fixtures perform the correct behavior of both FX IN and FX OUT; but in the case of RGB fixture it only does it correctly with FX OUT ... Ignore, because the time of FX IN
While testing I see that the input and output time works for us with position, but with int and beam fx it doesn't. It makes the sudden change. What am I doing wrong?
doesn't work that way as when you are stomping Position FX - you are basically loading Zero Position for FX into the programmer and defaulting Position data to default [i.e. 50/50 and pan and tilt]
@@ChamSysProUsers When I do this with intensity it makes all the fixture go dark, just like an blackout. Do I need to change an setting? It Works fine with color beam and position
sorry for not making it with a lot of glitter and giggling, memes from insta etc for entertainment purposes :D a lot of things sadly maybe boring to teach and explain, but sometimes I'm the only one who cares to explain stuff to others who don't read manuals or not bothered to check release notes :) but jokes aside, I take it as valuable feedback. thanks.
So I have created FX stop cues with times on my exec window. For example cues with 0sec, 3sec and 10sec FX stop values. After watching your video I am curious if there is a way to create FX release cues in 0sec, 3sec and 10sec so that I can add those to my exec window also?
Another discovery is that CMY fixtures perform the correct behavior of both FX IN and FX OUT; but in the case of RGB fixture it only does it correctly with FX OUT ... Ignore, because the time of FX IN
While testing I see that the input and output time works for us with position, but with int and beam fx it doesn't. It makes the sudden change. What am I doing wrong?
In the case of STOP - FX INT the input and output time does not behave correctly
With COL FX the behavior is correct .. Respects the time of FX IN and FX OUT
how about when i stomp the position fx drop to a certain position
doesn't work that way as when you are stomping Position FX - you are basically loading Zero Position for FX into the programmer and defaulting Position data to default [i.e. 50/50 and pan and tilt]
Is there also a way to make it work as well with pixel map fx?
@@ChamSysProUsers unfortunaly it does not work fore the simple pixelmapper.
Thanks you fore your great videos it helps me a lot
When I do this with intensity it makes all the fixture go dark, just like an blackout. Do I need to change an setting? @ChamSysProUsers
well, when u apply dim fx - it overtakes dimmer channel. so stomping dim fx - kills intensity.
What if you want to stop just one group of lamps and not all groups?
then select whichever group you want to stomp and then apply Stomp FX
@@ChamSysProUsers When I do this with intensity it makes all the fixture go dark, just like an blackout. Do I need to change an setting?
It Works fine with color beam and position
It seems that the function of track out or size or with PIXEL FX does not work like the rest
It's funny, but if the two FX (normal and STOP FX) are in the same CS (cue 1 and cue 2) if the fade fx in and fx out behave correctly
A bit borring explanation. But THANK YOU so much! Few hours before a gig and I have Chamsys (not a desk I work with)
sorry for not making it with a lot of glitter and giggling, memes from insta etc for entertainment purposes :D a lot of things sadly maybe boring to teach and explain, but sometimes I'm the only one who cares to explain stuff to others who don't read manuals or not bothered to check release notes :)
but jokes aside, I take it as valuable feedback. thanks.