On my RasPi build, I have 10 scene buttons (colors, lets say) and a chaser button (I call it Color Fader) all set in a solo frame. I can pick a solid color, switch between colors, and when I want, switch to the Color Fade which sequentially runs through the 10 color functions with a fade in/out time. On the RasPi, when I switch to the Color Fade, it cancels out any Scene button and runs the chaser - as it should, being in a solo frame).
I just recently built an Ubuntu 18.04 mini computer to potentially replace the RasPi. I am running QLC+ 4.12. However, when I load the show file from the RasPi, my Color Fade chaser function inside the solo frame doesn't work the same. As soon as I press it, the whole chase never starts and all the buttons cancel out. Was there a change made to QLC+ that would significantly change how this works? And, why does it work so well on the RasPi build? In one of my previous posts regarding Collections and feedback of the child functions, I was informed that the "function buttons" are essentially "virtual"... meaning, (in context of a "Parent Function" operating "Child Funtions") that the button itself isn't running the DMX signal, its the Parent Function that controls DMX and its the "Virtual Console" effect of showing you the active "Child" function. So, if I have a Parent Function (Chaser) running in a solo frame with Child Functions (color scenes), why does the chaser cancel out as soon as it is launched?
It would seem as though the answer is quite clear - a Solo Frame is a SOLO frame - one function at a time... but it works SO well on the RasPi.
Thanks team
Chaser in a solo frame with child functions....
-
sbenejam
- Posts: 607
- Joined: Sun Apr 12, 2015 6:28 pm
- Real Name: Santiago Benejam Torres
- Contact:
Can you share your workspace project?.
-
GGGss
- Posts: 3052
- Joined: Mon Sep 12, 2016 7:15 pm
- Location: Belgium
- Real Name: Fredje Gallon
The raspi outcome is unexpected...
If you fire a cue from within a solo frame ... everything else is disabled.
If you have a chaser inside that solo frame using the same cues as with the buttons, the use of the chaser will reset everything else including itself.
Say step 1 in the chaser is red scene. Start the chase
* red-scene comes up
* red button comes up
* QLC+ sees this as a 'red button press'
* disables red scene
* end
Why does it work 'wonderwell' on your raspi? I can only think of slow performance overseeing the 'red button press'??
Workaround:
copy your 10 scenes used in the chaser.
Now you won't see this behaviour (because the buttons aren't bound to these scenes)
But it's odd to have a chaser inside a solo frame
Now your single colours can be chosen again
If you fire a cue from within a solo frame ... everything else is disabled.
If you have a chaser inside that solo frame using the same cues as with the buttons, the use of the chaser will reset everything else including itself.
Say step 1 in the chaser is red scene. Start the chase
* red-scene comes up
* red button comes up
* QLC+ sees this as a 'red button press'
* disables red scene
* end
Why does it work 'wonderwell' on your raspi? I can only think of slow performance overseeing the 'red button press'??
Workaround:
copy your 10 scenes used in the chaser.
Now you won't see this behaviour (because the buttons aren't bound to these scenes)
But it's odd to have a chaser inside a solo frame
Now your single colours can be chosen again
All electric machines work on smoke... when the smoke escapes... they don't work anymore
-
chasersync
- Posts: 13
- Joined: Sun Aug 20, 2017 1:09 am
- Real Name:
Hello,
it might be a bit late, but the described behavior seems to be the change of Solo Frames mentioned in
viewtopic.php?f=17&t=11326
The Raspberry might have an Image <=4.10.x and on Ubuntu you might have a Version >=4.11. Maybe you want to try an older version.
My workaround was to put the scene into a chaser with only that scene and that chaser linked to the button in the solo frame.
Like this the SOLO-Frame works as the Button enabling the chaser is disabled when the color fade is activated
and a change of the scene only needs to be done once.
it might be a bit late, but the described behavior seems to be the change of Solo Frames mentioned in
viewtopic.php?f=17&t=11326
The Raspberry might have an Image <=4.10.x and on Ubuntu you might have a Version >=4.11. Maybe you want to try an older version.
My workaround was to put the scene into a chaser with only that scene and that chaser linked to the button in the solo frame.
Like this the SOLO-Frame works as the Button enabling the chaser is disabled when the color fade is activated
and a change of the scene only needs to be done once.
-
tavonmarkov
- Posts: 35
- Joined: Sun Apr 12, 2015 6:33 pm
- Real Name: Tavon Markov
Greetings QLC+ Forum.
Thank you to user chasersync. I read the post. It appears that Massimo changed the way SOLO frames work. The option to have a Chase within a SOLO frame to run functions ALSO within the same Solo Frame was a major feature as it automated a number of functions. However I want to reopen discussion on this topic. I am having a hard time imagining that no other user has wanted to design a workspace like this. It would appear that the only way to regain my ability to run my workspaces as designed, is to revert to a pre-4.11.x revision of QLC+.
I have worked up a different way to explain this.
Imagine a situation in which you have 10 functions: 8 Scenes and 2 chasers. You have a MIDI devices that has 5 MIDI buttons that send NOTE ON messages.
In QLC+, you create a SOLO frame, with 2 pages.
On page 1, you create 4 buttons for "SOLID" color scenes, and a button for a chase containing these 4 SOLID scenes. Assign each of the widgets to an individual MIDI control.
On Page 2, you create 4 buttons for "SPLIT" color scenes, and a button for a chase containing these 4 SPLIT scenes. Again, using the same 5 MIDI triggers, assign each of the widgets to an individual MIDI control.
SOLID - scenes where all fixtures are set to a single color (ex. all back LED Pars are RED)
SPLIT - scenes where some fixtures are set to a single color, and others are set to a different color (ex. All ODD back LED Pars are RED, and all EVEN pars are GREEN)
In this situation, we will assume the Scenes are assigned to MIDI buttons 1-4, and the Chases to MIDI button 5. Seeing as you only have 5 MIDI triggers, you want to be able to control all the scenes visible in the active frame, regardless of which "mode" your SOLO frame is in.
Page 1, would be considered SOLID "mode" as it contains ONLY SOLID scenes, whereas Page 2 would be considered SPLIT "mode" as it contains ONLY SPLIT scenes.
Scenarios
1.) Imagine a scenario in which you activate the RED scene on Page 1, but then want to activate the GREEN scene on Page 1. SOLO Frame will allow RED to deactivate when you activate GREEN.
2.) Imagine a scenario in which you activate the RED scene on Page 1, then want to activate the RED GREEN scene on Page 2. SOLO Frame will allow RED to deactivate on Page 1 when you activate RED GREEN on Page 2.
3.) Imagine a scenario in which you activate the RED scene on Page 1, but then want to activate the SOLID COLOR CHASE on Page 1 to run. The Chaser, which steps through these 4 scenes on Page 1 in order, would activate. You would want the previously selected scene (RED) to deactivate, and the SOLID COLOR CHASE to start.
4.) Imagine a scenario in which you activate the RED scene on Page 1, but then want to activate the SPLIT COLOR CHASE on Page 2 to run. The Chaser, which steps through these 4 scenes on Page 2 in order, would activate. You would want the previously selected scene (RED) to deactivate, and the SPLIT COLOR CHASE to start.
Scenarios 1 & 2 are basic, and function as they are design on all platforms.
Scenarios 3 & 4, while running on QLC+ 4.11.0 GIT, on Rasbian OS Jessie on RasPi, this situation works as described.
Scenarios 3 & 4, while running on QLC+ 4.x.x on all other OSes, this situation doesn't work at all. The SOLID COLOR CHASER activates (Activates RED scene in SOLO frame, deactivates SOLID COLOR CHASE), then ends.
So, REAL WORLD.
I have a Novation LaunchPAD. I want to utilize 2 rows of buttons for colors. I can use 2 pages (One for SOLID, One for SPLIT). I want to use 15 of the 16 buttons for color-scene functions for each page and the last for the corresponding Chase function.
15 "X" Colors, and 1 Chase
[color1] [color2] [color3] [color4] [color5] [color6] [color7] [color8]
[color9] [color10] [color11] [color12] [color13] [color14] [color15] [CHASE]
The functionality I get with the RasPi/Rasbian/QLC 4.11.0 GIT is amazing. In the SOLO frame, if I activate a RED scene, then activate the COLOR CHASE function, not only does it work, as I expected it to, but the corresponding color scenes activate the feedback channel for each scene button assigned to the "active scene" function running within the active "chase function". This allows the COLOR CHASE function to feedback to the LaunchPAD button that it is assigned to, and also shows me which color scene is currently active in step with the chaser.
How can I achieve this functionality with a "Normal" QLC+ distro without having to make duplicates of EVERY color scene I create? The problems would compound if I ever need to make a small change to ONE scene. Now I am forced to make these modifications to the duplicate scene. I have been trying a number of methods using Scripts, but to no avail.
Does anyone see the logic behind my setup, or, have any suggestion to achieve a similar result?
See the attached QWX file.
Thank you to user chasersync. I read the post. It appears that Massimo changed the way SOLO frames work. The option to have a Chase within a SOLO frame to run functions ALSO within the same Solo Frame was a major feature as it automated a number of functions. However I want to reopen discussion on this topic. I am having a hard time imagining that no other user has wanted to design a workspace like this. It would appear that the only way to regain my ability to run my workspaces as designed, is to revert to a pre-4.11.x revision of QLC+.
I have worked up a different way to explain this.
Imagine a situation in which you have 10 functions: 8 Scenes and 2 chasers. You have a MIDI devices that has 5 MIDI buttons that send NOTE ON messages.
In QLC+, you create a SOLO frame, with 2 pages.
On page 1, you create 4 buttons for "SOLID" color scenes, and a button for a chase containing these 4 SOLID scenes. Assign each of the widgets to an individual MIDI control.
On Page 2, you create 4 buttons for "SPLIT" color scenes, and a button for a chase containing these 4 SPLIT scenes. Again, using the same 5 MIDI triggers, assign each of the widgets to an individual MIDI control.
SOLID - scenes where all fixtures are set to a single color (ex. all back LED Pars are RED)
SPLIT - scenes where some fixtures are set to a single color, and others are set to a different color (ex. All ODD back LED Pars are RED, and all EVEN pars are GREEN)
In this situation, we will assume the Scenes are assigned to MIDI buttons 1-4, and the Chases to MIDI button 5. Seeing as you only have 5 MIDI triggers, you want to be able to control all the scenes visible in the active frame, regardless of which "mode" your SOLO frame is in.
Page 1, would be considered SOLID "mode" as it contains ONLY SOLID scenes, whereas Page 2 would be considered SPLIT "mode" as it contains ONLY SPLIT scenes.
Scenarios
1.) Imagine a scenario in which you activate the RED scene on Page 1, but then want to activate the GREEN scene on Page 1. SOLO Frame will allow RED to deactivate when you activate GREEN.
2.) Imagine a scenario in which you activate the RED scene on Page 1, then want to activate the RED GREEN scene on Page 2. SOLO Frame will allow RED to deactivate on Page 1 when you activate RED GREEN on Page 2.
3.) Imagine a scenario in which you activate the RED scene on Page 1, but then want to activate the SOLID COLOR CHASE on Page 1 to run. The Chaser, which steps through these 4 scenes on Page 1 in order, would activate. You would want the previously selected scene (RED) to deactivate, and the SOLID COLOR CHASE to start.
4.) Imagine a scenario in which you activate the RED scene on Page 1, but then want to activate the SPLIT COLOR CHASE on Page 2 to run. The Chaser, which steps through these 4 scenes on Page 2 in order, would activate. You would want the previously selected scene (RED) to deactivate, and the SPLIT COLOR CHASE to start.
Scenarios 1 & 2 are basic, and function as they are design on all platforms.
Scenarios 3 & 4, while running on QLC+ 4.11.0 GIT, on Rasbian OS Jessie on RasPi, this situation works as described.
Scenarios 3 & 4, while running on QLC+ 4.x.x on all other OSes, this situation doesn't work at all. The SOLID COLOR CHASER activates (Activates RED scene in SOLO frame, deactivates SOLID COLOR CHASE), then ends.
So, REAL WORLD.
I have a Novation LaunchPAD. I want to utilize 2 rows of buttons for colors. I can use 2 pages (One for SOLID, One for SPLIT). I want to use 15 of the 16 buttons for color-scene functions for each page and the last for the corresponding Chase function.
15 "X" Colors, and 1 Chase
[color1] [color2] [color3] [color4] [color5] [color6] [color7] [color8]
[color9] [color10] [color11] [color12] [color13] [color14] [color15] [CHASE]
The functionality I get with the RasPi/Rasbian/QLC 4.11.0 GIT is amazing. In the SOLO frame, if I activate a RED scene, then activate the COLOR CHASE function, not only does it work, as I expected it to, but the corresponding color scenes activate the feedback channel for each scene button assigned to the "active scene" function running within the active "chase function". This allows the COLOR CHASE function to feedback to the LaunchPAD button that it is assigned to, and also shows me which color scene is currently active in step with the chaser.
How can I achieve this functionality with a "Normal" QLC+ distro without having to make duplicates of EVERY color scene I create? The problems would compound if I ever need to make a small change to ONE scene. Now I am forced to make these modifications to the duplicate scene. I have been trying a number of methods using Scripts, but to no avail.
Does anyone see the logic behind my setup, or, have any suggestion to achieve a similar result?
See the attached QWX file.
- Attachments
-
chase in a solo frame.qxw- (15.32 KiB) Downloaded 151 times
-
tavonmarkov
- Posts: 35
- Joined: Sun Apr 12, 2015 6:33 pm
- Real Name: Tavon Markov
Is there ANY way to modify the source code to revert the Solo Frame code back to the pre-4.11.x behavior? The 4.10.5b version has the weird multi-page Widget edit bug. I am okay with using an older version of QLC+, but this Widget Bug makes editing quite frustrating.
Thanks!
Thanks!
-
chasersync
- Posts: 13
- Joined: Sun Aug 20, 2017 1:09 am
- Real Name:
Trying to get a similar result:
I modified the demo workspace.
1 I added a new chaser and called it 1
2 I added the scene 1 to the chaser.
3 I linked the chaser "1" to the VC-button where 1 was bound to.
4. same for all other scenes that were previously used in a solo frame
Like this a changed scene is applied to SOLID color and SOLID COLOR CHASER.
I modified the demo workspace.
1 I added a new chaser and called it 1
2 I added the scene 1 to the chaser.
3 I linked the chaser "1" to the VC-button where 1 was bound to.
4. same for all other scenes that were previously used in a solo frame
Like this a changed scene is applied to SOLID color and SOLID COLOR CHASER.
- Attachments
-
- modified__chase in a solo frame.qxw
- (17.85 KiB) Downloaded 105 times
-
tavonmarkov
- Posts: 35
- Joined: Sun Apr 12, 2015 6:33 pm
- Real Name: Tavon Markov
Thank you for your efforts. This edit "works". And it solves the scene editing problem. However, with my MIDI controller, it would never show the running scene in step with the chaser, as it does on my 4.11.0 GIT build on the RasPi - which, while you might not see the value of it, this function really is a nice ability. My only solution, for now, is to back-date the QLC version to 4.10.5b and run it that way. Does anyone know how the Solo Frame behavior code was changed? Is it at all possible for someone to let me know how that was changed so I can make the adjustment and recompile the newest QLC 4.12 to run like it used to? 4.10.5b has that MultiPage editing bug that really stinks. Or is there a fix to QT that fixes this bug on 4.10.5b - I saw something about this but I was not willing to try it last night.