Scrollers not automarking

Hi there

Am I correct in assuming that your scrollers are patched as a fixture by themselves, and not attached to a channel with intensity values?  If this is the case, I would suggest this is why the scrollers are not AMarking as they don't have an intensity value to tell them when they are dark.

The easiest solution I can suggest would be to patch the scrollers to the intensity channel they are associated with.  If you have already programmed your show (which by the sounds of it, you have)  I would suggest using the move-to command.  

Let's say your scrollers are currently ch 201 > 210 and the lights that they are attached to are ch 1 > 10.  From the patch screen:

[201 > 210 move to 1 > 10 part 2 enter]  Move to should be a softkey.  Alternatively, if you press [copy to] twice, it will post "move to" on the command line.  Advantage of using "move to" in patch is it does exactly that - it will move the channels in patch, and also in your record targets (cues, pallets, presets, etc)

Hope that helps

Cheers 

Show closed.  I tried your syntax before I struck the plot.  I seem to have lost intensity info in several of the cues.  

I am returning the scrollers.  Next time I will patch them with the dimmer channels.

On Eos/Ion, Congo and SmartFade ML, Scrollers are considered multi-part devices.

You patch both the Scroller and the Dimmer to the same channel (device in SFML).

The same concept applies to those moving lights that have external dimmers, like some Vari*Lites and versions of the Mac TW1

Any 'compound' fixture is simply made up of all its parts - quite literally in the case of Eos/Ion!

In ETC's modern consoles, a channel is a 'fixture' - be that a Source Four, a Source Four with scroller attached, or whatever the latest all-singing-all-dancing moving light may be.

This means that to control the fixture, you simply select the channel - the scroller turns up on the colour encoder, while the dimmer turns up on the level wheel. There's no longer any need to remember "Scroller 1001 is on dimmer 101" or whatever method/crib sheet you used before.

This is a big change from many older consoles, and can take a bit of getting used to - but we think it's much easier to deal with, and I hope you'll agree next time you use scrollers!

How do I discretely control two scrollers that are on a set of pars that are two-fered? 

That is address 1 = dimmer 1 = (2) pars = PART 1  Address 101 + 102 = (2) scrollers = PART 2

sk8rs_dad:

You could define a custom fixture with 2 scroller parts and 1 dimmer part.

A custom fixture is a good idea, however make sure you specify different attributes for each scroller. eg: "scroller" to control the scroller on the first lamps, and "scroller 2" for the scroller on the second lamp.  If you don't do this and you put the same scroller on 2 different parts, you will still only have one encoder to control the scroller.

Another alternative could be to make a dummy channel and just copy the intensity values to it so the auto-move still works properly.  Personally I'd prefer to make a custom fixture with 2 scroller encoders, but each to their own

Cheers 

sk8rs_dad:

You could define a custom fixture with 2 scroller parts and 1 dimmer part.

A custom fixture is a good idea, however make sure you specify different attributes for each scroller. eg: "scroller" to control the scroller on the first lamps, and "scroller 2" for the scroller on the second lamp.  If you don't do this and you put the same scroller on 2 different parts, you will still only have one encoder to control the scroller.

Another alternative could be to make a dummy channel and just copy the intensity values to it so the auto-move still works properly.  Personally I'd prefer to make a custom fixture with 2 scroller encoders, but each to their own

Cheers