Excel to QLab to Q Lights
175 views
Skip to first unread message
micpool
May 10, 2023, 8:47:41 AM5/10/23
to QLab
My Excel to QLab, console microphone mute, proof of concept......
https://groups.google.com/g/qlab/c/-RdirSxQnqA/m/waWetC8uAQAJ
is now working at a usable speed with up to 64 channels.
The idea of this is that the easiest way to program and manipulate simple 2 state data could be through a spreadsheet as this has all the tools you need to process tabular data really quickly and flexibly.
I have now developed this further for three states, as a cue light system. This demo has 10 outstations, and an Excel sheet with 10,000 cues which can be set just by clicking the boxes.
QLab reads the data directly from the spreadsheet and arms and disarms timeline groups for each of three states for each cue light (Red, Green Off) which are then fired en masse
The groups can contain cues to operate whatever devices you want to use. In this demo:
The attached demo video is 1 fps to fit within the posting limits for attachments in this group, so doesn't show true latency. In reality everything apart from the Philips Hue Light is close to instant, but the Philips Hue because it has to negotiate a connection with the Hub each time has a noticeable lag (<1sec). It is possible to get Philips hue lights to respond much faster from QLab using Hue Entertainment mode, but I haven't currently implemented that, as I would imagine the best way of using this for most users is going to be with MIDI controlled relay boxes or simple DMX LED drivers. What is really fast though is the acquisition of the data from the spreadsheet to QLab, which I thought with 10,000 cues might be a bottleneck, but isn't.
https://groups.google.com/g/qlab/c/-RdirSxQnqA/m/waWetC8uAQAJ
is now working at a usable speed with up to 64 channels.
The idea of this is that the easiest way to program and manipulate simple 2 state data could be through a spreadsheet as this has all the tools you need to process tabular data really quickly and flexibly.
I have now developed this further for three states, as a cue light system. This demo has 10 outstations, and an Excel sheet with 10,000 cues which can be set just by clicking the boxes.
QLab reads the data directly from the spreadsheet and arms and disarms timeline groups for each of three states for each cue light (Red, Green Off) which are then fired en masse
The groups can contain cues to operate whatever devices you want to use. In this demo:
LX is using Showplay running on an iPad
SND is using a little app called MicsQLight which puts an OSC controlled Q Light window on any Mac on the network
VID is using a Philips Hue Light
SND is using a little app called MicsQLight which puts an OSC controlled Q Light window on any Mac on the network
VID is using a Philips Hue Light
WINCH1 is using Showplay on an iPhone.
You can use any QLab cue type to control your cue light which might include Lighting cues for DMX output, MIDI to control relays, Network cues for any OSC device, audio cues for comms inject, Text Cues for output to Monitors etc. etc.
There is a MImic Window that shows the state of all 10 Q Lights
You can use any QLab cue type to control your cue light which might include Lighting cues for DMX output, MIDI to control relays, Network cues for any OSC device, audio cues for comms inject, Text Cues for output to Monitors etc. etc.
There is a MImic Window that shows the state of all 10 Q Lights
The attached demo video is 1 fps to fit within the posting limits for attachments in this group, so doesn't show true latency. In reality everything apart from the Philips Hue Light is close to instant, but the Philips Hue because it has to negotiate a connection with the Hub each time has a noticeable lag (<1sec). It is possible to get Philips hue lights to respond much faster from QLab using Hue Entertainment mode, but I haven't currently implemented that, as I would imagine the best way of using this for most users is going to be with MIDI controlled relay boxes or simple DMX LED drivers. What is really fast though is the acquisition of the data from the spreadsheet to QLab, which I thought with 10,000 cues might be a bottleneck, but isn't.
As a proof of concept it works really well and seems to be a really easy and flexible way to program Q Lights for a show.
Mic
Mic
Sebastian Frost
May 10, 2023, 10:58:52 AM5/10/23
to ql...@googlegroups.com
I can only guess that there have been no replies to this thread because we’re all still speechless in awe of Mic’s mighty masterfulness…
Seb
My Excel to QLab, console microphone mute, proof of concept......
https://groups.google.com/g/qlab/c/-RdirSxQnqA/m/waWetC8uAQAJ
is now working at a usable speed with up to 64 channels.
The idea of this is that the easiest way to program and manipulate simple 2 state data could be through a spreadsheet as this has all the tools you need to process tabular data really quickly and flexibly.
I have now developed this further for three states, as a cue light system. This demo has 10 outstations, and an Excel sheet with 10,000 cues which can be set just by clicking the boxes.
QLab reads the data directly from the spreadsheet and arms and disarms timeline groups for each of three states for each cue light (Red, Green Off) which are then fired en masse
The groups can contain cues to operate whatever devices you want to use. In this demo:
https://groups.google.com/g/qlab/c/-RdirSxQnqA/m/waWetC8uAQAJ
is now working at a usable speed with up to 64 channels.
The idea of this is that the easiest way to program and manipulate simple 2 state data could be through a spreadsheet as this has all the tools you need to process tabular data really quickly and flexibly.
I have now developed this further for three states, as a cue light system. This demo has 10 outstations, and an Excel sheet with 10,000 cues which can be set just by clicking the boxes.
QLab reads the data directly from the spreadsheet and arms and disarms timeline groups for each of three states for each cue light (Red, Green Off) which are then fired en masse
The groups can contain cues to operate whatever devices you want to use. In this demo:
LX is using Showplay running on an iPad
SND is using a little app called MicsQLight which puts an OSC controlled Q Light window on any Mac on the network
VID is using a Philips Hue Light
SND is using a little app called MicsQLight which puts an OSC controlled Q Light window on any Mac on the network
VID is using a Philips Hue Light
WINCH1 is using Showplay on an iPhone.
You can use any QLab cue type to control your cue light which might include Lighting cues for DMX output, MIDI to control relays, Network cues for any OSC device, audio cues for comms inject, Text Cues for output to Monitors etc. etc.
There is a MImic Window that shows the state of all 10 Q Lights
You can use any QLab cue type to control your cue light which might include Lighting cues for DMX output, MIDI to control relays, Network cues for any OSC device, audio cues for comms inject, Text Cues for output to Monitors etc. etc.
There is a MImic Window that shows the state of all 10 Q Lights
<Screenshot 2023-05-10 at 12.36.45.png>
The attached demo video is 1 fps to fit within the posting limits for attachments in this group, so doesn't show true latency. In reality everything apart from the Philips Hue Light is close to instant, but the Philips Hue because it has to negotiate a connection with the Hub each time has a noticeable lag (<1sec). It is possible to get Philips hue lights to respond much faster from QLab using Hue Entertainment mode, but I haven't currently implemented that, as I would imagine the best way of using this for most users is going to be with MIDI controlled relay boxes or simple DMX LED drivers. What is really fast though is the acquisition of the data from the spreadsheet to QLab, which I thought with 10,000 cues might be a bottleneck, but isn't.
The attached demo video is 1 fps to fit within the posting limits for attachments in this group, so doesn't show true latency. In reality everything apart from the Philips Hue Light is close to instant, but the Philips Hue because it has to negotiate a connection with the Hub each time has a noticeable lag (<1sec). It is possible to get Philips hue lights to respond much faster from QLab using Hue Entertainment mode, but I haven't currently implemented that, as I would imagine the best way of using this for most users is going to be with MIDI controlled relay boxes or simple DMX LED drivers. What is really fast though is the acquisition of the data from the spreadsheet to QLab, which I thought with 10,000 cues might be a bottleneck, but isn't.
As a proof of concept it works really well and seems to be a really easy and flexible way to program Q Lights for a show.
Mic
Mic
--
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/522cdd3c-eba0-47f7-993f-2506b48cee9en%40googlegroups.com.
<QLight Demo4K short.mov><Screenshot 2023-05-10 at 12.36.45.png>
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/522cdd3c-eba0-47f7-993f-2506b48cee9en%40googlegroups.com.
<QLight Demo4K short.mov><Screenshot 2023-05-10 at 12.36.45.png>
BoatHippie
May 11, 2023, 9:59:38 AM5/11/23
to QLab
wow.
Reply all
Reply to author
Forward
0 new messages