Parking Non-Dims.....

Hi Dave,

I don't have a console in front of me at the moment but I've got time to kill and was poking around offline...

The Fixture type "Non Dim at 50" has two ranges for its intensity. The first is where if the value is  0%- 49%, the DMX output is ranged DMX 0 - 0. The second range is from 50 to 100 and the DMX range is 255-255. So in theory, if you enter anything ≤ 49, it will output DMX 0. where as ifis ≥ 50, it will output 255

I can't replicate this, but it seems that the first time you hit full, you are going to "full" of the first range which would be 49%, while the second time you hit full, it takes you to full on the second range.  If in Park, if you try [At] [/][/] [255], does it work any better? Or in live, if you 1001-1048 [At] [/] [/]  255 [Park] [Enter]? Hopefully this syntax will ignore the ranges of the channel and just send the DMX value that you want.

Just a thought.

travisres said:

The Fixture type "Non Dim at 50" has two ranges for its intensity. The first is where if the value is  0%- 49%, the DMX output is ranged DMX 0 - 0. The second range is from 50 to 100 and the DMX range is 255-255. So in theory, if you enter anything ≤ 49, it will output DMX 0. where as ifis ≥ 50, it will output 255

I can't replicate this, but it seems that the first time you hit full, you are going to "full" of the first range which would be 49%, while the second time you hit full, it takes you to full on the second range.  If in Park, if you try [At] [/][/] [255], does it work any better? Or in live, if you 1001-1048 [At] [/] [/]  255 [Park] [Enter]? Hopefully this syntax will ignore the ranges of the channel and just send the DMX value that you want.

Thanks for that - I din't realise about the [/] [/] syntax! That said, it's probably quicker just to hit full lots of times (or requires me to think less!). Your explanation makes sense, I suppose - it just doesn't seem especially logical to me - surely full is full?

I'm still a little confused by the random values which show up in live when they're parked, but c'est la vie!

Ta!

I got caught out by this the other day as well.  I happened to be in Park because I needed to wheel some 5k dimmers and someone asked me for the band lights.  I type 1000 at FULL Enter and the value jumps to 49, but the non-dim does not come up.  I type the same thing and it jumps to FL and the lights come on. If I were to type 1000 LEVEL, it would instantly jump to FL and turn the lights on.

When I'm in LIVE, if I type 1000 at Full enter, then the value goes to FL and the lights come on.  But if I update that into the current cue and Go To Cue again, it jumps to 49 and the lights go off.  Clearly there is some strangeness going on with how non-dims are handled.  

I think for the moment if the dimmer is actually a non-dim, then just use a generic dimmer. If you are trying to make a real dimmer behave like a non-dim, then you have to put up with this for awhile longer.

Kevin

I got caught out by this the other day as well.  I happened to be in Park because I needed to wheel some 5k dimmers and someone asked me for the band lights.  I type 1000 at FULL Enter and the value jumps to 49, but the non-dim does not come up.  I type the same thing and it jumps to FL and the lights come on. If I were to type 1000 LEVEL, it would instantly jump to FL and turn the lights on.

When I'm in LIVE, if I type 1000 at Full enter, then the value goes to FL and the lights come on.  But if I update that into the current cue and Go To Cue again, it jumps to 49 and the lights go off.  Clearly there is some strangeness going on with how non-dims are handled.  

I think for the moment if the dimmer is actually a non-dim, then just use a generic dimmer. If you are trying to make a real dimmer behave like a non-dim, then you have to put up with this for awhile longer.

Kevin