Control/Dimming DMX 70 fades!??!

I must be a reallllllll dork, but I've been running 'conventional' and DMX boards for years and all I want to do is get my new Chauvet DMX 70 to fade between one scene and the next!??! It won't do it in manual - all I get is hard cuts when selecting the scene numbers. In 'auto' it simply runs between the scenes in the bank. With the speed slider set too low it runs to quickly through each scene. Set it higher and it waits for ever. Again all I want is a 3-4 second 'disolve' between scenes. HELP!!! and thanks!!!
 
It honestly sounds like you've set it for "steps" (effect) instead of "scenes". Do you have the manual? Does it even support scenes?
 
I do have the manual and have also contacted tech support. Their only help was 'be certain to push the auto button', which again only works with the speed slider - too low and it runs the scenes into each other. Too high (long) and the scenes never move... Yes it does have a fade slider, but only works with the speed slider!??! Thanks for the help so far. DRG
 
The DMX 70 is basically an inexpensive board for movers. It does that quite well. However, as it is designed to operate movers, it is programmed for LTP or Latest Takes Priority. This does not work too well if you are using it for conventionals where you want HTP or Highest Takes Priority. With the exception of lamp intensity or shutter, HTP would be a nightmare in a mover based system, so I am not sure there is even a way on the DMX 70 to change it to HTP. (HTP is what you need in order to cross fade.)
 
I don't see why HTP would be a nightmare in moving light programming. I programmed for years moving lights on a HTP console using traditional theater cue stacks. It is just a mode of thinking.

I can now use LTP consoles too, but in the end, it is just a way of thinking. Hardly a "nightmare". The real nightmare is programming moving lights without a monitor. ;-)

Mike
 
I don't see why HTP would be a nightmare in moving light programming. I programmed for years moving lights on a HTP console using traditional theater cue stacks. It is just a mode of thinking.

I can now use LTP consoles too, but in the end, it is just a way of thinking. Hardly a "nightmare". The real nightmare is programming moving lights without a monitor. ;-)

Mike

HTP- Cross fades: The problem occurs in the value shifts between the two scenes. If it is a hard cue with no fade in, it works ok, but slow it down and you end up with gobos, colors, X, Y, and other neat unintended changes as you transfer from A to B.
If the shutter/fader can be run HTP and X/Y and other features LTP, then no problem.
 
HTP- Cross fades: The problem occurs in the value shifts between the two scenes. If it is a hard cue with no fade in, it works ok, but slow it down and you end up with gobos, colors, X, Y, and other neat unintended changes as you transfer from A to B.
If the shutter/fader can be run HTP and X/Y and other features LTP, then no problem.

Maybe I am missing your point. I still don't see the problem.

I have a Studio Spot set at 95 on its litho setting in cue 4. It is also set at 95 in cue 5, but I want it to change in cue 6 so I set it to 100. It fades from the 95 litho to the 100 litho. If I am running another cue stack then I don't program in the light. So even when I run the C/D fader (assuming the previous cues are on the A/B fader) nothing happens. I see no problem.

Mike
 
Jumping in quickly on the whole HTP/LTP thing - it won't make any difference in a single cue list if movers are controlled HTP or LTP, but if you are mixing playbacks, like submasters+cue list, or multiple cue lists, then it can become quite nasty as only the higher level will win. And which is higher, by the way, red or blue? Stage Left or Stage Right? This is why LTP is much better for controlling non-intensity parameters. LTP behavior also can facilitate move-fades, which simply means once something gets moving to a target, it will continue to fade there in it's own timing without getting stomped on by another incoming cue. Usually you have LTP and MoveFade behavior in Tracking consoles. HTP is really a method of dealing with crossfading Preset style consoles. While HTP and non-intensity are usually a bad combo, they can coexist, but there will be challenges if you're not using a single cue list sequential playback style.

Ducking back out now...

Sarah

Sarah Clausen
Controls Product Manager
ETC, Inc.
 
Jumping in quickly on the whole HTP/LTP thing - it won't make any difference in a single cue list if movers are controlled HTP or LTP, but if you are mixing playbacks, like submasters+cue list, or multiple cue lists, then it can become quite nasty as only the higher level will win. And which is higher, by the way, red or blue? Stage Left or Stage Right? This is why LTP is much better for controlling non-intensity parameters. LTP behavior also can facilitate move-fades, which simply means once something gets moving to a target, it will continue to fade there in it's own timing without getting stomped on by another incoming cue. Usually you have LTP and MoveFade behavior in Tracking consoles. HTP is really a method of dealing with crossfading Preset style consoles. While HTP and non-intensity are usually a bad combo, they can coexist, but there will be challenges if you're not using a single cue list sequential playback style.

Ducking back out now...

Sarah

Sarah Clausen
Controls Product Manager
ETC, Inc.

Its certainly not ideal for running multiple stacked cue lists, but it is possible and hardly a "nightmare". In fact, for me LTP was a nightmare until I got used to it.

Mike
 

Users who are viewing this thread

Back