Chapter 17. Cue Stack Options

The Cue Stack Window has three Views – View Cue Stack, View Options and View Defaults.

The View Options view shows the settings for the Cue Stack on the current Playback. Changing these settings immediately affects the currently selected Cue Stack.

The View Defaults view shows the settings that will be used when new Cues and Cue Stacks are recorded. Changing the settings in View Defaults does not affect Cues and Cues Stacks that have already been recorded.

The View Defaults view contains two columns – one for single step Cue Stacks and one for multiple step Cue Stacks. When the first Cue is first recorded on a Cue Stack the single step defaults are used. When a second Cue is recorded on the Cue Stack the Cue Stack settings are modified to use the multiple step defaults.

17.1. Faders

17.1.1. Fader activates stack

When set to Yes raising the fader from 0 to above the activation threshold activates the Cue Stack. When set to No the fader does not activate the Cue Stack.

The activation threshold defaults to 0. It is a global setting which is set in Setup, View Settings, Hardware.

17.1.2. Fader releases stack

When set to Yes lowering the fader to the activation threshold releases the Cue Stack. When set to No the fader does Not release the Cue Stack.

The activation threshold defaults to 0. It is a global setting which is set in Setup, View Settings, Hardware.

17.1.3. Fader controls HTP chans

When set to Yes the fader will control the level of all channels from the Playback that are patched as HTP channels.

When set to No then all HTP channels will be activated at 100% of the their level within the Playback, ignoring the level of the fader.

MagicQ personalities normally only have Intensity set as HTP channel - but it is sometimes useful to patch fixtures without Intensity as HTP – e.g. the Red, Green, Blue channels of LED fixtures.

The fader controls the levels proportionately from 0% to 100% through the length of the fader.

If the Cue includes FX on HTP channels then the size of the FX is also reduced proportionately according to the fader level.

When this setting is set to Yes then the other “Fader controls” settings should generally be set to No.

The overall intensity level of HTP channels is also affected by the Grand Master and the Sub Master and any active Group Masters.

17.1.4. Fader controls LTP (IPCB) chans

When set to Yes the fader will crossfade all channels that are operating as LTP channels (generally this is everything apart from Intensity).

When the fader is at 0% the LTP channels are not controlled by this Cue Stack. When the fader is raised above 0% then MagicQ crossfades the LTP channels to the values stored in the Cue under control of the fader.

When the fader is at 100% then the LTP channels are exactly as stored in the Cue.

MagicQ crossfades the LTP channels from the values that they were at before the fader was raised above 0 – i.e. the current value of these channels. This will either be the values from other Cue Stacks, or if no other Cue Stacks are controlling these channels the LTP or default values.

When set to Yes then the other “Fader controls” settings should generally be set to No.

If the setting Fader controls HTP is set to No, and the setting Advanced, All Channels Controlled LTP is set to Yes, then MagicQ will crossfade channels that are normally HTP as well such as Intensity.

17.1.5. Fader blocks FX on LTP chans

When the setting Fader controls LTP (IPCB) chans is set to Yes then this setting determines how FX running on those LTP channels are affected.

When set to Yes any channels that are under LTP control of the fader also block FX from other playbacks according to the level of the fader - at 100% they completely block FX

When set to No any FX on the channels from other playbacks keep running without change.

This setting has no effect when the setting Fader controls LTP (IPCB) chans is set to No.

17.1.6. Fader controls Absolute chans

When set to Yes the fader will control the value of all LTP chans in an absolute way - when the fader is at 0% then the channels are at 0% - when at 100% the channels are at the programmed value. This allows direct control of the attributes from the fader.

This is similar to Fader Controls LTP (IPCB) chans except that the crossfade always starts from 0% rather than the value from other Playbacks.

17.1.7. Fader controls FX size

When this setting is set to Yes the fader controls the size of any FX that are running in the Cue Stack – this includes FX from the current Cue and also any FX that are tracking from previous Cues in the Cue Stack.

When the fader is at 100% then the FX is the size that was recorded in the Cue - lowering the fader reduces the size until there is No size (No FX) at 0%.

Fader controls FX size affects FX on any attribute.

When set to Yes then the other “Fader controls” settings other than “Fader controls speed” settings should generally be set to No.

17.1.8. Fader controls FX speed

When this setting is set to Yes the fader controls the speed of any FX that are running in the Cue Stack – this includes FX from the current Cue and also any FX that are tracking from previous Cues in the Cue Stack.

When the fader is at 100% then the FX runs at the speed that was recorded in the Cue - lowering the fader reduces the speed until it stops at 0%.

Fader controls FX speed affects FX on any attribute.

When set to Yes then the other “Fader controls” settings other than “Fader controls size” settings should generally be set to No.

17.1.9. Fader controls manual crossfades

When set to Yes then the fader performs a manual crossfade on the Cue Stack in a similar way to the dedicated manual crossfader. This enables multiple Cue Stacks to be manually crossfaded.

All other “Fader controls” settings, especially "Fader controls HTP" should be set to No, otherwise there will be unpredictable results.

17.1.10. Fader controls timing

This setting controls timing of Cue Stack steps.

When the fader is at 0 the Cue Stack snaps with 0 time, when at full it fades with 10 seconds.

If the Cue has split timing then the split timing is respected within the overall fade time set by the fader.

17.1.11. Fader jumps to Cue Step

When set to Yes and the Cue Stack has multiple steps then raising the fader will step through the Cue Stack - at 0% it will be on step 1 and at 100% it will be on the last step.

17.1.12. Encoder mode

This setting is not currently used.

17.1.13. Control type

This setting is not currently used.

17.1.14. Control mode

This setting is not currently used.

17.2. Buttons

17.2.1. Flash activates stack

When set to Yes pressing the Flash button activates the Cue Stack and sets the level of the Playback to 100%.

When set to No pressing the Flash button sets the level of the Playback to 100% but does not activate the Cue Stack.

The overall level of HTP channels is also affected by the Grand Master and Sub Master and any active Group Masters. The Sub Master can be configured in Setup to be an Add Swap Master.

17.2.2. Flash releases stack

When set to Yes releasing the Flash button releases the Cue Stack and sets the level of the Playback to 0%.

When set to No pressing the Flash button sets the level of the Playback to 0% but does not release the Cue Stack.

Note that if the option Fader Activates Stack is set to Yes then releasing of the Playback is also dependent on the fader.

If the Playback was activated by raising the fader then pressing the Flash button will not release the Playback.

In this case the Playback will only be released by lowering the fader to 0% or by pressing the Rel button. This allows the Flash button to be used both to bump in a Cue which was not activated by fader, and to also bump a Cue to 100% which was activated by the fader at a lower level.

17.2.3. Flash always swaps

When set to Yes, pressing the Flash button will always act as a Swap rather than an Add, regardless of the state of the Add/Swap button.

When the button is pressed the Intensity of all other active Playbacks will be set to 0%. When the button is released the other Playbacks will be restored to their previous level.

When this option is set Yes then the LED in the Flash button will always be red.

17.2.4. Flash acts as Go/Pause

When set to Yes, pressing the Flash button acts as if the Go button had been pressed and pressing Shift + the Flash button acts as if the Pause button had been pressed. When set this way the button does not act as a bump button.

When set to No the Flash button acts as a bump button in the normal way.

Holding Shift and pressing Flash will perform Pause instead of Go.

When set to Yes the settings “Flash activates Stack”, “Flash releases Stack” and “Flash toggles” are ignored.

17.2.5. Flash acts as Flash + Go

When set to Yes the Flash button acts as both a Flash button and a Go button.

Pressing the Flash button performs the Go function – this will active the Cue Stack, or if the Cue Stack is already active, it will Go to the next step. At the same time the Flash button will operate in the Normal way, setting the Playback level to 100%.

Releasing the Flash button will set the Playback level back to 0% or if the fader is raised to the level of the fader.

Holding SHIFT and pressing the Flash button will perform Flash + Pause.

Normally when “Flash acts as Flash + Go” is set Yes then the setting “Flash Releases Stack” should be set to No. If the option “Flash Releases Stack” is set to Yes then releasing the Flash button will also release the Playback unless the fader is raised.

When set to Yes, the setting “Flash acts as Go/Pause” is ignored.

17.2.6. Flash toggles

When set to Yes the Flash button acts as a toggle rather than a bump. Pressing the button the first time activates the Playback. Pressing the button again releases the Playback.

When this option is set and the playback is active the LED in the Flash button flashes to indicate the toggle mode is latched.

When set to Yes, the settings “Flash activates Stack” and “Flash releases Stack” are ignored.

17.2.7. Flash acts like fader

When set to Yes the Flash button has the same effect as if the fader has temporarily been raised to 100%. This is useful for enabling the Flash button to control attributes other than Intensity.

For example, if the fader is set to control FX size then pressing the Flash button would act like the fader being fully raised – so 100% FX size.

17.2.8. Go jumps out of loop

This setting affects Cues that are set to Chase Timing which are in a loop.

When set to Yes, pressing Go will exit the loop – jumping to the step after the Cue that loops back to an earlier Cue.

When set to No, pressing Go will step one step within the chase.

17.2.9. Go stop/starts

When set to Yes then pressing GO stops a Cue that is already running or starts a Cue that is stopped.

When set to No then pressing GO starts the next Cue.

17.2.10. Go uses Exec Grid 1

This enables the GO button on Playbacks 1 to 10 to control the first ten items in Exec Grid 1.

When set to Yes then pressing the GO button toggles the Exec Grid item corresponding to this Playback - for example GO on Playback 2 will toggle item 2 in Execute Grid 1.

When set to No the GO button acts normally.

17.2.11. Pause swaps

When set to Yes the Pause button acts as a Flash button in Swap mode.

Pressing the Pause button the Playback will be set to 100% and the Intensity of all other active Playbacks will be set to 0%. When the button is released the other Playbacks will be restored to their previous level.

This setting enables a Playback to have both an Add button and a Swap button.

17.2.12. Pause releases

When set to Yes the Pause button releases the Cue Stack.

17.2.13. Pause uses Exec Grid 1

This enables the Pause button on Playbacks 1 to 10 to control items 11 to 20 in Exec Grid 1.

When set to Yes then pressing the Pause button toggles the Exec Grid item corresponding to this Playback - for example Pause on Playback 2 will toggle item 12 in Execute Grid 1.

When set to No the Pause button acts normally.

17.3. Function

17.3.1. Cue Stack is an Intensity Master

When this setting is set to Yes then the Cue Stack behaves as an Intensity Master. The Cue Stack normal Cue execution behaviour is disabled.

The Group Id settings specifies the group of channels that are under control of the Intensity Master. Updating the channels stored within the specified group updates the channels under control of the FX Size Master.

If the Group ID is 0 or refers to an invalid group, then the channels stored in the first Cue are used to determine which channels are under control of the Intensity Master. The levels of the channels in the first Cue are not important – only that the channels are present at some level in the Cue.

In order for the Intensity Master to be activated the Go button must be pressed. To release the Intensity Master the Playback must be selected and the REL button pressed. The Button settings “Flash activates Stack” and “Flash releases Stack” are ignored. In order to avoid sudden changes in output level the fader should be raised to 100% before activating or releasing.

When the fader is at 100% then the Intensity Master has no effect. As the fader is lowered then all the channels under control have their intensity reduced.

It is possible to have multiple Intensity Masters that control the same channel which work proportionately.

Normally when this setting is set to Yes, the settings Cue Stack is a Size Master and Cue stack is a Speed Master should be set to No.

When this setting is set to No then the Cue Stack behaves normally.

17.3.2. Cue Stack is a Size Master

When this setting is set to Yes then the Cue Stack behaves as an FX Size Master. The Cue Stack normal Cue execution behaviour is disabled.

The Group Id settings specifies the group of channels that are under control of the FX Size Master. Updating the channels stored within the specified group updates the channels under control of the FX Size Master.

If the Group ID is 0 or refers to an invalid group, then the channels stored in the first Cue are used to determine which channels are under control of the Size Master. The levels of the channels in the first Cue are not important – only that the channels are present at some level in the Cue.

In order for the Size Master to be activated the Go button must be pressed. To release the Size Master the Playback must be selected and the REL button pressed. The Button settings “Flash activates Stack” and “Flash releases Stack” are ignored. In order to avoid sudden changes in output level the fader should be raised to 100% before activating or releasing.

When the fader is at 100% then FX size is as programmed. As the fader is lowered then the FX size is reduced until it reaches zero size at 0%.

A particular channel can only be controlled from one FX Size Master.

Normally when this setting is set to Yes, the setting Cue Stack is an Intensity Master should be set to No. It is possible to have a Cue Stack set to both a Size Master and a Speed Master.

When this setting is set to No then the Cue Stack behaves normally.

17.3.3. Cue Stack is a Speed Master

When this setting is set to Yes then the Cue Stack behaves as an FX Speed Master. The Cue Stack normal Cue execution behaviour is disabled.

The Group Id settings specifies the group of channels that are under control of the FX Speed Master. Updating the channels stored within the specified group updates the channels under control of the FX Speed Master.

If the Group ID is 0 or refers to an invalid group, then the channels stored in the first Cue are used to determine which channels are under control of the Speed Master. The levels of the channels in the first Cue are not important – only that the channels are present at some level in the Cue.

In order for the Speed Master to be activated the Go button must be pressed. To release the Speed Master the Playback must be selected and the REL button pressed. The Button settings “Flash activates Stack” and “Flash releases Stack” are ignored. In order to avoid sudden changes in output level the fader should be raised to 100% before activating or releasing.

When the fader is at 100% then FX size is as programmed. As the fader is lowered then the FX speed is reduced until it stops at 0%.

A particular channel can only be controlled from one FX Speed Master.

Normally when this setting is set to Yes, the setting Cue Stack is an Intensity Master should be set to No. It is possible to have a Cue Stack set to both a Size Master and a Speed Master.

When this setting is set to No then the Cue Stack behaves normally.

17.3.4. Group ID (0 is not used)

This setting is used when the Cue Stack is an Intensity Master, FX Size Master or FX Speed Master. It specifies the group to use for the Master.

When set to zero the Master will use the data in the first Cue of the Cue Stack to determine which heads are controlled by the master.

17.3.5. Group Attributes

This setting is used when the Cue Stack is an FX Size Master or FX Speed Master and the Group ID is non zero. It specifies which attributes the FX Speed or FX Size master should control for the heads in the Group.

The Group Attributes defaults to all attributes. The options are All, Pos, Pan, Tilt, Col, Int, Zoom.

If the Group ID is zero or invalid then this setting is not used and MagicQ uses the data in the first Cue of the Cue Stack to determine which heads and attributes are controlled by the master.

17.3.6. Cue stack is a Prog Master

The Playback with this Cue Stack operates as a Programmer Master. The Programmer master enables level control of the contents of the Programmer on the fader and stepping between different Programmer states.

See Programmer Master.

17.3.7. Intensity Master to 200%

When Cue Stack is an Intensity Master is set to yes, then the fader will operate from 0% to 200% intensity. Above 100% the level recorded in the Cue will be boosted - although the maximum output level will always be 100%.

17.3.8. Col Tag

When a Col Tag is set for a Cue Stack then that Col Tag is shown in the Playback legend above the Playback faders and buttons.

The RGB LEDs on the MQ500 and Stadium Wing playbacks can be set to show the colour of the Col Tags in Setup, View Setting, Windows, Playback Col Tags.

17.4. Activate/Release

17.4.1. Halt at last step

When set to Yes the Cue Stack halts at the last step in the Cue Stack.

When set to No then the Cue Stack will return to the first step after the last step.

17.4.2. Release after last step

When set to Yes the Cue Stack automatically releases after the last step in the Cue Stack has completed fading.

When set to No the Cue Stack must be released manually.

17.4.3. Release resets to first step

When set to Yes the Cue Stack always starts from the first step when the Cue Stack is activated. The setting “Release steps 1 step” is ignored.

When set to No the Cue Stack activates at the step it was on when it was last released.

17.4.4. Release steps 1 step

When set to Yes the Cue Stack activates at the step following the step the Cue Stack was on when it was last released.

When the setting “Release resets to first step” is set to Yes, this setting has no effect.

17.4.5. Release time

This is the time for channels to release when the Cue Stack is released (using the REL button or via fader/flash button). The exact behaviour depends upon whether channels are active on other Playbacks. Intensity channels not used by other channels will fade out using the release time.

The release time also affects channels that are released from Cue steps within a Cue Stack step – i.e. when the Cue Stack step Tracking option is not set to LTP (“Rel old chans” = yes)

This setting can also be set in the End field in View Cue in the Cue Stack Window.

17.4.6. Release attributes

This setting determines which attributes are released with time when a Cue Stack is released with time.

Individual attribute types - "Int", "Pos", "Col", "Beam" can be selected together with combinations.

The default is "All" which will fade out all attribute types except for attributes that are set to Instant.

17.4.7. Release Executes Last Step

When the Playback is released then MagicQ executes the last step of the Cue Stack before releasing. Any macros in the last step of the Cue Stack are also executed.

It affects all releases including releasing by flash button, fader to 0% or RELEASE button.

This can be used with a Release Time on the Cue Stack to perform a fade out of a different look when the Cue Stack is released.

17.4.8. Activate on page change

When set to Yes, then this Cue Stack is activated when the page is changed to the page that this Cue Stack is assigned to.

If there is an active Cue Stack on this Playback then the new Cue Stack will only be activated if the old Cue Stack is set to release on page change.

17.4.9. Release on page change

When set to Yes, then this Cue Stack is released when the page is changed to any page other than the page that this Cue Stack is assigned to.

17.4.10. HTP always active (Use HTP)

When set to Yes then the fader always controls the Intensity (HTP) channels from the Cue Stack regardless of whether the Cue Stack is activated. Whenever the fader is raised above zero the Intensity channels will affect the Output. The highest level from this Cue Stack and any other Playbacks will determine the Output level for each channel.

This setting overrides the Advanced Setting “All Channels controlled LTP”.

This setting is similar to the Use HTP setting on some other consoles.

17.5. Advanced

17.5.1. All chans controlled LTP

When set to Yes all HTP channels under control of the Playback act as if they were LTP channels. When the Playback with this Cue Stack is the latest activated and highest priority Playback then the Playback has complete control of all HTP channels regardless of whether they are active on other faders.

HTP channels that are active on higher priority Playbacks will be under control of the higher priority Playback and will ignore this setting.

HTP channels that are active on other Playbacks with the same priority, but which were activated/reasserted more recently than this Playback, will be under control of the other Playbacks.

17.5.2. Block FX from other playbacks

When set to Yes then any channels controlled by this Playback block FX on those channels from other Playbacks.

Channels controlled by this Playback that have levels but no FX are not affected by FX on other Playbacks. In effect an implicit zero FX is added to these channels to block the other Playbacks.

When set to No then channels controlled by this Playback that have levels but no FX are affected by FX on those channels from other Playbacks.

17.5.3. Masters affect level

When set to Yes then the levels of HTP channels (generally Intensity) are affected by the grand master and sub master faders. Channels also are affected by DBO and can be released by SHIFT RELEASE.

When set to No then the levels of HTP channels are not affected by the grand master and sub master faders. They are also not affected by DBO or by SHIFT RELEASE and will not be automatically activated and released by timecode.

Note that Group Masters are not affected by this setting. Therefore even with “Masters affect level” set to No, channels will still be affected by Group Masters.

17.5.4. Playback priority

The Playback priority can be set to Normal, Mid, High, Programmer and Above Programmer.

When all Playbacks are set to priority Normal then the latest Playback to be activated/reasserted will control the channels.

Playbacks set to Mid priority always have higher priority than Playbacks set to Normal priority.

Playbacks set to High priority always have higher priority than Playbacks set to Normal or Mid priority.

Playbacks set to Programmer priority have the same priority as the programmer but always have higher priority than Playbacks set to Normal, Mid or High priority.

Playbacks set to Above Programmer have higher priority than the Programmer – in order to edit the Cues in the Programmer and see the changes on the Output it is best to release the Cue Stack.

17.5.5. Move when dark

When set to Yes, then MagicQ checks after each Cue is executed whether it should perform a move when dark.

Any heads that are used in the next Cue but which have 0% intensity in the current Cue are checked to see whether the Position, Beam and Colour attributes should be preloaded before the next Cue is executed. If the Position, Beam or Colour values are different from the current values then the new values are crossfaded with a time of 3 seconds.

This option is similar to putting a Mark Cue before every Cue in a Cue Stack.

17.5.6. Recalculate state on jumps

This option specifies how MagicQ calculates the Cue State when playing back a Cue Stack.

When set to Yes, MagicQ recalculates the Cue State whenever a jump is made in the Cue Stack. The Output of a particular Cue always appears the same regardless of which Cue was executed preciously. MagicQ recalculates the Output as if the Cue Stack had been played back from the first Cue to this Cue by pressing the GO button.

When set to No, MagicQ calculates the Cue State based on the Cues that it has actually executed – when jumping to a new Cue only the Cues that have been previously executed will make up the Output.

In tracking modes this setting defaults to Yes. In non-tracking modes this setting defaults to No.

17.5.7. Stomp other playbacks

Stomping enables Playbacks that have been completely overridden by other Playbacks to be automatically released.

This option only has an effect when the Setup, Playback setting “Stomp Playbacks” is set. When “Stomp Playbacks” is set to No then this setting is ignored.

When this setting is set to Yes then this Playback is allowed to stomp other Playbacks.

When this setting is set to No then this Playback will not stomp other Playbacks - this can be useful when bumping in stabs and temporary FX.

17.5.8. Sync next Playback to this one

This setting enables one or more playbacks to be synchronised together so that they step the same Cue Ids at the same time.

Setting this option to Yes forces the next Playback (higher number) to synchronise to this Playback.

If enabled for playback PB10 then Wing 1 PB1 will be synced to it.

If you Go on this playback to a Cue Id that is not implemented on the next playback then the next playback will not change step. It will only sync to steps where the Cue Ids match.

It is possible to synchronise multiple playbacks by enabling this setting on several adjacent playbacks. In this case all the adjacent playbacks are synced to the first playback in the adjacent playbacks.

It is not neccessary for each of the adjacent playbacks to have all the Cues - each adjacent playback syncs independently to the first adjacent playback ignoring the Cues of any intermediate adjacent playbacks.

17.5.9. External timecode

This setting affects any steps in this Cue Stack that have their Halt field set to “Timecode.

When set to Yes this Cue Stack is controlled by external timecode. When set to No then this Cue Stack is controlled by internal timecode – activating the Playback starts the timecode from 0.

This setting can also be changed from an encoder soft button.

17.5.10. Timecode offset

This can be used to add a positive or negative timecode offset to all timecode values within a Cue Stack including all TC Tracks associated with that Cue Stack.

For example if the Cues in the Cue Stack have been set to respond to timecode starting at 0/0/0 and the timecode received actually starts at 2/0/0 then setting the timecode offset to 2/0/0 will make the Cue stack correctly respond to the received times.

Similarly if the CueStack has been set to respond to timecode starting at 5/0/0 and timecode is actually received starting at 0/0/0 then setting a timecode offset of -5/0/0 will have the desired effect.

Note that all the Cues will still show their programmed timecode values but an offset will be applied when playing back or recording timecode. The titlebar of the Cue Stack Window shows the offset.

17.5.11. Send playback state to other consoles

When set to Yes then the state of this Playback is sent to other MagicQ consoles on the network.

If Net Sessions, Playback sync is set then the state of all Playbacks is sent to other consoles regardless of this Cue Stack setting, so this setting should be set to No.

This setting requires Setup, Network, Ethernet Remote Protocol to be set to “ChamSys TX” or “ChamSys TX and RX”.

17.6. Chase Options

17.6.1. Skip first times

When this setting is set to Yes, then when the Cue Stack is activated the fade times for the first step are ignored and the levels bumped straight in.

This only affects Cue steps set to “Chase Timing”.

17.6.2. Speed

This controls the speed of any Cue Steps in the Cue Stack set to “Chase Timing”. This setting can also be controlled via encoder X in the Cue Stack view.

17.6.3. Xfade

This controls the crossfade of any Cue Steps in the Cue Stack set to “Chase Timing”. This setting can also be controlled via the Y encoder in the Cue Stack view.

17.6.4. Direction

This controls the direction (forward or backward) of any Cue Steps in the Cue Stack set to “Chase Timing”. This setting can also be controlled via encoder C in the Cue Stack view.

17.6.5. Repeat type

The options are Normal, Bounce and Random. Bounce executes the Chase alternating backward and forward direction. This setting can also be controlled via encoder D in the Cue Stack view.

17.6.6. Number of repeats

This setting specifies how many repeats of the Chase should take place.

When set to 0 then the Chase will continue until the chase is exited manually.

17.6.7. Running

This setting specifies whether Chases start running or halted.

17.7. Chase Times

17.7.1. HTP in fade, HTP out fade, Position fade, Colour fade, Beam fade

The fade times for any Cue Steps in the Cue Stack set to “Chase Timing”. These times generally match the Chase speed. These times can also be controlled via encoder C in the Cue Stack view.

Setting one or more attribute group fade times to 0 causes that attribute group to snap rather than fade.

The overall Chase speed corresponds to attribute group with the biggest combined delay and fade time.

HTP in delay, HTP out delay, Position delay, Colour delay, Beam delay

The delay times for any Cue Steps in the Cue Stack set to “Chase Timing”.

These times can be used to make one or more attribute groups snap at end.

The overall Chase speed corresponds to attribute group with the biggest combined delay and fade time.

17.8. Audio

17.8.1. Audio controls fader level

When set to Yes, the level of the playback is controlled by the received audio level on the chosen. The level of the real fader is ignored. The effect on the Playback is determined by the Cue Stack, Fader settings.

The Cue Stack must be active for the audio to take effect.

When this setting is set to Yes, the settings “Audio Bumps Go” and “Audio sets BPM” should be set to No.

The setting can be used in conjunction with the setting “Audio jumps to Cue Step”.

The audio level, audio parameter 1, and audio parameter 2 settings can be used to fine tune how the received audio affects the fader level.

17.8.2. Audio bumps Go

When set to Yes, the Cue Stack bumps to the next step every time a peak in the audio is detected on the specified channel. This enables a Cue Stack to follow the beat of the music.

This is best used with the Cue Stack set to Cue Timing instead of Chase Timing.

The Cue Stack must be active for the audio to take effect.

When this setting is set to Yes, the settings “Audio controls fader level”, “Audio sets BPM” and “Audio jumps to Cue Step” should be set to No.

Audio parameter 1 is used as a divider – set it between 2 and 16 to divide the received beat frequency by a value between 2 and 16 times.

Audio parameter 2 should be set to 0.

17.8.3. Audio sets BPM

When set to Yes, then the chase speed of the Cue Stack is set to the timing of the peaks on the specified audio channel. The Cue Stack should be set to Chase Timing.

The Cue Stack must be active for the audio to take effect.

When this setting is set to Yes, the settings “Audio controls fader level”, “Audio bumps Go” and “Audio jumps to Cue Step” should be set to No.

Audio level, audio parameter 1, and audio parameter 2 should be set to 0.

17.8.4. Audio jumps to Cue Step

“Audio jumps to Cue Step” enables the level of the specified audio channel to determine which step in the Cue Stack is executed – for example if you have a Cue Stack with 10 steps, then a level of 0% will execute step 1, 10% will execute step 2 whilst a level of 100% will execute step 10. This is very useful if you wish to program different Cues onto LED or media servers.

The Cue Stack must be active for the audio to take effect.

When this setting is set to Yes, the settings “Audio bumps Go” and “Audio jumps to Cue Step” should be set to No.

If the setting “Audio Controls fader level” is set to YES then audio level, audio parameter 1, and audio parameter 2 will affect the level of the Playback and hence the Cue step chosen.

17.8.5. Audio channel

This setting specifies the audio channel that the Playback will respond to.

The ChamSys audio interface supports 7 different frequency bands on two audio inputs (left and right).

Selecting the option “Energy” uses all frequency bands mixed together.

17.8.6. Audio level

When “Audio controls fader level” is set to Yes then the settings Audio parameter 1 and Audio Parameter 2 can be set to control the response:

Audio P1 = 0 Normal (direct trigger from level)

Audio P1 = 1 Decayed (decays by Audio P2 each sample)

Audio P1 = 2 Pulse (triggers at Audio Level, Audio P2 is duration of pulse)

Audio P1 = 3 Pulse decay (triggers at Audio Level, decays by Audio P2 each sample)

Audio P1 = 4 Switch (triggers to on/off at Audio Level)

Audio P1 = 5 Slow (increases/decreases by Audio P2 each sample)

These parameters are ignored for the settings “Audio Bumps Go” and “Audio sets BPM”, and “Audio jumps to Cue Step”

When the setting “Audio Bumps Go” is set to Yes, then Audio P1 acts as a divider - from 2 to 64 so that the Cue Stack is bumped at a slower rate than the audio input.

17.8.7. Audio parameter 1

Audio P1 = 0 Normal (direct trigger from level)

Audio P1 = 1 Decayed (decays by Audio P2 each sample)

Audio P1 = 2 Pulse (triggers at Audio Level, Audio P2 is duration of pulse)

Audio P1 = 3 Pulse decay (triggers at Audio Level, decays by Audio P2 each sample)

Audio P1 = 4 Switch (triggers to on/off at Audio Level)

Audio P1 = 5 Slow (increases/decreases by Audio P2 each sample)

17.8.8. Audio parameter 2

Audio P2 is dependent on Audio P1

Audio P1 = 1 Decayed (decays by Audio P2 each sample)

Audio P1 = 2 Pulse (triggers at Audio Level, Audio P2 is duration of pulse)

Audio P1 = 3 Pulse decay (triggers at Audio Level, decays by Audio P2 each sample)

Audio P1 = 5 Slow (increases/decreases by Audio P2 each sample)

17.8.9. Rate Divisor

Cue Stacks can be set to use a divisor of the tapped time - by default it is set to "Normal" and takes the tapped time. Options include "Div by 2" to "Div by 8" and "Mult by 2". The divisor affects setting of the rate by tap to time either as the selected playback, as part of global tap to time, or as part of audio BPM rate setting.

Cue Stacks can also have the Rate Divisor can be set to "Inhibit" - in this case the rate of the Cue Stack is never affected by global tap to time options. This allows Global Tap to Time to be used without affecting particular Cue Stacks.

17.8.10. Audio file

This specifies an audio file to be associated with the Cue Stack.

17.8.11. Audio play mode

In "Normal" mode, the audio file specified will play upon the playback being activated, and stops when deactivated.

In "Stack Audio Muted" mode, the audio file will be shown in the Audio Timeline window to allow timecode based Cue Stacks to be modified visually, but MagicQ won’t play back the audio itself. This mode is used when you are receiving timecode from an external system which is playing the same audio file and providing a timecode source to MagicQ.

17.9. Step (View Defaults only)

17.9.1. Step controlled as a chase

When set to Yes, the step defaults to Chase timing. When set to No the step defaults to Cue timing.

17.9.2. Step follows last

When set to Yes, the step executes after the completion of the previous step. When set to No the step executes after the wait time specified in the Cue step.

17.9.3. Step halts before executing

When set to Yes, the step halts and waits for the user to pres GO before executing the Cue step.

When set to No the step executes immediately after the previous step has completed – this is either after it has completed fading (when “Step follows last” is set to YES) or immediately after the wait time has expired.

When “Step Controlled as Chase” is Yes then this setting is normally set to No so that the chase runs step to step without user interaction.

When “Step Controlled as Chase” is No then this setting is normally set to Yes so that the Cue Stack is executed step by step under user control.

17.9.4. Zero old HTP (from previous steps)

When set to Yes, any HTP channels from previous Cues that are not in this Cue step are faded out.

In tracking modes this setting defaults to No. In non-tracking mode this setting defaults to Yes.

The Tracking flag “H” corresponds to the inverse of this setting.

17.9.5. Zero old FX (from previous steps)

When set to Yes, any FX on channels from previous Cues that are not controlled by a FX in this Cue step have the FX faded out.

In tracking modes this setting defaults to No. In non-tracking mode this setting defaults to Yes.

The Tracking flag “F” corresponds to the inverse of this setting.

17.9.6. Release old chans

When set to Yes, any channels used in previous Cues but not used in this Cue step are released.

This setting defaults to No in all modes.

The Tracking flag “L” corresponds to the inverse of this setting.

17.10. Step Times (View Defaults only)

17.10.1. HTP in fade

The default fade times used when new Cues are recorded in a Cue Stack. Used by Cues in the Cue Stack set to “Cue Timing”.

Once Cues have been recorded then the times for Specific Cues are edited in the Cue Window, View Times.

17.10.2. HTP out fade

The default fade times used when new Cues are recorded in a Cue Stack. Used by Cues in the Cue Stack set to “Cue Timing”.

Once Cues have been recorded then the times for Specific Cues are edited in the Cue Window, View Times.

17.10.3. Position fade

The default fade times used when new Cues are recorded in a Cue Stack. Used by Cues in the Cue Stack set to “Cue Timing”.

Once Cues have been recorded then the times for Specific Cues are edited in the Cue Window, View Times.

17.10.4. Colour fade

The default fade times used when new Cues are recorded in a Cue Stack. Used by Cues in the Cue Stack set to “Cue Timing”.

Once Cues have been recorded then the times for Specific Cues are edited in the Cue Window, View Times.

17.10.5. Beam fade

The default fade times used when new Cues are recorded in a Cue Stack. Used by Cues in the Cue Stack set to “Cue Timing”.

Once Cues have been recorded then the times for Specific Cues are edited in the Cue Window, View Times.

17.10.6. HTP in delay

The default delay times used when new Cues are recorded in a Cue Stack. Used by Cues in the Cue Stack set to “Cue Timing”.

Once Cues have been recorded then the times for Specific Cues are edited in the Cue Window, View Times.

17.10.7. HTP out delay

The default delay times used when new Cues are recorded in a Cue Stack. Used by Cues in the Cue Stack set to “Cue Timing”.

Once Cues have been recorded then the times for Specific Cues are edited in the Cue Window, View Times.

17.10.8. Position delay

The default delay times used when new Cues are recorded in a Cue Stack. Used by Cues in the Cue Stack set to “Cue Timing”.

Once Cues have been recorded then the times for Specific Cues are edited in the Cue Window, View Times.

17.10.9. Colour delay

The default delay times used when new Cues are recorded in a Cue Stack. Used by Cues in the Cue Stack set to “Cue Timing”.

Once Cues have been recorded then the times for Specific Cues are edited in the Cue Window, View Times.

17.10.10. Beam delay

The default delay times used when new Cues are recorded in a Cue Stack. Used by Cues in the Cue Stack set to “Cue Timing”.

Once Cues have been recorded then the times for Specific Cues are edited in the Cue Window, View Times.

17.11. FX (View Defaults Only)

Default speed

This is the default FX speed used when creating new Waveform FX in the FX Editor Window.

17.11.1. Default in fade

This is the default FX fade in used when setting a specific FX fade in time. Note that by default FX are faded in using the fade times of the Cue step.

17.11.2. Default out fade

This is the default FX fade in used when setting a specific FX fade out time. Note that by default FX are faded out using the fade times of the Cue step.