Scroller Madness

Thanks guys.  It's nice to know I didn't miss something obvious.  I have all my color palettes labelled with the frame numbers, since that's how our designers tend to think, I was actually just hoping for a reference for myself for when I lose the piece of paper with the scroll colors on it.

 I can, however, see a possible drawback to calibrating the scrolls backwards.  Well, it's pretty minor, but if you do that you have to remember to watch out for any quick scrolls to home (no color), since they'll be going to the opposite end of the scroll from where 'frame 1' is calibrated.  Not a fatal flaw in my little corner of theatre, but possibly annoying none the less.  In the end, I'll never know, since I'm going to get the scrolls physically reversed, even if I have to do it myself.

Brian

I recently had cause to revisit the scrollers on encoders thing.  I realized that during these dance school recitals, I have no designer whining about seeing what frame a light is in.  I simply have to pick a color fast  and move on.  We have two sets of 26 frame scrollers.  In order to avoid using 52 Direct Selects for discreet Color Palettes we use one set of palettes for both, labeled as Frame #.  Then we are constantly referring to two sheets of paper to decipher the gel colors.  I was very pleased to rediscover that once I built my custom scroll I was able to use the Color Picker.  Just pick any point on the spectrum and it automatically takes you to the nearest available match on your scroll.  Though I still think it won't be of much use when working for designers who starve for info, I can foresee myself using it more in the future.  Here are a few questions and notes:

When I built the scroll and put it on the encoder, the touch screen buttons (non-expanded) said Min and Max.  Is there a reason that can't be Next and Last?  It caused me a lot of unintended scroller runs. 

When in Coarse mode, there was no 'click' to indicate a full frame.  Therefore the only way to call a frame was in the expanded mode.  I think this is a bug because it bugged me.  Was I doing something wrong?

I am assuming that Calibrating a scroller should have no affect on pre-existing color palettes?

How does one Import a calibrated custom scroll into a new show?   Are they stored in Fixtures, Patch or what?

For Palettes, please remind me of the syntax needed to add new scroller channels (say 1 thru 10) and have them included in the existing show palettes.

Is there currently any plans for having some Encoder labels showing in the Tombstone, maybe as a choice instead of Palette labels?  It sure would be cool...

Thanks much, Brent 

(as of ver 1.4.5 on pc, 1.4.2 on console)

Calibrating a scroller only adjusts the snap points for NEXT/LAST on the encoder.  You find that the scroller value onscreen is different after calibrating then before, therefore all color palettes need to be updated with the new DMX values.  If your encoded does not have NEXT/LAST try using Wybron Coloram2 for a scroller type. I believe the custom values are stored on a per string type basis.  Per unit is more than we can expect.  I create a new string for each batch of strings, even if the frames are the same. 

As far a patching scrollers, or any other non-conventionals, I want the interesting part (ie Wybron Coloram2 etc) to be part 1, so that when I'm in Live Table packed I see "Coloram2....." instead of "dimmer" above the table.  I switch to Patch by Address after all non-dimmer patching is done, as these dimmer addresses  will be safely added to additional parts.  I try to organize patch to make maximum use of NEXT / LAST as the console keyboard seems to lend itself to typos.

I reserve Color Palettes 1 to 20...etc for color frame based scrollers.  CP 1 = Frame one, and so one.  We also have CXI's, so CP 101 - 184 is taken directly from the CXI colormix manual.  I notice the Color Picker is timid about taking parameters to their maximum value, so we have palettes for Max Red, Blue, Green etc.

To preserve palette info from show to show, I don't start a show from scratch, but just delete show channels cues, designer's groups and presets.  It's important to keep one channel of each color change type to preserve the palettes. I have 1001 = Coloram2, 1002 = CXI, 1003 = VL1k 1004 = VL3500,1005=autoyoke w/scroller, and so on.  You should deep clear after deleting all this as I have noticed what could be called artifacts in the tombstone display, most likely from corrupt persistent memory.

After installing a new string, I patch 3 or 4 of the scrollers  into 1001 (to get a consensus) and then calibrate them in the boardroom, if possible, writing down the values for archive purposes.  In blind spreadsheet I set the values for 1001 in CP-1  and so on, not by typing it in but by using the NEXT/LAST on the encoded (encoder expanded mode is helpful here).  Why? Because the console will fetch up the Hue/Saturation value for that gel as well as the DMX value.  I can copy the Hue/Sats to my CMY mixers to get, if not a perfect match, at least a starting point (VL's suck at mixing color).

With mixers I notice that I'll get Hue/Sat greyed out or the physical parameters (scroller,scroller2,C M Y etx), but not both.  This is to avoid a chicken vs egg situation (and a crash).  With scrollers especially CXI's you want to fade by the physical parameter not HUE/SAT, which is what the color picker gives you.  To shift the emphasis I would type chan 1002 scroller scroller2 @ + 0 ENTER.  When this is done the console calculates new values for the greyed out parameters.  The formulas are lossy so you can't flip back without data corruption, which means going back to the color picker gel library to start over.

I can fix all the CXI's at once in blind.

CP 101 Thru 184 ENTER.  Group2(show cxi's)scroller scroller2 @ + 0 ENTER

You can use the same technique to populate your custom string info into the show.

<BLIND SPREADSHEET> CP 1 thru CP(Last)<ENTER>Chan 1001 Copy to Group(Coloram2)ENTER  Chan 1003 Copy to Group (VL1K) ENTER and so on.

You don't have to be in "Spreadsheet " to do a spreadsheet style command, by the way

When I select a scroller channel the console will convert the DMX screen value the correct gel name on the encoder screen,  which is the second reason you  should go to the trouble of building a custom scroll type.  I did have a network glitch once which caused the console to drop the scroller info, but since I had the correct DMX in palettes I was able to proceed thru tech anyway.

Of course , most of this applies to beam palettes as well.

It would be great to have an autocopy feature.  If a fixture had no value in a particular palette, values from the highest fixture of the same type would be copied over.  So If I saved a new mix on one light, setting the whole group to the same palette would populate the rest of it.

Well, here's an update on my encoder situation-

One of my scroller groups is 21 thru 31.  They are all patched as Wybron coloram II's with the same custom scoll profile.  They are all in the same Frame 1.  If I call the whole group, I get Min and Max on the Encoder.  What's particularly vexing is that the is a picture of the next and last frame above the words min and max  (all the way through the string.)  It makes it very easy to press the Min or Max button, hoping for Next or Last, thus running the full length of the scroll unintentionally.

However, I discovered that if I call channels 21 thru 25 instead, I get Next and Last plus clicks on the wheel.  Same if I call 26 thru 30.  Turns out that the scollers are in Part 1 of 21 thru 25, and Part 2 of 26 thru 30.  It looks as though the console is treating them as different 'fixtures' or something just because they are in different parts.

Can anyone tell me if this is based on intentional logic or if this is something that might get remedied in the future?

Must I be expected to make sure that all my scrollers/devices are in consistent channel parts?  Various edits of patch invariably happen while ringing out the rig.

What is the easiest way to switch the two parts of a series of channels?  In this instance, I will write down the dimmer address of 26 thru 30. Delete those part ones, then repatch so that they land on part two instead.  I will have to do this on a couple other groups as well.  It sounds like a drag to me.

(using version 1.4.5 offline)

The only way I get MIN/MAX on this version is if the first channel in the selection is not a frame based scroller (ie dimmer or CXI or VL) .  I can't get pictures over them though.  Scrambling the patch and even mixing types didn't affect it, although a ETC tech told me that patch order may have affected palettes a few version back.  Consistancy never hurts. You should indicate the version your running since each version  is another spin of the wheel.

I notice that the NEXT/LAST encoder keys generate a command line message (CHAN 21 SCROLLER_NEXT).  You can "learn" this into a macro (LAST as well).  You may have to clean it up with the macro editor, be sure and leave the line terminator symbol if you do.

(using version 1.4.5 offline)

The only way I get MIN/MAX on this version is if the first channel in the selection is not a frame based scroller (ie dimmer or CXI or VL) .  I can't get pictures over them though.  Scrambling the patch and even mixing types didn't affect it, although a ETC tech told me that patch order may have affected palettes a few version back.  Consistancy never hurts. You should indicate the version your running since each version  is another spin of the wheel.

I notice that the NEXT/LAST encoder keys generate a command line message (CHAN 21 SCROLLER_NEXT).  You can "learn" this into a macro (LAST as well).  You may have to clean it up with the macro editor, be sure and leave the line terminator symbol if you do.