Good morning everybody,
unfortunately I cannot find "xy pad" threads with the search funtion, so I try with a new one.
I've got 4 moving heads in my QLC+ and various EFX programmed which I start with buttons on the virtual console.
On the virtual console I've also added a XY pad, configured for the 4 moving heads, and I can perfectly see the movings they make when I start an EFX.
But when I want to limit the range of the moving heads on XY pad they continue to use 100% of their range instead of the one I've set.
Could anyone please describe me how to do to have the working area of the moving heads limited? I know there's a chapter in the docs, but there must be something I've missed.
Thank you very much
Andreas
limit the working area of moving heads with xy pad
- lemon
- Posts: 51
- Joined: Mon Apr 13, 2015 6:04 am
- Location: BZ, Italy
- Real Name: Andreas H
Hi plugz,
that's it, thank you very much!!!
Maybe you also know an answer to this: I've added 4 other moving heads, created an EFX with them and added them to the same XY pad, so that I have now 2 buttons (each for every EFX) at the bottom of the XY pad.
Unfortunately I can activate only one at a time. When I click the second one, the first one gets deactivated.
Edit: I've noticed now that the button in the XY pad override the buttons in my solo frame on the virtual console. I thought that I have to ACTIVATE the limitation with the XY pad buttons, but it seems that I have to START the EFX from there, right?
In this case I have to create a XY pad for each moving head group, haven't I?
Thank you again
Andreas
that's it, thank you very much!!!
Maybe you also know an answer to this: I've added 4 other moving heads, created an EFX with them and added them to the same XY pad, so that I have now 2 buttons (each for every EFX) at the bottom of the XY pad.
Unfortunately I can activate only one at a time. When I click the second one, the first one gets deactivated.
Edit: I've noticed now that the button in the XY pad override the buttons in my solo frame on the virtual console. I thought that I have to ACTIVATE the limitation with the XY pad buttons, but it seems that I have to START the EFX from there, right?
In this case I have to create a XY pad for each moving head group, haven't I?
Thank you again
Andreas
-
- Posts: 637
- Joined: Sun Apr 12, 2015 6:30 pm
- Real Name: David
What ? I haven't seen any solo frame in the workspace you shared here (test.qxw)lemon wrote: Edit: I've noticed now that the button in the XY pad override the buttons in my solo frame on the virtual console.
Yes and yeslemon wrote:I thought that I have to ACTIVATE the limitation with the XY pad buttons, but it seems that I have to START the EFX from there, right?
In this case I have to create a XY pad for each moving head group, haven't I?
- lemon
- Posts: 51
- Joined: Mon Apr 13, 2015 6:04 am
- Location: BZ, Italy
- Real Name: Andreas H
You're right, but I've tried these settings in my standard project now.plugz wrote:What ? I haven't seen any solo frame in the workspace you shared here (test.qxw)
Anyway you help me very much, thank you again!
- lemon
- Posts: 51
- Joined: Mon Apr 13, 2015 6:04 am
- Location: BZ, Italy
- Real Name: Andreas H
Noticed something strange now. Just look at my "line" EFX. When I start it with the button in the solo frame everything works fine (its a vertical line movement), but when I start it through the XY pad it gets diagonal. WTF?
- Attachments
-
- test.qxw
- (12.54 KiB) Downloaded 175 times
-
- Posts: 1331
- Joined: Mon Apr 13, 2015 7:05 am
- Location: Bratislava, Slovakia
- Real Name: Jano Svitok
- Contact:
The EFX's parameters width and height are controlled by sliders in XYPad, which is in some cases useful and sometimes it results in what you see.
I don't have a workaround for you
Massimo, David: this is #3 we discussed in the mail from 15.10.2015 (QLC+ 4.10.0 round 2); #2 from that mail might be the reason why EFX is copied in XYPad.
I don't have a workaround for you
Massimo, David: this is #3 we discussed in the mail from 15.10.2015 (QLC+ 4.10.0 round 2); #2 from that mail might be the reason why EFX is copied in XYPad.
- lemon
- Posts: 51
- Joined: Mon Apr 13, 2015 6:04 am
- Location: BZ, Italy
- Real Name: Andreas H
Ok, thank you, though it was not the answer I wanted to get
By the way, I noticed that while every button on the virtual console gets updated when I change the name of an EFX, scene, collection etc. in the functions tab, on the XY pad the names remain the same. Is this a bug?
By the way, I noticed that while every button on the virtual console gets updated when I change the name of an EFX, scene, collection etc. in the functions tab, on the XY pad the names remain the same. Is this a bug?
-
- Posts: 1331
- Joined: Mon Apr 13, 2015 7:05 am
- Location: Bratislava, Slovakia
- Real Name: Jano Svitok
- Contact:
It is a bug caused by the fact that XY Pad uses internal copy of the EFX in order to not destroy the parameters of the original EFX.
The copy is not updated when the original changes.
The copy is not updated when the original changes.
-
- Posts: 1331
- Joined: Mon Apr 13, 2015 7:05 am
- Location: Bratislava, Slovakia
- Real Name: Jano Svitok
- Contact:
After seeing Massimo's latest tutorial (EFX) I got an idea:
The problem is that we create line effects using width=0 and height as needed or vice versa. Massimo created his line effect with width=127, height=127 and rotate=45 or 135.
So, if you create the line that way (using rotation and leaving width and height untouched) then the XY Pad will work.
The problem is that we create line effects using width=0 and height as needed or vice versa. Massimo created his line effect with width=127, height=127 and rotate=45 or 135.
So, if you create the line that way (using rotation and leaving width and height untouched) then the XY Pad will work.