Hello QLC+ experts,
actually I have a new little problem and want to ask, why this setup did not work as expected.
I have an "Akai APC Mini" with 64 Buttons (ok, some more) and different lights like Moving Heads, simple Spots and more.
Actually I have 'programmed' some chasers with different colors which I can start and stop using the buttons on the APC. Because only one chaser for example of the Moving Heads should run, I have configured some SoloFrames for each different lights like Moving Heads and Spots, working fine.
Actually I also use chasers for the moves too and have split these ones also in chasers for vertical and horzontal movings, so I can create different effects with the Heads with only a handful of different chasers. EVERYTHING IS WORKING UNTIL HERE!
As you can imagine I have now many buttons with functions and I lost a little bit the overview where the color chasers and the movement chasers are stored on which buttons although I use different colors for the buttons on the APC, but also the 64 buttons are not enough.
The idea now was to create another SoloFrame with pages, the first page one only should contain the buttons for the color chasers, the second one has the buttons for the movement chasers, until here also no problem. Because there still should only run one chaser for the colors of the Moving Heads (as an example) I have to use another SoloFrames within the SoloFrame on the first page, on the second page two SoloFrame for the X and the Y-movement chasers, also no problem for the creation of this until here!
If I create a single button on a SoloFrame page and assign it to a button of the APC, I can see a feedback in the configuration like "APC Button 8-3 (Page 1)", if I switch to the second page and do the same, therefor it looks like "APC Button 8-3 (Page 2)", everything fine here.
If I now create a SoloFrame on page one of the first SoloFrame, create a button and want to assign this one to one of the APC, the information on which page of the first SoloFrame I am is lost. If I do the same on the second page, I can assign the button. If I start now QLC+, I can switch the pages of the first SoloFrame, see there the other SoloFrames, but when I hit a button, it's recognized in the SoloFrames of both pages.
Example:
a big SoloFrame "around" all
- on page one of the first another SoloFrame "Colors Moving Head" with three buttons also configured on APC as buttons 1-1, 1-2 and 1-3
- on page two of the first another SoloFrame "Moving X axis" with three buttons also configured on APC as buttons 1-1, 1-2 and 1-3
- on page two of the first another SoloFrame "Moving Y axis" with three buttons also configured on APC as buttons 2-1, 2-2 and 2-3
as you can see the buttons 1-1, 1-2 and 1-3 are double assigned on two different pages, normally this works. But they are in another SoloFrame and at this point it doens't work any longer. If I push 1-1 and I am on page one of the first frame, also the button configured on page 2 in the SoloFrame is activated.
Simple question, why? Is there another way to realize this?
Bye
Alhifi
Using SoloFrames within SoloFrames, but the assigment of buttons did not work as expected
- GGGss
- Posts: 3052
- Joined: Mon Sep 12, 2016 7:15 pm
- Location: Belgium
- Real Name: Fredje Gallon
I didn't read your post completely but I can say one thing:
!! don't use a solo frame within a solo frame !!
To find a workaround I should read your complete post.
!! don't use a solo frame within a solo frame !!
To find a workaround I should read your complete post.
All electric machines work on smoke... when the smoke escapes... they don't work anymore
- Alhifi
- Posts: 43
- Joined: Mon Feb 11, 2019 6:25 pm
- Real Name:
Hi GGGss,
thank you very much, would be nice, if you have an idea to solve the ... ok, not really a problem ...
Perhaps I can use a normal Frame to separate the color section from the moving section on another page.
But I think I still have to use one or more solo Frames to guarantee that only one chaser is active for one type of lights. The only problem are the doubled assigned buttons of the APC Mini on the different pages, maybe it works with a normal Frame, but actually I can not imagine that a normal Frame is different here than a solo one.
Bye
Alhifi
thank you very much, would be nice, if you have an idea to solve the ... ok, not really a problem ...
Perhaps I can use a normal Frame to separate the color section from the moving section on another page.
But I think I still have to use one or more solo Frames to guarantee that only one chaser is active for one type of lights. The only problem are the doubled assigned buttons of the APC Mini on the different pages, maybe it works with a normal Frame, but actually I can not imagine that a normal Frame is different here than a solo one.
Bye
Alhifi
- Alhifi
- Posts: 43
- Joined: Mon Feb 11, 2019 6:25 pm
- Real Name:
It works now when I use a normal Frame to switch between the buttons planned to use for color chasers and moving chasers, on the different pages I can then use solo Frames to change between different chasers and only one of them is running, great.
I mapped the buttons of the APC Mini now on the different chasers and use the feedback function to set the different colors of the APCs buttons to see which button is assigned (color on) and which one is active (color flashing).
If I switch now the pages of the normal Frame the state of the buttons will not be updated to show what's actually active on the selected page, so it's nice that I can use double assigned buttons, but I cannot see in which state the button and therefor which chaser is active.
Is it possible to get that working?
Bye
Alhifi
I mapped the buttons of the APC Mini now on the different chasers and use the feedback function to set the different colors of the APCs buttons to see which button is assigned (color on) and which one is active (color flashing).
If I switch now the pages of the normal Frame the state of the buttons will not be updated to show what's actually active on the selected page, so it's nice that I can use double assigned buttons, but I cannot see in which state the button and therefor which chaser is active.
Is it possible to get that working?
Bye
Alhifi
- Alhifi
- Posts: 43
- Joined: Mon Feb 11, 2019 6:25 pm
- Real Name:
Maybe my problem is solved now!
I use a normal frame to switch between the color section and the movement section as I described above, on the two pages are some solo frames with the buttons. The problem was, that the switch of the pages did not change the state of the buttons on the Akai APC Mini!
Normally the response values for the big buttons on the Akai APC Mini are
0 -> off
2 -> green
4 -> green flashing
6 -> red
8 -> red flashing
10 -> yellow
12 -> yellow flashing
-> 255 always green
I have created a complete Akai APC Mini with all buttons and sliders on both pages.
Since off should be the value 0, I put this into the fields for the user lower and upper response values of a empty buttons, but it did not work. After "trial and error" I tried many combinations and just before giving up I tried a 1 within this fields ... and it WORKS!
The color section (still in progress)
The movement section (still in progress)
The value 1
When I switch between the both pages the colors of the buttons changed to the actual state on that page, even flashing, on or still off! GREAT!
Now I still have to create more chasers for color and moves and to implement again the configuration for a "Novation Launchkey Mini" to do a manual light show while playing the keyboard!
Bye
Alhifi
I use a normal frame to switch between the color section and the movement section as I described above, on the two pages are some solo frames with the buttons. The problem was, that the switch of the pages did not change the state of the buttons on the Akai APC Mini!
Normally the response values for the big buttons on the Akai APC Mini are
0 -> off
2 -> green
4 -> green flashing
6 -> red
8 -> red flashing
10 -> yellow
12 -> yellow flashing
-> 255 always green
I have created a complete Akai APC Mini with all buttons and sliders on both pages.
Since off should be the value 0, I put this into the fields for the user lower and upper response values of a empty buttons, but it did not work. After "trial and error" I tried many combinations and just before giving up I tried a 1 within this fields ... and it WORKS!
The color section (still in progress)
The movement section (still in progress)
The value 1
When I switch between the both pages the colors of the buttons changed to the actual state on that page, even flashing, on or still off! GREAT!
Now I still have to create more chasers for color and moves and to implement again the configuration for a "Novation Launchkey Mini" to do a manual light show while playing the keyboard!
Bye
Alhifi