XY Pad: No output when surrounding frame was disabled in Design Mode
Posted: Sat Aug 22, 2015 9:41 am
Edit 1: Added the workspace and required fixtures
Edit 2: I think I've found what's causing the bug: All frames have to be activated when I change to operate mode otherwise the output will not work. I will test if this is only the case in for my workspace or if I can reproduce it with a new one later this day.
Edit 3: I was able to reproduce the bug in a very simple workspace, the frame has to be active when the operate mode is turned on otherwise there's no output from the pad, the bug only affects the pad.
Hello,
I came across the following issue during some live performance where the setup is the following:
I have multiple XY Pads which control the same pair of moving lights but each with a different setting (invert x for device #1, invert x for device #1 and #2, and so on), each XY Pad rests inside a Frame and gets its input from a generic loopback pan tilt device which is controlled by some EFX functions.
I use the "enable / disable" function of the Frames to control how the moving lights should behave, I already tested this and it used to work flawlessly, but I loaded the project yesterday and I got no output from all the XY Pads (the cursor moved and also the loopback input worked correctly once the frame was set to enabled, but the moving lights did not move and also their pan and tilt value in the DMX monitor did not change), even when I removed and added the controlled devices again, also when I moved the XY cursor manually without using the loopback. The only solution to get it working again was to delete the present and create a new XY Pad.
I also experienced similar problems during the design stage when I copied a Frame XY Pad combination instead of creating a new one, which I only considered a small but bearable bug.
Greetings,
Daniel
Edit 2: I think I've found what's causing the bug: All frames have to be activated when I change to operate mode otherwise the output will not work. I will test if this is only the case in for my workspace or if I can reproduce it with a new one later this day.
Edit 3: I was able to reproduce the bug in a very simple workspace, the frame has to be active when the operate mode is turned on otherwise there's no output from the pad, the bug only affects the pad.
Hello,
I came across the following issue during some live performance where the setup is the following:
I have multiple XY Pads which control the same pair of moving lights but each with a different setting (invert x for device #1, invert x for device #1 and #2, and so on), each XY Pad rests inside a Frame and gets its input from a generic loopback pan tilt device which is controlled by some EFX functions.
I use the "enable / disable" function of the Frames to control how the moving lights should behave, I already tested this and it used to work flawlessly, but I loaded the project yesterday and I got no output from all the XY Pads (the cursor moved and also the loopback input worked correctly once the frame was set to enabled, but the moving lights did not move and also their pan and tilt value in the DMX monitor did not change), even when I removed and added the controlled devices again, also when I moved the XY cursor manually without using the loopback. The only solution to get it working again was to delete the present and create a new XY Pad.
I also experienced similar problems during the design stage when I copied a Frame XY Pad combination instead of creating a new one, which I only considered a small but bearable bug.
Greetings,
Daniel
