Hi,
I'm just evaluatiing QLC+ V4.13.1 and I'm really impressed!
This is really a great kind of work.
To start my tests I have created a small setup with 8 RGB spots and I'm able to see my changes in the DMX Channel Monitor and at my physically connected spots (via an ENTTEC DMX USB PRO interface).
In my next step I created some scenes to make the handling a bit easier..
In my first scene I send an init condition to my spots and all channel values are set as expected:
https://photos.app.goo.gl/YiiX62TVAEE7cwVR6 NEW LINK - hopefully it should be visible now ...
As you can see, all channel values specified in the scene were sent to the spots and are shown in the DMX Channel Monitor.
In my next scene, I tried the change only the color values of my spots.
Therefore I only enabled the RGB channels.
After calling the scene the RGB values are set correct BUT my "channel 7" information is overritten - even "channel 7" is disabled in the scene:
https://photos.app.goo.gl/uijM57TeGsWfn5e46 NEW LINK
In my third scene I tried to set the brightness of all spots to 100%, so that my changes get visible.
Therefor I only enabled channel 1 of each spot in the next scene.
After calling the scene all brightness parameters are set correct BUT my RGB channels are all set back to 0 - even the RGB channels are disabled in my scene.
https://photos.app.goo.gl/KmxVnJvQYfvX3Xei7 NEW LINK
What do I make wrong?
Can anybody help me?
Kind regards
garysn
Weird behaviour of the "channel enable/disable" functionality in the scene editor ...
-
GGGss
- Posts: 3052
- Joined: Mon Sep 12, 2016 7:15 pm
- Location: Belgium
- Real Name: Fredje Gallon
Welcome to the community,
Your photos all result in a 404 not found.
The best practice is to handle values layer by layer. What you are doing is correct.
Now first, we will have to see if your fixture definition is set correctly. Intensity channels should be HTP. All the others should be LTP. (Unless you have a special use to deviate from the standard.)
By calling the scenes, do you activate them all together or one by one?
Can we also have a look at your project file?
Your photos all result in a 404 not found.
The best practice is to handle values layer by layer. What you are doing is correct.
Now first, we will have to see if your fixture definition is set correctly. Intensity channels should be HTP. All the others should be LTP. (Unless you have a special use to deviate from the standard.)
By calling the scenes, do you activate them all together or one by one?
Can we also have a look at your project file?
All electric machines work on smoke... when the smoke escapes... they don't work anymore
-
garysn
- Posts: 5
- Joined: Fri Jul 12, 2024 8:36 pm
- Real Name: Gerhard
So, here is the project description and all files:
Our Drummer has a Click Track, that is played by a software called GigPerformer.
This software allows us to add Marker at any position inside the .WAV Files.
When the .WAV file is played and a marker position is passed, a MIDI event is sent to QLC+ which triggers a button.
Each button is connected with a scene or collection.
So far, so good.
To avoid "brute force" writing I created a bunch of scenes that allows me to adjust all aspects of my intended "show"
I use 2 rows with 4 RGB spots each and so I have build e.g. a scene for setting the brigness of "Row 1" (SPOT 1,2,3,4) to 50%, or changing the color of "Col 2" (SPOT 2 & 6) to orange.
As long as I write all 7 channel parameters of a spot at the same time all works fine.
When I'm trying to write only a few channels, the other "inactive" channels seems to be written too, even if they are "diabled".
Atteched you will find:
- my fixture definition file
- my input profile file
- and my project file with a small sample.
If you click the virtual console buttons "1-23" to "1-31" you will see the intended result in the DMX channel monitor.
The connected scenes are always write all channel information of each spot.
When trying to do it in a "layered way" please click the buttons "1-32" to "1-40".
In theory the same result should appeary, but in reality only button "1-32" works, the rest ends somehow in chaos.
I would be very thankful for any help or ideas to solve this problem.
Kind regards
garysn
Our Drummer has a Click Track, that is played by a software called GigPerformer.
This software allows us to add Marker at any position inside the .WAV Files.
When the .WAV file is played and a marker position is passed, a MIDI event is sent to QLC+ which triggers a button.
Each button is connected with a scene or collection.
So far, so good.
To avoid "brute force" writing I created a bunch of scenes that allows me to adjust all aspects of my intended "show"
I use 2 rows with 4 RGB spots each and so I have build e.g. a scene for setting the brigness of "Row 1" (SPOT 1,2,3,4) to 50%, or changing the color of "Col 2" (SPOT 2 & 6) to orange.
As long as I write all 7 channel parameters of a spot at the same time all works fine.
When I'm trying to write only a few channels, the other "inactive" channels seems to be written too, even if they are "diabled".
Atteched you will find:
- my fixture definition file
- my input profile file
- and my project file with a small sample.
If you click the virtual console buttons "1-23" to "1-31" you will see the intended result in the DMX channel monitor.
The connected scenes are always write all channel information of each spot.
When trying to do it in a "layered way" please click the buttons "1-32" to "1-40".
In theory the same result should appeary, but in reality only button "1-32" works, the rest ends somehow in chaos.
I would be very thankful for any help or ideas to solve this problem.
Kind regards
garysn
- Attachments
-
The Old Office.qxw- (131.2 KiB) Downloaded 39 times
-
- Deskew-GigPerformer.qxi
- (10.94 KiB) Downloaded 40 times
-
- Dongguan-Tong-Global-Industrial-Co.-Ltd-Stage-Light-ZQ01082.qxf
- (2.2 KiB) Downloaded 45 times
-
MichelSliepenbeek
- Posts: 718
- Joined: Wed Feb 08, 2023 10:24 am
- Location: Nederland
- Real Name: Michel Sliepenbeek
In the Scene Editor both channels 1 and 7 show up as Master Level. That might explain the weird behaviour you noticed.
Did you create the Fixture Definition yourself?
If you post the manual of your Fixture and the Fixture Definition, we can help you to correct it.
Did you create the Fixture Definition yourself?
If you post the manual of your Fixture and the Fixture Definition, we can help you to correct it.
A QLC Workspace is like a Bob Ross painting: "it's your world, you can create whatever you want!"
-
GGGss
- Posts: 3052
- Joined: Mon Sep 12, 2016 7:15 pm
- Location: Belgium
- Real Name: Fredje Gallon
I changed your fixture definition (someone else published it: viewtopic.php?t=17547—do you have 2 accounts now?).
1-16 .. 1-19 Click x chasers: They all have intensity settings, and some have color information. Was this intentional? It doesn't make sense to change intensity without setting the RGB values.
Your 'layered' cues are all inside a solo frame, so only one can be active at the time. Here, you lose your intensity values automatically.
I decided to change your project into a workable (?) example. With the midi controls in place, this might not work for you because of the HTP channels. If you call a brightness of 50% and at the same time a brightness of 75%, 75% will be sent. Now call the 75%, and then the 50% (at the same time) -> 75% will be kept and sent.
This is the default HTP behaviour. This explains why if you do your init (with a blue value of 100), the blue value stays even if you set a value of 0 in later called scenes.
If you want the latest called scene to be in control, you have to change your logic to LTP. This implies that all called values will stay put unless you deliberately reset them. This mode is the default for theatre. We record desired changes and follow the cue list.
1-16 .. 1-19 Click x chasers: They all have intensity settings, and some have color information. Was this intentional? It doesn't make sense to change intensity without setting the RGB values.
Your 'layered' cues are all inside a solo frame, so only one can be active at the time. Here, you lose your intensity values automatically.
I decided to change your project into a workable (?) example. With the midi controls in place, this might not work for you because of the HTP channels. If you call a brightness of 50% and at the same time a brightness of 75%, 75% will be sent. Now call the 75%, and then the 50% (at the same time) -> 75% will be kept and sent.
This is the default HTP behaviour. This explains why if you do your init (with a blue value of 100), the blue value stays even if you set a value of 0 in later called scenes.
If you want the latest called scene to be in control, you have to change your logic to LTP. This implies that all called values will stay put unless you deliberately reset them. This mode is the default for theatre. We record desired changes and follow the cue list.
- Attachments
-
- Dongguan-Tong-Global-Industrial-Co.-Ltd-Stage-Light-ZQ01082.qxf
- (2.2 KiB) Downloaded 55 times
-
- The Old Office.qxw
- (132.17 KiB) Downloaded 48 times
All electric machines work on smoke... when the smoke escapes... they don't work anymore
-
garysn
- Posts: 5
- Joined: Fri Jul 12, 2024 8:36 pm
- Real Name: Gerhard
Hi again,
thanks again for your support.
I'm really a newbie in lightning control and this is my first try - so I have to learn a lot and are really thankful for any help I can get.
Sometimes reading manuals is not enough to get a working result.
To your questions:
Yes I have created the fixture definition by my own, cause I could not find a matching definitiion in your database - and due to the fact that it's my first try I'm quite sure that there is not everything set in the right way.
No, of cause I have no second account (that's a no go !!!)
I will try your modifications and let you know how close they are to that that I would like to have ...
Kind regards
garysn
thanks again for your support.
I'm really a newbie in lightning control and this is my first try - so I have to learn a lot and are really thankful for any help I can get.
Sometimes reading manuals is not enough to get a working result.
To your questions:
Yes I have created the fixture definition by my own, cause I could not find a matching definitiion in your database - and due to the fact that it's my first try I'm quite sure that there is not everything set in the right way.
No, of cause I have no second account (that's a no go !!!)
I will try your modifications and let you know how close they are to that that I would like to have ...
Kind regards
garysn
