Scroller Calibration

If you record the calibrate button into a macro, you can use it from the OLE. [Learn 1 Calibrate] now macro 1 is the calibrate key. We'll also fix it so that the button is accessible in the virtual encoder screen as well.

Importing just your patch will include the scroller calibrations.

There is currently no way to display the scroller frame label within the channel display, without using palettes. It's something we are discussing doing though.

Thanks for bringing these things up, and let us know if you are still having difficulty getting it working on the client.

Thank you both for the good answers.  Some followups-

I don't think I had a problem clicking the Calibrate button with the mouse on the OLE.  The real issue was that I had no need to Calibrate before I was able to Fine tune the frame in.  But I wonder if I could trick it into Fine mode with a Macro?...

That's good news on the RFU.  I hope there will be a way to perform all operations on it.

Is the Scroller Calibration info in a specific part of the Patch?  Will I benefit at all from the new Partial Load feature?  Or will all the Board Ops have to remember to load that Patch File before Patching any new show fixtures?

I encourage your discussion on this matter.  Every Designer this season has been desperate to be able to look at the screen and see what Frame the scrollers are in, and then wishing that it would say what that frame is.  We have two sets of 26 frame scrollers.  My first solution was to make a Show File with all channels 1-400 patched as scrollers.  I then dialed each frame in and recorded 26 CP's.  This worked for a while.  No matter which scroll was used, CP 1-26 reflected Frames 1-26.  Then I became aware of the Show Reference Labels thing and foolishly shared that info.  Now I am being asked to create a discreet set of Palettes for each scroller set so that we can label them by gel names.  This means 52 CP's taking a lot of real estate on the Direct Selects for the maybe dozen frames that they end up using.  Now, I've been holding my ground since October saying, "1.3 is coming in Nov, and could be here any day.  Then we can use that cool Calibration Feature to make that Super Cool 'Build your own Scroll on the Encoder Feature' usable."  At this point though, for that feature to be usable, we'll need to put a cheat sheet in front of the Designers saying which DMX value refers to which frame.  I can guess which one they'll want.

Thanks again for your attention,

Brent  

Oh yeah- another thing-

When I calibrate, does it effect the scroller (every scroller of that type and attribute), or the channel (just that specific scroller head)? 

All of our scroller heads have the same deviation.  Can I just patch one each of our two types into two channels and go from there, assuming the calibration will follow the scrollers?  Or do I need to do another dummy patch with virtual scrollers patched into every channel?

Is the Scroller Calibration info in a specific part of the Patch?  Will I benefit at all from the new Partial Load feature?  Or will all the Board Ops have to remember to load that Patch File before Patching any new show fixtures?

When I calibrate, does it effect the scroller (every scroller of that type and attribute), or the channel (just that specific scroller head)? 

All of our scroller heads have the same deviation.  Can I just patch one each of our two types into two channels and go from there, assuming the calibration will follow the scrollers?  Or do I need to do another dummy patch with virtual scrollers patched into every channel?

 How do you guys envision this feature?  Was it made to deal with a single aberrant scroller or two on a show by show basis, or was it developed as a permanent one time solution for people who use the same scrollers on many different shows.  I wonder if I am just looking at this wrong, trying to do something it wasn't designed for.

I would also like to reiterate my desire for some encoder label info on the Live screen.

Thanks all,

Brent

Brent... sorry, this one slipped through the cracks.

 The calibration is scroller specific.  So, if you calibrate one instance of a scroll, it has no impact on other instances (answering the "aberrant scroller" question).  If all of your scrollers have the same behavior, you can calibrate the first and then copy that channel part to other channels and the calibration is also copied.  

It would probably make sense for you all to start out with a "base" showfile, that has all of your scrollers patched to some channel.  If you have a rep plot, this works pretty well.  As you then move them around, the calibration information moves as well.  If you don't have a rep plot, it might be cleanest if you have a holding bin for them in higher numbered channels. 

Hope this helps. 

Hi there

I have to agree with everyone else, showing colour info for scrolls on the live display would be well wicked and useful, especially as there is the feature to build your own scrolls.

For those of you who are programming shows with lots of scrollers with different strings (eg: 130 scr's w/ 10 different types of strings), one possibilty could be to record each frame in to the colour pallet with the same gel number (eg: Lee200 = CP200, Rosco 78 = CP78).  That would make it easier to remember numbers so you don't have to rely on pages of direct selects.  If there are any double-ups in numbers (eg: L026 and R26) just record one of them as CP26.1

If you wanted you CP's to be in the same order as the frames (eg: CP1 = Frame 1, CP2 = Frame 2, etc) and using the example of 10 strings with each string containing 26 frames, you could record these as CP 1 >26 for the first set, CP 101 > 126 for the second set, etc.  Not sure if you can record above CP1000 so that may not work in that example.  Another idea would be CP 1.1 > 1.26 for the first type of sting, CP 2.1 > 2.26 for the second string and so on.  (you may need to record them actually as CP 1.01 > 1.26...not too sure)

All in all, the above ideas mean you can give each frame individual labels, and it should (hopefully) be a bit easier to remember the CP #'s and not have to rely on direct selects.  If you did use the example of CP1.01 > CP1.26 etc you could write 10 macros that are "CP1." "CP2." etc which may speed up things slightly, then all you'd have to do is enter the frame number. 

Just some food for thought.  Hope it's of some use

Cheers 

Cheers 

Hi there

I have to agree with everyone else, showing colour info for scrolls on the live display would be well wicked and useful, especially as there is the feature to build your own scrolls.

For those of you who are programming shows with lots of scrollers with different strings (eg: 130 scr's w/ 10 different types of strings), one possibilty could be to record each frame in to the colour pallet with the same gel number (eg: Lee200 = CP200, Rosco 78 = CP78).  That would make it easier to remember numbers so you don't have to rely on pages of direct selects.  If there are any double-ups in numbers (eg: L026 and R26) just record one of them as CP26.1

If you wanted you CP's to be in the same order as the frames (eg: CP1 = Frame 1, CP2 = Frame 2, etc) and using the example of 10 strings with each string containing 26 frames, you could record these as CP 1 >26 for the first set, CP 101 > 126 for the second set, etc.  Not sure if you can record above CP1000 so that may not work in that example.  Another idea would be CP 1.1 > 1.26 for the first type of sting, CP 2.1 > 2.26 for the second string and so on.  (you may need to record them actually as CP 1.01 > 1.26...not too sure)

All in all, the above ideas mean you can give each frame individual labels, and it should (hopefully) be a bit easier to remember the CP #'s and not have to rely on direct selects.  If you did use the example of CP1.01 > CP1.26 etc you could write 10 macros that are "CP1." "CP2." etc which may speed up things slightly, then all you'd have to do is enter the frame number. 

Just some food for thought.  Hope it's of some use

Cheers 

Cheers