Hi,
First, I am completely new to lighting.
I am working with a dmx setup consisting of about 100 lights which already has its own controller that loops over 6 or 7 scenes infinitely and repeats every 15 minutes.
Since I am new, I have no idea what type of fixtures these are or what channels they are on.
However, I want to be able to slow down or even pause the loop for the purposes of my performance. So my question is, can I use the dmx dump feature without actually setting up my fixtures first. Can I just record snapshots of the various scenes and replay them in a different order without knowing exactly which signals go to which lights etc?
I know its not the right way but don't think I have time to actually map the real setup.
Any advice on how I might approach this is greatly appreciated.
Dan
Working with Unknown Fixtures and Channels
- GGGss
- Posts: 3052
- Joined: Mon Sep 12, 2016 7:15 pm
- Location: Belgium
- Real Name: Fredje Gallon
You could snoop the DMX line with an DMX interface with input. Ideally a DMX interface with 2 channels (like Enttec PRO mk2 - you have to assign channel 1 as input; channel 2 as output)
You are talking about 100 lights ... are they just bulbs or are they RBG fixtures or even more 'worse' scanners and movers?
in QLC+ create like 256 generic dimmers on universe 2.
create like 256 knobs in VC
Have universe 1 act as DMX input
use the input channels as the trigger for the knobs (Yes I know - a very tedious job)
now when signals are present from your other desk - you snoop the values inside QLC+
DMX dump these into scenes.
After the snoop fase, simply unplug the existing desk and change the DMX line into channel 2 of your interface. Now QLC+ is sending (in control of your universe)
Some Advice: if there are movers or other 'intelligent' lights present - you really will need to have knowledge what what does. So an inventory will be necessary.
Brake a leg.
You are talking about 100 lights ... are they just bulbs or are they RBG fixtures or even more 'worse' scanners and movers?
in QLC+ create like 256 generic dimmers on universe 2.
create like 256 knobs in VC
Have universe 1 act as DMX input
use the input channels as the trigger for the knobs (Yes I know - a very tedious job)
now when signals are present from your other desk - you snoop the values inside QLC+
DMX dump these into scenes.
After the snoop fase, simply unplug the existing desk and change the DMX line into channel 2 of your interface. Now QLC+ is sending (in control of your universe)
Some Advice: if there are movers or other 'intelligent' lights present - you really will need to have knowledge what what does. So an inventory will be necessary.
Brake a leg.
All electric machines work on smoke... when the smoke escapes... they don't work anymore
-
- Posts: 3
- Joined: Sat Apr 06, 2019 8:38 pm
- Real Name: Rolo Saenz
What GGG says
i suggest that you get a pen and paper and make a list of all the fixtures you have in that venue
Make and Model
get a ladder and see what DMX channel the fixture is and also what channel count mode, most of the DMX fixtures have different modes
Example of this
ADJ mega par led light
that is a simplre RGB slim par Led fixture that can work in 3CH,4CH,5CH and 6CH dmx mode
the more channels , the more functions and or features you can access with your DMX controller
So yes, break a leg and get ready to spend some hours maping your venue
Rolo
i suggest that you get a pen and paper and make a list of all the fixtures you have in that venue
Make and Model
get a ladder and see what DMX channel the fixture is and also what channel count mode, most of the DMX fixtures have different modes
Example of this
ADJ mega par led light
that is a simplre RGB slim par Led fixture that can work in 3CH,4CH,5CH and 6CH dmx mode
the more channels , the more functions and or features you can access with your DMX controller
So yes, break a leg and get ready to spend some hours maping your venue
Rolo
-
- Posts: 2
- Joined: Tue May 07, 2019 12:24 pm
- Real Name:
Thanks for the info guys. Will try out the suggestion.
I of course want to map them out. We'll see if I have the time. At the very least I want to just use identical scenes to the console I am copying just played in a different order/speed.
I of course want to map them out. We'll see if I have the time. At the very least I want to just use identical scenes to the console I am copying just played in a different order/speed.
- GGGss
- Posts: 3052
- Joined: Mon Sep 12, 2016 7:15 pm
- Location: Belgium
- Real Name: Fredje Gallon
You know you could help the community?
A 'DMX Snoop Project'-project file would be very welcome. The DSP-project aka Digital Signal Processing. [edit- has to be extended to the other means of QLC+ inputs - more than DMX]
In VC
* a moderate sized frame with 8 pages of 8 x 8 rotary control matrix - labeled to the actual channel 001-512
* every rotary control bound to an external input (via input profile ??)
in play mode
* every of the 512 rotary-controls reflect the values read thru the input
* use the DMX-dump feature to copy whatever present at the input.
* so you can copy what is present thru others work in a unknown universe (do we have troubles with copyright now?)
This gives you a list of predefined cues you can alter into your production preferences.
and now - my limited list of cobblestones... this could mean...
* Device X configured as a QLC+ universe input:
- every project has to be altered to this config - !
- is the input profile going to work with altered input device config - ?
- will rotary sliders inbound control be reset with this altered config -?
* non DMX control inputs?
- midi (altered input profile)
- OSC (strict message structure & adopted input profile)
- (possible interaction of other QLC+ input controllers)
...
My 2 cents
A 'DMX Snoop Project'-project file would be very welcome. The DSP-project aka Digital Signal Processing. [edit- has to be extended to the other means of QLC+ inputs - more than DMX]
In VC
* a moderate sized frame with 8 pages of 8 x 8 rotary control matrix - labeled to the actual channel 001-512
* every rotary control bound to an external input (via input profile ??)
in play mode
* every of the 512 rotary-controls reflect the values read thru the input
* use the DMX-dump feature to copy whatever present at the input.
* so you can copy what is present thru others work in a unknown universe (do we have troubles with copyright now?)
This gives you a list of predefined cues you can alter into your production preferences.
and now - my limited list of cobblestones... this could mean...
* Device X configured as a QLC+ universe input:
- every project has to be altered to this config - !
- is the input profile going to work with altered input device config - ?
- will rotary sliders inbound control be reset with this altered config -?
* non DMX control inputs?
- midi (altered input profile)
- OSC (strict message structure & adopted input profile)
- (possible interaction of other QLC+ input controllers)
...
My 2 cents
All electric machines work on smoke... when the smoke escapes... they don't work anymore
-
- Posts: 51
- Joined: Tue Jun 02, 2015 4:29 pm
- Location: Scotland
- Real Name: Allan Rhynas
I've created a QLC based DMX Tester project to help analyse a DMX stream. See this thread QLC Based DMX Tester / Snoop.