LED PAR Fade out works - Fade in doesn't

[arizonajill]

I'm new to QLC and have been trying to find a solution to a probable newbie problem.

I've set up a SCENE called ALL PAR RED FADE. I've set the SPEED DIAL WINDOW to 2s FADE IN and 3s FADE OUT.

Fade out works great, but fade in doesn't seem to work at all. When I click the button I created in VIRTUAL CONSOLE the fixture turns on without fading in. When I click the button again it fades out like I meant it to.

I'm sure I'm doing something wrong. I've attached my workspace file.

Any help would be greatly appreciated!

[edogawa]

Interestingly it works just fine for me here,,,
I'm on openSUSE Tumbleweed, using 4.12.8-git which currently is the same as 4.12.7 stable.

[GGGss]

4.12.7 on windows: no issues with the All Red (blue green) fade scenes...

[MichelSliepenbeek]

Instead of creating specific scenes with Fade times, it's easier to use a Speed Dial.

If you want to read the on-line help: https://www.qlcplus.org/docs/html_en_EN ... ddial.html

It is important to know that you can use "as many as you want" speed dials, so you can:
- use a specific speed dial for your PARS and onther one for your Moving Heads.
- use a Speed Dial to control the RGB channels of your Moving head and another one for position changes (Pan and Tilt) of your heads.
- use separate speed dials for Duration (set Fade in and Fade Out to "not sent") and Fade (now set Duration to "Not sent").

To get you started:
create a Speed Dial on your Virtual Console.
select the functions you want it to control (e.g. All Fixtures Blue, All Fixtures Green and All Fixtures Red), set fade in/Fade out to 1 and duration to Not Sent.
create some Presets.
and on the Appearance Tab unbox everything you don't want to see.

Try This:

JillyWorkspace with Speed Dial.qxw

(74.64 KiB) Downloaded 155 times

[arizonajill]

Thanks MichelSliepenbeek! I'll check it out!

[arizonajill]

MichelSliepenbeek . . . I still have the same issue, however I've determined that my spider (Moving Head) lights fade in and out just fine. I only have a problem with the PAR lights fading in. (they fade out ok)

I think I've gotten something wrong in the device config for the PAR lights or I've made some other blunder concerning those particular lights. I'll look at that...

Again THANKS!

[arizonajill]

I'm having no luck. If anyone has the bandwidth, maybe they can compare the specs to the fixture definition and tell me what I'm doing wrong,

I've attached a picture of the fixture's spec sheet that came with it that I used to set up the fixture in the fixture editor and I'm attaching a copy of the fixture definition file.

Specs for the PAR Light in question

Hopefully, I attached the files correctly.

[edogawa]

Do NOT fill in the "Acts On" column in Mode editor unless you know why!

This is stated in the documentation and has been raised several times here in the forum.

I think you also should remove all the aliases, they're not needed for your fixture.

The DMX table tells that channel 7 controls color selection, speed of color changes or pulsing, depending on the level setting of channel 6. But it always acts as one parameter across full range. Aliases are there to swap one channel depending on the value of another one. While in your case, no matter what level channel 6 is at, channel 7 always acts from 0 - 255 continuously. I wouldn't go for that added complexity just to display the correct icon in simpledesk etc. for channel 7.

[MichelSliepenbeek]

I found the same issues and corrected the Fixture definitions:

UKing-Par-Light-B262.qxf

(2.08 KiB) Downloaded 187 times

BeTopper-Mini-Spider-LM30A.qxf

(3.44 KiB) Downloaded 159 times

In order to solve Jilly's earlier problem i even created seperate modes on the LM30A for RGBW and WBGR .


There is however another problem at hand: if you use Jilly's workspace (with those Fixture Definitions) and you use the Fixture Monitor in 2D mode, it will let you add the LM30A's but you cannot add the PAR's.
Somehow on the selection screen it shows as if they already have been selected.

If i add another UKing B262 fixture (e.g as PAR5 on DMX channel 100), i can add that one to the DMX Monitor just like that and it works fine.
This tells me that the problem is not in the Fixture Definition.

I also noticed that for PAR1 - PAR4 there were channel modifiers defined. If i remove them you still cannot add the pars to DMX Monitor.
I also removed all the Channel Groups: no difference.


Something in the Workspace is "corrupted", but i cannot find it.

[MichelSliepenbeek]

My feeling was correct: i checked the Workfile in Notepad and in the <Monitor> section there were 8 fixtures, so the PAR's were already selected (but for some reason did not show).
I removed the 4 lines for those PAR's, saved the file, restarted QLC and now i was able to add the PAR's to the Monitor, they showed up and ....... the Fade In and Fade OUT both worked.

Jilly should put the following fixture definitions in her QLC User Lib (C:\users\"your Name"\QLC+\Fixtures)

UKing-Par-Light-B262.qxf

(2.08 KiB) Downloaded 145 times

BeTopper-Mini-Spider-LM30A.qxf

(3.44 KiB) Downloaded 170 times

And then use this Workspace:

JillyWorkspace Fixed.qxw

(71.61 KiB) Downloaded 188 times

[arizonajill]

MichelSliepenbeek. I'm Jilly... and still learning. I appreciate your help soooo much.

I added the two fixture definitions to the C:\Jilly\QLC+\Fixtures folder. I removed my old fixture definitions from the C:\Jilly\QLC+\Fixtures folder. And launched the workspace file that you provided.

So, it looks like all the fixtures are pointing to the new fixture definitions which is what we want. However, when trying to fade in, I ran into the same problem.

The GOOD news is, if I add a NEW fixture using the definitions you sent it works! Fades in and Out like a charm! Yay!

I must have really messed things up and suspect that I corrupted something, but you've saved the day! I'm going to try and figure out a way to get the fixtures to work without having to recreate all the scenes.

(The way it is now, if I remove a fixture on the fixtures tab and re-add it, it gets removed from scenes and I have to re-do them)

But if I do have to re-do them, at least you've gotten me to where I need to be!
Again, thank you for taking the time to work on this. You're the bomb!

Jilly

[arizonajill]

FYI, UPDATE: After restarting everything is working like it should! Maybe something in memory needed to get cleared out, but everything is GREAT now!

[arizonajill]

Thanks to all that replied in this thread. I really appreciate all of you trying to help me.