Questions

[neil]

Hi everyone!

I have a show coming up soon and I have a few questions about the desk.

I am a frequent AVO user, but tend to do things off the subs, but this time I am going to be daring and 'busk' using pallets. So a few questions....

1) Can I break down ONE chase so that it changes when I hit the GO button. What I want to do is have some ACLs which I want to go on on various parts of the stage on cue.

2) My understanding of 'busking' is putting the desk into RUN. Then setting up a series of chases already there, then to change the gobo or the colour I select the fixture (like I do in PROGRAM mode) and then press the pallete button [ie colour red or gobo triangles etc] - the blue one under each fader. Is this correct? My theory is that I add in positions, colours and gobos to these preset buttons ready to create lots of different looks etc.

2a) If above is correct when I let go of the preset button what happens, does the shape/colour/gobo remain the same or do I need to keep my finger on it? Also are these LTP or HTP?

3) Can I create a 'BLACKOUT' fader/button by clearing the desk and programming whats up (nothing) into a sub? Will it blackout?

4) Is there a way of getting my movers into positon without a 'sweep'. If I want my movers in look 1 to stay on the back wall, but then a sweep FOH down on the audience. However I don't want a sweep from back wall to FOH. Is there a way I can do this?

I think thats it for now.

Many Thanks in advance.

Neil

[niclights]

1)
Yes. 'Unlink' chase steps via Edit Times menu.
If you do this from an 'unfolded' chase you can define for individual steps. Playback Add button will step through as well as the [Go] button. With unlinked steps you can also manually wheel through a xfade, including going backwards.

2)
For this you use Run Mode Takeover (not Normal).
When programming to allow interaction between Playback memories and palettes it is important to use Record By Channel (not Fixture). Be very specific about what information is stored. Editied values are represented with an 'm' in the display (ie. 1mFF). [Clear] removes all values from programmer.
To avoid confusion I always keep attributes stored in playbacks completely separate from those stored in palettes.
If you use the option 'Quick Palettes' you do not have to select fixtures when you want to apply a palette. This feature recalls all the information stored when no fixtures are selected. Similarly attributes are recalled by 'focus mask'. When 'Dimmer' attribute is selected, all attributes will recall.
Thus by programming only one attribute and one fixture type to any particular palette you can access palettes with only one button press, without worrying over fixture/attribute selection. Two button presses gives you a timed fade, which is nice! It also means you can use [clear] without worrying about deselecting fixtures.
You can also access palettes via the softbuttons from the Palette Menu.
With both methods timing information can be entered in seconds before applying the palette. If you are in the Palette Menu then timing information will remain until you enter a new value (or zero).

2a)
The palette is applied when you let go of the button. While still holding (Preset Add or Softbutton) you can cancel by pressing [focus]. You can also chose to filter the palette by only the fixtures contained in a particular playback by pressing the Playback Swop button.
Palettes can used for HTP and LTP attributes. The only difference is you cannot perform timed recalls on HTP palettes and they cannot exist in the programmer (or store) as references.
With LTP attributes the applied values will remain until new ones are selected. With HTP attributes the values willl remain until [clear] is pressed, at which point any HTP values contained in raised faders (preset or playback) will return.

3)
You can select fixtures (including normal dimmers) and set the value to zero by wheel or numerically and then store as a palette. Recalling palettes puts the information straight into the programmer and therefore will override anything coming from the playbacks, even though the attributes might be HTP. To regain control of any affected HTP channels you must press [clear]. All this would be quite odd though. Since most things that can blackout will be defined as HTP you would normally just lower the fader or any of the masters.

4)
The fixture has got to get there somehow. It is up to you how you make sure it is blacked-out. Either program a chase with position and dimmer along with the necessary timing or just do it manually - ie. black lamps out, select 'High' palette, enter 4 second fade, select 'Low' palette and fade in/out. Personally I go for the latter when busking since it keeps more playbacks clear for generics.

HTH

[neil]

thanks nick, thats very very helpful!

Is record my channel a default or something I have I have to set?

Also, something I have found with interesting results is that when I select one fixture and put it in a place then record the pallet, when I selet all fixtures the same and press the pallet only one moves into that position. Is this a fault or because the desk is in 'record by fixture'?

Sorry for all the questions, its made me realise how little I do actually know the desk.

[niclights]

Record by channel/fixture is set in User Settings. I fairly certain it is now available directly from the <shift> (Avo) key, but I can't find in the simulator so I'm not 100% - might have been implemented in one of the later builds.
I should have pointed out that the majority of this info is only relevant to 2004 software builds.

If you only store information for one fixture of a particular type in a palette then it should store as a 'shared' palette and recall over all fixtures of that type selected. Multiple 'shared' palettes can be overlayed for different types of fixture. This works irrespective of record by channel/fixture. Try deleting the palette first - it might have contained some other info. The does create a problem if you do actually want to only have that fixture stored/recalled. I have an option to store as shared or not, but I am not sure if this is available in release versions yet. The workaround is detailed in the manual and in one of my posts here.