Kiosc and Scheduler

[chillioliver]

I currently have 30+ RGBWW DMX floods being controlled with Kiosc and OSC and Show Control.
See photo attached. Each page does a group of lights.
I've used separate faders for WW, CW and created virtual dimmer channels as couldn't get it working reliably any other way, and the fixtures don't have intensity channels.

Client has asked for a scheduler for 2x of the lights. I could separate these out into a separate zone if it helps.

Q1, will the scheduler or the show control OSC take priority... i.e. if scheduler turns light on, and then someone goes to edit colour with app, what will happen?

Q2, is there a way of getting the faders to reflect what the lights are actually doing based on their DMX values? At the moment if you control all lights through the global page, the faders on the other pages remain at 0 which is a bit confusing. It would also be handy if the faders could move in the appropriate group, based on the scheduler too.

Once scheduler is working, I'd probably like to integrate a scheduler toggle switch as mentioned here.


Thanks for any input!

[Julien Levaufre]

It looks like a really nice project that you have done here.
You say that you are using KIOSC but you dont say what is the DMX controller it is controlling, is it CueCore3 or other?

The way to implement the scheduler behaviour will be different depending on the type of controller you are using but  I expect you to use a CueCore3.

I think you main question is not about the scheduler trigger set up it self, so I will skip this part.

I guess that you are using the network messages from the Kiosc to directly control the parameters of fixtures.
In a basic programming it will be the last one sending values that will be applied, so the scheduler will erase what was set before for each parameter but then the user can directly take over from KIOSC and change the output.
From version 1.28.xx of the CueCore3 we have "conditions" in the show control. This can be used to be sure that when the scheduler is activated the user cannot change the parameters of those specifics fixtures.

You can also record your scheduled preset in a playback, and in this case the playback and the fixture control will be merged HTP. ( but you can do a fixture/clear before calling your cue)

Anyway if you do not want the user to be able to change the color of the scheduled fixtures, the best is to use the conditions.

Now if you want the faders to reflect the fixture status, you just need to create a "fixture" actionlist, where you will be able to use the intensity or  RGB color as a trigger to send an OSC message to the KIOSC. Using the element tags you will be able to remotely control them. Sadly this trigger is not available for CW and WW.

I hope those informations will help. you in your project,
Do not hesitate to ask more informations if needed.

[chillioliver]

Thanks so much for your prompt response. I updated to 1.28.24.
I am just experimenting with the scheduler programming now.

In case I need to edit remotely, I'm trying to enable the Purple Cloud, but every time I generate a new key and add into settings page - it still does not appear on the web portal. Any ideas why? I've tried toggling the share analytics option.

[Julien Levaufre]

Great, good luck with the scheduler programming!

For the cloud, the "share analytics" function needs to be turned on.
If the connection doesn't work, check if you have a router set in the CueCore3 settings.

[chillioliver]

Excellent thanks - editing the router IP address seemed to allow it to connect to Purple Cloud, although it still seems a bit intermittent. I'm wondering if there's a problem with the internet connection. The cloud symbol on the bottom left of CueCore web ui is flashing, but right this moment it's offline from Pcloud ui.

For now I have added scheduler to action lists, and created 2 actions, changing fixtures intensity from 0/100% on @ Sunset and off @ 21;30

[Julien Levaufre]

I am glad to read that you get the Cloud connection working.
We do not have any report of issues with the cloud servers now, so it is probably a network issue on your side that makes the connection unstable.