Light Definition - Virtual Intensity for RGB Fixture

[Peter Hodgkinson]

hi all,

I've tried searching for this on here and elsewhere online but not found anything so I might be using the wrong terminology. If I am using the wrong words please let me know so that I can locate any existing information :)

I am working in an environment for the next couple of weeks where we have a number of light fixtures that are:

Intensity
Red
Green
Blue

and some that are just

Red
Green
Blue

and then we also have some conventional dimmers that just have intensity.

Is it possible to create a virtual intensity channel for the RGB-only fixtures so that for things like a blackout we can do a single command of all.intensity=0 and know that we will get all the fixtures to go out, whilst preserving the colour that they were before?

Kindest Regards

Peter Hodgkinson

[wmac...@gmail.com]

Hello Peter,

Not sure if this is what you're asking but, in the patch window, if you click on 'new instrument', under 'generic' you will find a good selection of configurations, including 'RGB' and 'RGB with Intensity' (which allows you to adjust intensity without changing hue).

You can then put the instruments in 'groups' to control the intensity of that group.

Cheers,

William

[micpool]

Hi William

I think you may have misunderstood the difference between an RGB and an RGB with intensity fixture.

The Intensity is not a virtual channel. but a real channel requiring a DMX address for instruments that are designed with an intensity master for their RGB sources.

i.e an RGB luminaire will have 3 addressable parameters and an RGB with intensity luminaire will have 4 addressable parameters.

As far as I know there is not a way to do what Peter was asking.

I think It would be great if there was a 'one to many type' virtual parameter which was proportional, i.e it acted as a (one)  multiplier to  the (many) channels that are assigned to it. At present the one to many  virtual parameter just sets the many to the level of the one, so if applied to the RGB components of a fixture that only has RGB the result is always white, regardless of what the color was before the level of the  virtual parameter is set.

Mic

[William Mackwood]

Hello Mic,

I do understand the difference between RGB and RGB with intensity. However, I now understand what Peter was asking . . . must read more carefully. :) 

w

--
Contact support anytime: sup...@figure53.com
Follow QLab on Twitter: https://twitter.com/QLabApp
User Group Code of Conduct: https://qlab.app/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups "QLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qlab+uns...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qlab/09674004-42a9-4394-a984-9267c5824475n%40googlegroups.com.

[Sam Kusnetz]

Hello folks

There is a way to do this, although it might not be completely obvious at first blush.

Using QLab’s built-in definitions for RGB fixture (either 8-bit or 16-bit, doesn’t matter), select the light in the Dashboard and look at the color picker control on the right side.

You’ll see a colorful triangle, then four sliders below. Pick a color using the triangle, then drag the “%” slider down to proportionally fade all three colors.

Record these changes into cues, and presto, you effectively have a virtual intensity control.

Best
Sam

––
Sam Kusnetz [he/him/his] (what is this?)
Figure 53
https://qlab.app | https://figure53.com

To view this discussion on the web visit https://groups.google.com/d/msgid/qlab/njvbcu39k540hklu0o0d912n.1606684428315%40gmail.com.

[micpool]

Hi Sam,

Unless I'm missing something, the percent slider couldn't be defined as the default for the channel, in the same way as a one to many virtual parameter  named intensity could, so  it couldn't be used in a QLab lighting command ,which was what Peter wanted to do.

Mic

[Sam Kusnetz]

Mic

You’re not missing something. The exact behavior that Peter seeks is not possible, but the results are available if he’s willing to approach it slightly differently.

Best
Sam

––
Sam Kusnetz [he/him/his] (what is this?)
Figure 53
https://qlab.app | https://figure53.com

To view this discussion on the web visit https://groups.google.com/d/msgid/qlab/4f29c834-fb77-4348-9e13-4cd6133447d9n%40googlegroups.com.

[micpool]

So would a new virtual parameter like 'one multiplier to many' be a sensible feature request?. This master level of RGB fixtures  thing does seem to come up a lot.

Mic

[Sam Kusnetz]

Mic

I think it’s certainly a sensible request!

Do you think that would be better than allowing the percentage slider to be assigned as the default parameter, or do you think those two options are more or less equally useful?

-sk

––
Sam Kusnetz [he/him/his] (what is this?)
Figure 53
https://qlab.app | https://figure53.com

To view this discussion on the web visit https://groups.google.com/d/msgid/qlab/98114c28-edf2-4c74-92bf-449ca6ecb117n%40googlegroups.com.

[micpool]

Actually, thinking about it it wouldn't work any better than the existing one to many as it would still lose the color settings in an all.intensity=0 command. So the complete answer to Peters original question is probably that adding the existing one to many virtual parameter to the RGB definition as a custom definition would allow an all.intensity=0 blackout. But,  he would still have to use the individual RGB values to bring them up to level in a color.
Mic

[micpool]

Allowing the percentage slider to be assigned to a virtual parameter that could be named intensity (or anything else you wanted) and set as the default parameter would I think probably work best.

Mic

[David B]

Any update to this yet? Unfortunately running into a very similar problem. Trying to control RBG fixtures (and blackout) without loosing the color that was previously set. Checked QLab 5 and don't see any new virtual parameters :( 

[Chris Ashworth]

None yet, but it’s on the radar — thank you for the reminder and the feedback!

-C

[David B]

Appreciate it!

In the meantime, is there any way perhaps to programmatically (or from a cue) control a submaster on the Light Dashboard? That may be able to resolve my problem temporarily.

[Chris Ashworth]

Hi David,

The light dashboard has an OSC API that you could use:

https://qlab.app/docs/v5/scripting/osc-dictionary-v5/#workspaceiddashboardsetlight-string-setting-time 

--
Contact support anytime: sup...@figure53.com
Follow QLab on Twitter: https://twitter.com/QLabApp
User Group Code of Conduct: https://qlab.app/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups "QLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qlab+uns...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/qlab/cf8a781f-cbc3-4855-ac59-9b44f73d85e7n%40googlegroups.com.