Manual override

[tfm...@gmail.com]

Hi,

I have two fixtures with their own effects and would like to build the ability to manually override these temporarily.

Say I have a music synced scene and have a part of the track I'd like to create a static red across the fixtures using a midi pad (the override). For ease of control this is ideally a toggle function or if not possible use a pad A for "override on' and pad B for 'override off' - using Midi data. 'Override off' resumes the previous scene. I would think the override has to control a new source while at the same time disable the regular source(s) which create the auto effects.

What's the easiest way to implement this?

[Mathieu]

You could create a new grid and set a higher precedence number to it. You can set the precedence when selecting the grid in the grid manager. It's at the same place that you'll find the grid activation slider that you can control with your midi toggle.

So basically, when you activate a grid with a higher precedence, it overrides lower precedence grids, allowing to layer your effects.

[tfm...@gmail.com]

Ok txs. So in the new grid I setup whatever override behavior I want. Do I need another Midi message to deactivate the new grid or can I build a toggle function with the same Midi message?

[tfm...@gmail.com]

Managed to get a start on it. Duplicated the grid as "override" and added a source connected to Midi and can override the other grid! 3 questions:

• How can I toggle the source(s) on/off through Midi as at the moment I need to hold the pad for the grid to remain active?
• The pads on my keyboard are touch sensitive so they send a different value to activation every time while I really need 0 or 100%. Probably needs a formula to activate and possibly implement the toggle as well
• How can I create pure Red, Green and Blue values with the HSL model?

[Mathieu]

>> How can I toggle the source(s) on/off through Midi as at the moment I need to hold the pad for the grid to remain active?

When you select the midi note, there's a toggle option. It automatically generates the formula for you.

Just for your information, the formula looks like:

toggle(onbeat(midi.note(1,10)))

It returns either 0% or 100% and it should work with your touch sensitive pad.

>> How can I create pure Red, Green and Blue values with the HSL model?

Pure red is: hue = 0, saturation = 100%, intensity = 50%

Pure green is: hue = 120, saturation = 100%, intensity = 50%

Pure blue is: hue = 240, saturation = 100%, intensity = 50%

[tfm...@gmail.com]

Ok I have gone the single grid route and listed all the attributes (e.g. red, green, blue, pan etc.) in columns with each having a source controlled by Midi. Works well.

Where I get stuck is the activation. Essentially when I override red (all fixtures go red) I also need to activate the grid at the same time and when toggling the same pad deactivate the grid so the previous grid with the lower precedence continues its patterns. How do I do that? I tried to use the activation attribute of the grid but this didn't give me consistent results.

[Mathieu]

I think I'd need more info about what you've tried. Your manual grid with a higher precedence should be active at the same time as your other grids.

[tfm...@gmail.com]

Ok so are you saying if I have 2 grids - grid A at precedence 0 and grid B at 5 - both can be activated and all I have to worry about is any attributes that appear in both grids. Say I have a dimmer attribute on grid A with power slider on a sine wave and I manually override the dimmer attribute in grid B with a strobe signal on power) as long as I release the attribute in grid B (toggle or temporary) it will go back to the sine wave control from grid A?

[Mathieu]

>> if I have 2 grids - grid A at precedence 0 and grid B at 5 - both can be activated and all I have to worry about is any attributes that appear in both grids.

Exactly.

[LCS Mike]

Hi Matthew,

I just wanted to say thank you for LightGems.

We’ve been using it in real concert situations with our band, and it’s been rock solid.

The system does exactly what we need: fast, reliable, musical, and actually usable on stage – which is rare.

I’m sending you a short video where you can see how we’re running it live, synced to the show.

For us, it’s not just a lighting tool, but a core part of how the concert works.

Thanks again for the work you put into this – it really shows.

https://vm.tiktok.com/ZNRMuX3pV/

Best regards,

LCS Mike

--
You received this message because you are subscribed to the Google Groups "Lightjams" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lightjams+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/lightjams/9a1d977f-98b6-4a18-990e-b2c4a977a508n%40googlegroups.com.

[Mathieu]

Thanks for the kind words! Lightjams has been in development for 15 years now and it will continue for many years to come :)

[LCS Mike]

Hi Matthew,

Thanks a lot for the kind reply — really appreciate it.

Good to hear LightJams is still actively evolving. From a live-performance perspective, that long-term stability and philosophy really shows in use.

If it’s ever useful on your side, I’m happy to share more real-world feedback from concert environments as we keep pushing the system live on stage.

Thanks again,

Mike

To view this discussion visit https://groups.google.com/d/msgid/lightjams/f50c3aa2-3ade-4b58-bbe3-7084ecd163den%40googlegroups.com.