I'm having trouble making a simple scene. Here's what I do in a new project:
Add fixtures, American DJ Mega Tri Par and Chauvet Colorstrip Mini
Add Scene "red", Mega Par channels to red and colorstrip mini to red
Toggle scene on/off, the Mega will turn on/off, the Strip stays on, values do not change in Simple Desk.
I've checked the "Can Fade" and the channels are selected. Thanks for any help!
Fixtures stay on despite of scene
-
Jano Svitok
Do you use the bundled color strip definition or have you made your own?
In the bundled definition some of the channels use LTP and what you see is direct consequence of that
Go to where you set "Can Fade" and change channels all channels to HTP. This will make it work in RGB mode, but may cause problems in the other modes.
In the bundled definition some of the channels use LTP and what you see is direct consequence of that
Go to where you set "Can Fade" and change channels all channels to HTP. This will make it work in RGB mode, but may cause problems in the other modes.
-
jef m
Hi Jano and thanks for writing.
I am writing my own. The behavior does seem like the HTP/LTP swap you mention, but changing it does not seem to matter. Kind of confusing. I'm trying to write the definition for a Chauvet Radius which is how I'm noticing it. The ADJ Mega Pars I have in the same universe have no problem.
Here is what I'm noticing:
Open QLC, New workspace
Add Generic Dimmer, 1 Channel
Add Red function, Add fixture Dimmer to it, set slider to red (like, 15)
Toggle function on/off, red light on/off, no problem. Behavior is HTP
Good enough, so
Open QLC, New workspace
Add Radius 2.0, three channel definition I'm writing
All channels are LTP? Oh no, I change them to HTP, ok and verify.
Add Red function, Add Radius to it, set slider red (like, 15)
Toggle function on/off, red light stays on. Behavior is HTP. Simple desk shows Radius channel is still in position set by Red scene. Zero out, light turns off, reset universe.
Hm maybe if I quit and restart.
Save as 'Save Test' close QLC
Open QLC, open 'Save Test'
Verify Radius Behavior is all HTP still, it is.
Toggle Red function, light stays red. Simple desk shows Radius channel is still in position set by Red scene. Zero out, light turns off, reset universe.
I cannot figure it out, thanks for any help! I'm also attaching the saved workspace and will upload the definition I'm writing.
I am writing my own. The behavior does seem like the HTP/LTP swap you mention, but changing it does not seem to matter. Kind of confusing. I'm trying to write the definition for a Chauvet Radius which is how I'm noticing it. The ADJ Mega Pars I have in the same universe have no problem.
Here is what I'm noticing:
Open QLC, New workspace
Add Generic Dimmer, 1 Channel
Add Red function, Add fixture Dimmer to it, set slider to red (like, 15)
Toggle function on/off, red light on/off, no problem. Behavior is HTP
Good enough, so
Open QLC, New workspace
Add Radius 2.0, three channel definition I'm writing
All channels are LTP? Oh no, I change them to HTP, ok and verify.
Add Red function, Add Radius to it, set slider red (like, 15)
Toggle function on/off, red light stays on. Behavior is HTP. Simple desk shows Radius channel is still in position set by Red scene. Zero out, light turns off, reset universe.
Hm maybe if I quit and restart.
Save as 'Save Test' close QLC
Open QLC, open 'Save Test'
Verify Radius Behavior is all HTP still, it is.
Toggle Red function, light stays red. Simple desk shows Radius channel is still in position set by Red scene. Zero out, light turns off, reset universe.
I cannot figure it out, thanks for any help! I'm also attaching the saved workspace and will upload the definition I'm writing.
- Attachments
-
save%20test.qxw- (1.94 KiB) Downloaded 254 times
-
jef m
Here's the radius def, mostly done
- Attachments
-
- Chauvet-Radius-2.0.qxf
- (1.82 KiB) Downloaded 234 times
-
Jano Svitok
Hi, the problem is that HTP/LTP override mechanism is not properly implemented.
I will fix it when I find some time... In the meatime, the easiest workaround is to change the fixture definition to use Intensity group for channel 1.
Note for me/other developers: GenericFader should not use FadeChannel::group() but rather Fixture::forcedHTPChannels(), Fixture::forcedLTPChannels() and/or Universe::channelCapabilities() & HTP.
I will fix it when I find some time... In the meatime, the easiest workaround is to change the fixture definition to use Intensity group for channel 1.
Note for me/other developers: GenericFader should not use FadeChannel::group() but rather Fixture::forcedHTPChannels(), Fixture::forcedLTPChannels() and/or Universe::channelCapabilities() & HTP.
-
jef m
Hello Jano,
I changed my definiton to intensity for channel 1/color and that did the trick. Thank you, I thought I was loosing my mind, as it seemed every definition I wrote (an some builtins) was broken.
If somebody can post here when this is fixed, I would love it, I'm going to fix my defintions but it would be better to have them on Color, because the click-n-pick looks cool :}
I changed my definiton to intensity for channel 1/color and that did the trick. Thank you, I thought I was loosing my mind, as it seemed every definition I wrote (an some builtins) was broken.
If somebody can post here when this is fixed, I would love it, I'm going to fix my defintions but it would be better to have them on Color, because the click-n-pick looks cool :}
-
NiKoyes
We have also a problem here, seems to come from HTP/LTP, but that arrived after a week working on a new project, still on 4.7.2 :
At first quite everything was fine, working with cuelists (ie chasers).
1. But after a few days, lights won't get back to zero, everything kept displayed with the highest dmx values ; and these values, after killing all functions, stay in the simple desk (that we don't use). I have to set everything to zero moving the simple desk faders manually and reset the universe.
but now the lights won't act like before, the values never gets back to zero...
(fixtures incriminated are chauvet led strobe, and showtec spectral cyc 650 in mode pixel, i have 2 generic dimmers and they don't face the problem)
2. We set the fixtures in LTP to try if there was a difference. it works better, even if it is LTP and we are working with color dimmers so we had to program things a different way but :
some chasers with ltp color dimmers have a very small black between steps instead so the chase twinles an ugly way
(see chase named "vumetre 123" in my file)
3. Setting the dimmers to LTP ables us to work despite of the bug, but restarting QLC+ gets all the dimmers back to HTP... and is not a valuable solution because they are dimmers and they shouldn't act like that, the weird thing is that it appears after a few days, first there was nothing strange. is our file too big ? to much functions in it ?
I send you the file, there are many thing, you can try with the chases in the folder "__SET VOSTFR" these are our cuelists, you will see everything stays even when getting back to black.
I even wonder why i appear to be alone having such a bug because there is nothing i can do now. Is it because i changed once between htp and ltp ? it seem to appear before in fact...
Hope someone finds somthing
At first quite everything was fine, working with cuelists (ie chasers).
1. But after a few days, lights won't get back to zero, everything kept displayed with the highest dmx values ; and these values, after killing all functions, stay in the simple desk (that we don't use). I have to set everything to zero moving the simple desk faders manually and reset the universe.
but now the lights won't act like before, the values never gets back to zero...
(fixtures incriminated are chauvet led strobe, and showtec spectral cyc 650 in mode pixel, i have 2 generic dimmers and they don't face the problem)
2. We set the fixtures in LTP to try if there was a difference. it works better, even if it is LTP and we are working with color dimmers so we had to program things a different way but :
some chasers with ltp color dimmers have a very small black between steps instead so the chase twinles an ugly way
(see chase named "vumetre 123" in my file)
3. Setting the dimmers to LTP ables us to work despite of the bug, but restarting QLC+ gets all the dimmers back to HTP... and is not a valuable solution because they are dimmers and they shouldn't act like that, the weird thing is that it appears after a few days, first there was nothing strange. is our file too big ? to much functions in it ?
I send you the file, there are many thing, you can try with the chases in the folder "__SET VOSTFR" these are our cuelists, you will see everything stays even when getting back to black.
I even wonder why i appear to be alone having such a bug because there is nothing i can do now. Is it because i changed once between htp and ltp ? it seem to appear before in fact...
Hope someone finds somthing
- Attachments
-
- Janski%20VOSTFR%20%5B2014%5D.qxw
- (106.54 KiB) Downloaded 195 times
-
NiKoyes
News :
The bug is resolved by deleting the fixtures in the fixture panel, re-adding them and reprogramming all the scenes which became empty...
Is that a good news ?
The bug is resolved by deleting the fixtures in the fixture panel, re-adding them and reprogramming all the scenes which became empty...
Is that a good news ?
-
jef m
Hi all,
I'm noticing this behavior still exists so I'm rewriting a lot of fixtures to have all intensity channels.
I was wondering if by setting everything to intensity/htp, if I'm heading into a problem? My universe might have over twenty fixtures and four moving heads.
I'm noticing this behavior still exists so I'm rewriting a lot of fixtures to have all intensity channels.
I was wondering if by setting everything to intensity/htp, if I'm heading into a problem? My universe might have over twenty fixtures and four moving heads.
-
jef m
I have two Chauvet Intimidator 250's and was excited that the definition was in QLC+ already. Loaded it up but had the same problem with scenes not resetting.
So I wrote a quick Intimidator definition with all channels as Intensity, change one of the lights to my definition, it would work while the other light hung up in the same scenes.
So I assign my def to both lights and they both work in the same scenes.
How do people write the definitions with this problem in the software? Does this happen to other people, do you change all the channels to Intensity like I'm doing?
So I wrote a quick Intimidator definition with all channels as Intensity, change one of the lights to my definition, it would work while the other light hung up in the same scenes.
So I assign my def to both lights and they both work in the same scenes.
How do people write the definitions with this problem in the software? Does this happen to other people, do you change all the channels to Intensity like I'm doing?