light control and organize > groups; memory; interpolation of midi control
Bennnid last edited by
I m desining a patch for a show, there's around 50 cues/scenes, lights, turning platform, retro projector connected with dmx,
so I got my Enttec usb-dmx pro and working with "DX- Dmx enttec compatible" actor in an activated scene works fine.
Therefore I'm sending in a matrix value send ( one copy for each scene), all my light controls, so that I can use the crossfade scene to work my transition and that's fine!
but the problem is that the little korg nano control 1 managing the lights is not motorized and if the light operator needs to take control/adjust, there's going to be jumps of adjustments...
Also I wondered if any interpolation patch you'd like to share?
Another problem being I'm using scenes to " memorize" state, but if the operator adjust lights in a scene, it'll leave the scene changed,
in other words, how would you make a system allowing him to play within the scene and still get the "original " when coming back? just by reloading the patch?
Last thing, sometimes light softs allow to group light controls and this modularity makes them quite effective,
Do you know if anybody ever tried to do that in izzy? cos recreating a d-light or so would be quite long process...
thanks for your ... lights !
jfg last edited by
Another problem being I'm using scenes to " memorize" state, but if the operator adjust lights in a scene, it'll leave the scene changed,in other words, how would you make a system allowing him to play within the scene and still get the "original " when coming back? just by reloading the patch?
Could the snapshots be a solution?
DusX Tech Staff last edited by
As mentioned, the concern about the operator changing the state of the scene could be addressed by saving the 'good' stage of the scene as a Snapshot, and loading the snapshot on enterscene. This way you would have to save any changes to the snapshot before it would be permanent.
bonemap last edited by bonemap
Like @DusX and @jfg, I thought Snapshots might be the go to. The snapshot feature includes the option to exclude selected actors from the snapshot capture. This can be critical if you have actors in the scene that are more dynamic and you don’t want permanently fixed inside a snapshot.
dbini last edited by
The use of snapshots will help, but won't solve the initial problem of using a MIDI controller to tweak values, when each MIDI control will be set at an arbitrary level on entering a scene (lx scene rather than izzy scene) - i can imagine the scenario whereby a lx operator will want 'just a touch more light from this channel' and the channel is at 50% but the slider is currently at zero, causing a jump. how about a method of temporarily interrupting the data from the controller while the knobs/sliders get set to current values? (hold a button on the Korg while you fade up the slider until its output matches the current setting, then release the button to make changes)
there are ways to string together actors to make data increase or decrease relative to where it is currently set (i use comparator/value delay line/counter) but this will be an issue with the Korg Nano Kontrol because the rotary knobs are fixed 0-127. if you can get hold of something with endless rotary controllers (like an old Behringer BCR2000) then you can always increase or decrease your values relatively.
Bennnid last edited by Bennnid
@dbini good idea to mute midi controller until you match the actual state, (which you have to be sure though)
@bonemap and jFg of course snapshot is the way to restaure original values ! ( I m' not use with them and it seems perfect )
thanks everyone !
I'm now still a bit afraid with the possibility in grouping several fader in one.. seems hard to do without java isn't it?