I have defined a few fixture definition files (and submitted a few) but I would like to clear up a situation I am unsure of
I have a channel defined like this in the fixture manual...
0-7 OFF
8-134 Master Dimmer low to high
135-239 Strobe from slow to fast
240-255 Open
What is the recommended way to define this channel in the definition editor for use with QLCPlus 4 and 5?
Here is one approach but is this ok for the master dimmer function to work correctly?
Using the Fixture Definition Editor 4.12.2
I have defined the channel as follows
Channel Name: Shutter/Dimmer/Strobe
Channel Preset: Custom
Channel Type: Effect
Default value: 0
Role: Coarse
Minimum value: 000 - Maximum value: 007 - Description: Off - Capability Preset: ShutterClose
Minimum value: 008 - Maximum value: 134 - Description: Master Dimmer - Capability Preset: Custom
Minimum value: 135 - Maximum value: 239 - Description: Strobe from slow to fast - Capability Preset: StrobeSlowToFast
Minimum value: 240 - Maximum value: 255 - Description: Open - Capability Preset: ShutterOpen
any problems with that?
Defining a channel with Master Intensity and Strobe
- GGGss
- Posts: 3052
- Joined: Mon Sep 12, 2016 7:15 pm
- Location: Belgium
- Real Name: Fredje Gallon
I don't like these kind of fixtures because you won't be able to control its intensity by the Grand Master...
So your choise to use a shutter or efx is correct. (It you would choose intensity - it will be influenced by GM and other intensity efx which will be a surprising mess going on... GM dimming will have them flash and strobe then when @60% full brightness up to 10% or so and darkness) <- unwanted behaviour
Downside is again that this channel will not be effected by intensity EFX - which is a pity because you can't use the full strenght of QLC+
If you someway manage to create a virtual copy of the intensity channels limited to only workable values - that would help you... topics here: loopback channels, channel modifiers.
Or you look if there is an other mode that can be selected...
Break a leg
So your choise to use a shutter or efx is correct. (It you would choose intensity - it will be influenced by GM and other intensity efx which will be a surprising mess going on... GM dimming will have them flash and strobe then when @60% full brightness up to 10% or so and darkness) <- unwanted behaviour
Downside is again that this channel will not be effected by intensity EFX - which is a pity because you can't use the full strenght of QLC+
If you someway manage to create a virtual copy of the intensity channels limited to only workable values - that would help you... topics here: loopback channels, channel modifiers.
Or you look if there is an other mode that can be selected...
Break a leg
All electric machines work on smoke... when the smoke escapes... they don't work anymore
-
- Posts: 5
- Joined: Fri Oct 05, 2018 7:01 am
- Real Name: Michael
I don't like channel definitions like this either. For light shows it is so important to be able to run independent sequences such as colour changes and others of intensity changes and others of movement. For new readers avoid buying fixtures like this but there are many out there and several in the qlcplus fixture library. As you suggested GGGss making the intensity range (of 8 to 134) available for efx, gm and just general intensity chasers is probably going to get the best out fixtures like this. My view would be to sacrifice the strobe functions and find a way to just use the valid intensity range. (maybe include the 7 value so that 7 to 134 includes the master intensity at zero.
I have to admit I have often bought a fixture without checking out the dmx chart so you will not be the first if you are reading this after realising that it applies to you!
I'm not familiar with the topics you mention GGGss: loopback channels, channel modifiers but I'm certainly going to try them if I can find the qlcplus info. (any link?) To get the best out of qlcplus 5 preview it is also necessary for the gui intensity control (and other stuff) to work so if there is a way to adjust the configs in the fixture definition library so that they can be used (and visualised), with intensity chases after all, I will track down a few if I can. (strobe of no importance by comparison so junk it!) I have a fixture I can use as a test case.
Without doing that you are right about the flashing of the real fixture that results. I have seen it happen in qlcplus 5, hence this discussion. If other readers have a fixture with this problem maybe we can compare tentative config solutions before we think about updating (or even suggesting it) any definitions. Checking the preview is good will not be enough to check this out properly so bear that in mind if you have done that and imagine there is no problem.
I have to admit I have often bought a fixture without checking out the dmx chart so you will not be the first if you are reading this after realising that it applies to you!
I'm not familiar with the topics you mention GGGss: loopback channels, channel modifiers but I'm certainly going to try them if I can find the qlcplus info. (any link?) To get the best out of qlcplus 5 preview it is also necessary for the gui intensity control (and other stuff) to work so if there is a way to adjust the configs in the fixture definition library so that they can be used (and visualised), with intensity chases after all, I will track down a few if I can. (strobe of no importance by comparison so junk it!) I have a fixture I can use as a test case.
Without doing that you are right about the flashing of the real fixture that results. I have seen it happen in qlcplus 5, hence this discussion. If other readers have a fixture with this problem maybe we can compare tentative config solutions before we think about updating (or even suggesting it) any definitions. Checking the preview is good will not be enough to check this out properly so bear that in mind if you have done that and imagine there is no problem.
-
- Posts: 5
- Joined: Fri Oct 05, 2018 7:01 am
- Real Name: Michael
Using the Channel Modifier:
https://www.qlcplus.org/docs/html_en_EN ... rties.html
As I understand it, this feature can be used to avoid QLCplus sending a strobe value to the channel by mapping all the x values to y intensity values. To do this the feature definition for the channel should be set to intensity (which is always full scale).
Does this allow the efx feature to work correctly? I think it does, but not tried it yet. I think that will also allow the qlcplus 5 visualisation to show intensity variations in any chase etc.
I note that the info in the link explains that the GM is after this mapping is applied, so I think that means that the intensity pop-up in the qlcplus 5 visualisation could start the strobe occuring in the channel example given earlier for this topic. Since this is less important than a visualisation of a programmed show I think this will be very useful even if the gui control is not used. Is this a sensible approach?
I'll try that out and report my results.
https://www.qlcplus.org/docs/html_en_EN ... rties.html
As I understand it, this feature can be used to avoid QLCplus sending a strobe value to the channel by mapping all the x values to y intensity values. To do this the feature definition for the channel should be set to intensity (which is always full scale).
Does this allow the efx feature to work correctly? I think it does, but not tried it yet. I think that will also allow the qlcplus 5 visualisation to show intensity variations in any chase etc.
I note that the info in the link explains that the GM is after this mapping is applied, so I think that means that the intensity pop-up in the qlcplus 5 visualisation could start the strobe occuring in the channel example given earlier for this topic. Since this is less important than a visualisation of a programmed show I think this will be very useful even if the gui control is not used. Is this a sensible approach?
I'll try that out and report my results.
-
- Posts: 3
- Joined: Sat Sep 24, 2022 8:56 am
- Real Name: Stu B
Hi, jumping on this topic as I have a similar question (please let me know if this should be a fresh topic).
I have 8x LED lamps with 4 channels:
CH1:
0=off
1-127=Dimmer
127-255=Flash
CH2,3,4=R, G, B
I have created the fixture and it works, but putting the Dimmer control into a Channel Group doesn't work because the values above 127 cause it to flash.
I looked into Aliases (to create a kind of virtual channel with the appropriate values), but the "+" button in the Aliases tab is greyed out.
Is there a workable solution?
Thanks so much - this is all new to me and I love the program!
I have 8x LED lamps with 4 channels:
CH1:
0=off
1-127=Dimmer
127-255=Flash
CH2,3,4=R, G, B
I have created the fixture and it works, but putting the Dimmer control into a Channel Group doesn't work because the values above 127 cause it to flash.
I looked into Aliases (to create a kind of virtual channel with the appropriate values), but the "+" button in the Aliases tab is greyed out.
Is there a workable solution?
Thanks so much - this is all new to me and I love the program!
-
- Posts: 3
- Joined: Sat Sep 24, 2022 8:56 am
- Real Name: Stu B
Update 1: I figured out why the Aliases button was greyed out. I still don't quite understand Aliases, but I'll have to study more in the future.
Update 2: To at least give me a smooth and consistent fade, I created a Configuration Template with a threshold of 127, so that any value above 127 is limited to 127. It means I can't access the Flash values, but if I need them to flash I can do it via QLC+, right??
Update 2: To at least give me a smooth and consistent fade, I created a Configuration Template with a threshold of 127, so that any value above 127 is limited to 127. It means I can't access the Flash values, but if I need them to flash I can do it via QLC+, right??
- GGGss
- Posts: 3052
- Joined: Mon Sep 12, 2016 7:15 pm
- Location: Belgium
- Real Name: Fredje Gallon
Please try to use the correct terminology: it's called "Channels-fade-configuration" aka dimmer-curve.
You can get a consistent fade if you create a scene with intensity 127 and have this one fade in (-out). I don't get your problem here... Doing this with channel groups won't be possible, but don't use channel groups for everything... don't be lazyMidlifeCrisisStu wrote: ↑Sun Oct 02, 2022 1:21 pm Update 2: To at least give me a smooth and consistent fade,
untrue. A dimmer-curve is the last soldier in line. Whatever value you let QLC+ produce, it will follow the dimmer-curve. 127 in the curve is the absolute maximum. So no - with your particular fixture you cannot use the strobe function. (But again: you can create a fast on-off chaser and now you have a strobe.)MidlifeCrisisStu wrote: ↑Sun Oct 02, 2022 1:21 pm limited to 127. It means I can't access the Flash values, but if I need them to flash I can do it via QLC+, right??
All electric machines work on smoke... when the smoke escapes... they don't work anymore
-
- Posts: 3
- Joined: Sat Sep 24, 2022 8:56 am
- Real Name: Stu B
Clear, thanks for the reminder.
You are right - I am the infancy of my DMX control journey, and I was testing the lights by using the Simple Desk. Now I have set the Channel Fade Configuration, I will of course be using the Fade In/Out anyway.
I'm not sure what this means? I'm guessing you mean that in the processing chain, all values are calculated by QLC+ and then at the last moment the dimmer-curve steps in to adjust the final values sent via DMX?
Yes, thanks - you are confirming what I thought I can't use the inbuild flash setting on the lamp, but I can recreate the effect (with better control anyway) through QLC+.
Thankyou so much for your help!