Chapter 46. Settings

MagicQ supports a large number of settings that the user is free to change. These settings are divided into two categories – show settings and console settings. Show settings are settings that the user may wish to change on a show by show basis, whereas console settings are associated with the specific console and its connectivity to external devices.

Show Settings

Console Settings

Both show settings and console settings are stored in MagicQ show files, but by default only show settings are loaded when a MagicQ show is loaded. To force consoles settings to be loaded as well use SHIFT and LOAD SHOW+CON.

In MagicQ, console settings are marked with a red tag in the bottom right corner of the text box describing the setting.

46.1. Programming Mode

The MagicQ console allows the programming mode to be configured in the Setup Window. The modes control several of the different settings of the console. All of the settings can be configured individually – however, the modes make it easy to change between the most frequently used settings.

The programming mode determines how the console is programmed. The options are Normal, Theatre non-track, Theatre tracking and Hog II Warp. Most users will choose Normal.

Changing mode during programming does not change Cue Stacks that have already been programmed – it only affects the programming of new Cue Stacks.

The setting affected by changing mode are:

Table 46.1. Setup, Prog Settings

SettingNormal(live)Theatre non trackTheatre TrackHog II warp

Programmer Tracking

No

No

Yes

Yes

Unused Chans return to defaults

No

Yes

Yes

Yes

Programmer overrides FX

No

No

No

Yes

Highlight mode

Normal

Advanced

Advanced

Advanced

Fan mode

Normal

Normal

Normal

No toggle

Select multiple groups

No

Multiple

Multiple

Multiple

Recording to Palettes

Selected

Selected

Selected

All heads


Table 46.2. Setup, Keypad Encoders

SettingNormal(live)Theatre non trackTheatre TrackHog II warp

Select heads on keypad intensity set

Yes

Yes

Yes

Yes

Select heads and palettes from keypad

No

Yes

Yes

Yes

Keypad always selects heads

No

No

No

Yes

Maintain encoders as Pos, Col, Beam

No

No

No

Yes

Keypad Syntax – Theatre Patch

No

Yes

Yes

No


Table 46.3. Setup, Windows

SettingNormal(live)Theatre non trackTheatre TrackHog II warp

Always Show Record Options

No

No

No

Yes


Table 46.4. Setup, Cue Stack Defaults, Fader

SettingNormal(live)Theatre non trackTheatre TrackHog II warp

Fader activates

Yes

No

No

No

Fader releases

Yes

No

No

No


Table 46.5. Setup, Cue Stack Defaults, Flash

SettingNormal(live)Theatre non trackTheatre TrackHog II warp

Flash activates

Yes

No

No

No

Flash releases

Yes

No

No

No


Table 46.6. Setup, Cue Stack Defaults, Step

SettingNormal(live)Theatre non trackTheatre TrackHog II warp

Multi Cue, Controlled as chase

Yes

No

No

No

Multi Cue, Step halts before executing

No

Yes

Yes

Yes

Multi Cue, Zero Old HTP

Yes

Yes

No

No

Multi Cue, Zero Old FX

Yes

Yes

No

No

Track

L

L

HLF

HLF


Table 46.7. Setup, Cue Stack Defaults, Step Times

SettingNormal(live)Theatre non trackTheatre TrackHog II warp

HTP in, HTP out, Pos times

0s

3s

3s

3s


For changing between tracking and non-tracking mode simply change the “Programmer Tracking” setting in the Setup Window, “Prog” tab. This automatically sets the Default Cue Stack options (Recalculate state on jumps, Zero old HTP, Zero old FX) correctly.

46.2. Playback Mode

The playback mode determines how the console plays back cues. The options are Normal and Safe. In Normal mode the user can make changes during playback just like when they were programming the show. In Safe mode, making changes is not allowed and backups are turned off to any possible interference with the running of the show.

46.3. Advanced Settings Option

The MQ40/MQ40N user interface has a reduced number of options to ensure that it is easy to use for users unfamiliar with lighting programs. More advanced users can access the advanced settings by setting the Advanced Settings = "Enabled" in Setup, View Settings, Mode.

When "Advanced Settings" is "Disabled" then the Patch Window shows a simplified view with one only one tab and simple buttons to CHOOSE HEAD and PATCH IT. Items can be moved around in the Visualiser using the X, Y, Z encoders. For more advanced features of MagicVis, and for patch features like Clone and Morph use Advanced Settings.

From 1.8.0.2 on all MagicQ consoles the Advanced Setting option is saved and will appear on start up and reset as it was before the start up or reset. On older versions of software whenever the MQ40N or MQ40 was first started or reset then it defaulted back to the simple settings - this was intentional to ensure that basic users saw the simple settings on start up and were not confused by all the advanced features.

46.4. Output Settings

The console universes can be configured to use different protocols. Outputs must be configured and enabled before the console will output data. To set up outputs, open the Setup Window and select the VIEW DMX I/O view.

MagicQ software supports 64 universes but older versions of MagicQ support less universes. To change the number of universes in operation please see Configuring number of universes.

46.4.1. Configuring Output Universes

For each of the universes, the output and input protocol can be selected in the Out Type and In Type fields respectively. Press ENTER or double click to change to the next protocol type.

image

The possible protocols are

Table 46.8. DMX I/O Out Protocols

None

No protocol

Art-Net

Art-Net, Art-Net II and Art-Net III protocols (over Ethernet)

Pathport

Pathport protocol (over Ethernet)

Show Net

Show net protocol (over Ethernet)

ACN

ACN Streaming DMX (over Ethernet)

MQ Direct Direct

DMX outputs from MagicQ Pro and Expert consoles

MQ Wing

DMX outputs on MagicQ PC wing, Mini Wing or Maxi Wing

MQ Dual DMX

MagicQ Dual DMX interfaces

MagicDMX

ChamSys MagicDMX USB interface

Enttec Pro/Lumen Radio

Enttec Pro dongle/Lumen Radio Nova wireless

Dig Enlight

Digital Enlightenment dongles

Peperoni

Peperoni dongles and devices

DMX4ALL

DMX4ALL devices

USBDMX

USBDMX devices

Velleman

Velleman K8062

Nicholaudie

Nicholaudie / Sunlight devices


MagicQ Dual DMX modules, MagicDMX interfaces and SnakeSys Ethernet to DMX Interfaces use their own internal processor to ensure correct DMX framing at high DMX refresh rates.

For network protocols such as Art-Net and Pathport it is necessary to set up the Out Uni and In Uni fields - these determine which the ID of the Universe when carried over Ethernet. These need to be set up to match the Ids configured on the Ethernet Interface boxes.

Where large numbers of universes are being carried over Ethernet it may also be necessary to configure the Art-Net subnet ids. Enter subnet ids using the syntax 1-0 for subnet 1 universe 0. The subnet ids default to 0.

A ! by a Universe indicates a clash whereby more than one Universe is being output on the same network Universes.

46.4.2. Using Art-Net II

To use Art-Net II simply configure the Output Universe type to Art-Net and then set the following options:

Each Universe on MagicQ can be set to Unicast to a specific IP address rather than broadcast as in Art-Net I. The IP addresses of Art-Net compliant devices on the network can be viewed in Setup Window, View System, View Status, Art-Net nodes.

Two Unicast addresses are provided - this allows for redundancy. Note that using both Unicast addresses doubles the amount of network traffic.

When a Unicast address is set up got a Universe set to Output Art-Net, MagicQ sends data for that universe direct to the unicast address rather than broadcasting that universe. Note that MagicQ will still broadcast that universe once per second - this allows all other consoles on the network to determine that there is a console outputting ArtnNet for this universe. This additional broadcast can be inhibited by setting Setup, View Settings, Hardware, Reduced Rate DMX to "M+C no broadcast".

46.4.3. Using ACN Streaming DMX

ACN Streaming DMX uses multicast to output DMX data onto the network. When using many universes this often provides a much better solution that using Art-Net in broadcast mode. In ACN Streaming DMX nodes only decode the universes they are interested in rather than having to decode all the universes broadcast on the network.

From v1.7.1.1 MagicQ supports unicast of ACN Streaming DMX - set the Unicast addresses in Setup, View DMX I/O. When a Unicast address is set for a universe, MagicQ no longer sends that universe to the Multicast address.

From v1.7.3.9 MagicQ supports use of the priority field in ACN universes. Versions of MagicQ prior to this transmit ACN with priority 100 and ignore priority when recieving ACN.

The output priority can be set in SETUP → Network. This should be between 1 - 200 and defaults to 100. When receiving ACN, if there are multiple sources for a particular universe, MagicQ will only listen to the highest priority. The behaviour of MagicQ is undefined when there are more than 5 ACN sources for a particular universe or multiple sources with the same (highest) priority; this is not reccomended.

46.4.4. SnakeSys T2/B4/R4/R8/ChamSys Ethernet Interface

The SnakeSys B4 and SnakeSys R4 support four DMX output universes. The SnakeSys T2 supports two DMX output universes whilst the R8 supports eight DMX output universes. original ChamSys Ethernet Interface supported three DMX output universes,

To use a SnakeSys interface that is set for Art-Net on Art-Net Universe 0-0 (both rotary switches set to 0) set the first 4 universes in Setup, DMX I/O to Out Type of Art-Net, and In Type of Art-Net and enable them. For the simplest operation, set the Out Uni and the In Uni for Universe 1 to 0, for Universe 2 to 1 and Universe 3 to 2, and Universe 4 to 3.

46.4.5. MagicQ Consoles Direct Outputs

All current MagicQ consoles have four direct DMX outputs on the rear panel.

By default MagicQ consoles are set to output the first 4 console universes on the direct console outputs.

If the setting “Setup, View Settings, Ports, MagicQ Wings & Interfaces” is set to “Yes (auto DMX)” then the first 4 universes will output regardless of whether they are enabled in Setup, View DMX I/O.

If you wish to patch the direct outputs to other than the first four universes, then set the required universes to “MQ Direct” and set Port 1, Port 2, Port 3 or Port 4. As soon as any of the universes are set to “MQ Direct” or “Cham USB” then this overrides the default settings.

Note that MagicQ consoles support DMX input via Art-Net, Pathport or sACN. The direct DMX ports on MagicQ consoles and MagicQ Wings do not support DMX Input. In order to receive DMX into a MagicQ console we recommend to use a SnakeSys interface to convert from DMX to Art-Net or sACN.

46.4.6. MagicQ Stadium Wing

The MagicQ Stadium Wing is designed to connect to a MQ500 console to add extra playbacks and DMX outputs. Older versions of MagicQ supported the Stadium Wing on some other MagicQ products - in order to simplify the product range this is no longer supported.

MagicQ Stadium Wing has four DMX outputs. When connected to a MQ500 the DMX outputs are by default set to output console universe 5 to 8. If you wish to patch the direct outputs to other than universes 5 to 8, then you will need to set all required universes to “MQ Direct”.

46.4.7. MagicQ Mini/PC/Maxi Wing

MagicQ Mini Wing has one DMX output, MagicQ PC Wing and PC Wing Compact have two DMX outputs and the MagicQ MaxiWing has four DMX outputs.

By default MagicQ is set to output the first universes on the system to the DMX outputs on the MagicQ Mini, PC and Maxi Wing. For MagicQ Mini Wing Universe 1 will be output from the DMX port, for PC Wing and PC Wing Compact universes 1 and 2 will be output, and on MaxiWing universes 1 to 4 will be output.

If Setup, View Settings, Ports, MagicQ USB Wings & Interfaces is set to “Yes – auto DMX” then MagicQ will automatically output DMX on the Wings starting from Universe 1 – provided that none of the Universes have been explicitly set to “MQ Wing”.

To use different universes, set the required universes to MQ Wing and enable them. The universes set to MQ Wing will be output to the ports in order.

Note that in an emergency it is also possible to use the MagicQ Mini Wing, PC Wing or Maxi Wing direct DMX outputs with a MagicQ console – simply connect the MagicQ Wing to the MagicQ console using a USB cable and set the outputs as above.

46.4.8. MagicQ Dual DMX Interfaces

For MagicQ Dual DMX Interfaces select MQ Dual DMX. In older software this was ChamSys USB. Then select the module and port in the Out Uni field. For example, select Mod 1 Port 1 and Mod 1 Port 2 for the two outputs. Any of the universes can be output to MagicQ Dual DMX interfaces.

When connected to MagicQ consoles and some laptops the MagicQ Dual DMX Interface may need external power from a 12V power supply. Check Setup, View System, View Status, DMX Interfaces, DMX Modules.

When connected to MagicQ consoles the module should be configured as Mod 2 Port 1 and Mod 2 Port 2 since the console internal DMX module is considered to be module 1.

46.4.9. MagicDMX Interfaces

MagicDMX Interfaces automatically output on universe 1 when Setup, View Settings, Ports, MagicDMX mode is set to DMX Out.

It is possible to set the Out type for Universe 1 to be MagicDMX – this automatically sets the Setup setting MagicQDMX mode to DMX Out.

It is not necessary to set the Out type for Universe 1 – only the MagicDMX mode setting.

MagicDMX devices do not need any additional drivers – they use different HID drivers within the operating system.

Note that the MagicDMX Basic version is limited to 5 hours of continuous use. When the time is close to expiring warnings will be shown. On expiry the MagicDMX will send out DMX levels of 0. The MagicDMX Basic interface must then be unplugged and MagicQ software restarted to use the device again.

The MagicDMX Basic version only supports DMX Out. The MagicDMX Full Interface supports both DMX Out and DMX In.

The MagicDMX interfaces do not remove the automation and remote restrictions when used with MagicQ Software – this requires a MagicQ Wing, or MagicQ Dual DMX Interface.

46.4.10. Support for Lumen Radio Nova

MagicQ now supports the Lumen Radio CRMX Nova TX USB dongle for controlling one universe of DMX via Lumen Radio. This allows Heads from many manufacturers including Robe and Ayrton to be controlled over wireless direct from the console.

In MagicQ simply set the Output Type in Setup, View DMX I/O for Universe 1 to Enttec Pro / Lumen Radio and enable the universe. When connected the interface should be shown under Setup, View System, View Status, Interfaces, Port Type as "En". The Enttec Pro / Lumen Radio can only be configured on Universe 1. To output a different universe to the device set the copy field on Universe 1 to copy from the required universe.

The Lumen Radio device is supported on all MagicQ consoles except MQ40 and MQ40N.

Only one Lumen Radio device is supported per console.

46.4.11. 3rd party DMX dongles

MagicQ software had some support for 3rd party DMX dongles but we cannot guarantee their performance - we recommend the use of our low cost MagicDMX interfaces. 3rd party DMX dongle are supported on Universe 1 only. Note that some of these devices rely on the PC to do the DMX framing and therefore results may be unpredictable on some systems. Many of these devices are unable to transmit full DMX frames at the full DMX refresh rate.

Note that if you are using the Enttec Pro on Windows you must use the MagicQ wing drivers from Program files, ChamSys Ltd, MagicQ Wing Drivers, FTDI. Be aware that Windows may change the drivers when it auto updates - you will need to reinstall the MagicQ Drivers.

[Note]

Enttec Pro 1 may need to be flashed with the rdm_203.bin firmware using the Enttec Pro Utility; the dmx_144.bin firmware may have reliability issues on Windows.

46.4.12. Testing Output Universes

MagicQ supports some simple options for testing complete output universes, including sending all ‘0’s, sending all ‘255’s, and several additional test patterns. Tests can be performed on individual universes using by selecting the test in the Test field of the Setup Window, DMX I/O view.

Selecting "Input" automatically routes all 512 input channels received on the universe to the 512 output channels. This is useful for loopback and network protocol conversion.

Selecting "Merge" automatically merges the received 512 input channels with the consoles 512 output channels. All 512 channels are HTP merged - i.e. the output is the largest of the input value and the console calculated value.

When any of the universes are in test mode a warning flashes in the Status Display.

46.4.13. Copying Output Universes

MagicQ supports copying of entire universes to multiple outputs – this may be useful where you wish to duplicate an output universe onto different outputs of an Art-Net box, or you want to set MagicQ wing outputs to be the same as Ethernet outputs. Select the universe you wish to copy in the Copy field of the Setup Window, DMX I/O View.

Select the Universe to copy – e.g. Uni 1 for the first Universe. You can enter the universe number. Enter 0 to turn off copying.

46.4.14. Hot take-over

MagicQ supports hot take-over to enable a second console (or MagicQ PC) to take-over running the show if the first console has a problem.

When using Net Sessions, then all Hot Takeover fields in DMX I/O should be set to No.

For how to use hot take-over see Using Multiple Consoles.

46.4.15. Input universes

MagicQ supports the same number of input universes as output universes. Input universes can be used for grabbing DMX data from other consoles, remote triggering via DMX, and merging with MagicQ calculated data. The Input universes can also be used to monitor lighting data on the network.

By default the Input universes are configured the same as the Output universes. If you wish to receive data from other consoles then you must use different universes for input from the ones you are using for output. For example if you have universe 1 to 16 set to output on Art-Net 0-0 to 0-15 then you must not uses these Art-Net universes for Input. We recommend using much higher universes for input - e.g. Art-Net 4-0.

From v1.7.1.3 if data is received on the input from another console then MagicQ will detect a conflict and change the status field to show "En Cflct" and "Dis Cflct" dependent on whether the universe is "Enabled" or "Disabled".

Data being received on Input Universes can be viewed in the Output Window, View Chans, View DMX by selecting DMX Inputs. Make sure to change back to View Outputs after you have finished viewing the Outputs otherwise it may cause confusion later.

Data received on input universes can be merged into <_testing_output_universes,complete universes> or merged in the <_merging_with_dmx_input,Patch>, or to <_using_an_external_dmx_console_for_extra_playbacks,trigger playbacks> (Setup, View System, View Wings) or used to trigger <_automation,Automations>. It can also be used to <_grabbing_palettes_from_dmx_input,grab palettes from DMX>.

The DMX I/O window shows the status of the Input universes (page right) including:

In last rx

Time since last received input

In last change

Time since DMX data last changed

In last byte

The value of the 1st byte in the last DMX data received

In max gap

The maximum gap between DMX packets received

In last period

The period that this universe was last receiving data for

In IP

The IP address that data was last received from

In conflicts

The number of conflicts - where data transmitted/received from 2 or more sources

The maximum gap only starts counting once a valid DMX data is received on that universe. It is set back to 0 when changes are made in DMX I/O.

The period that the universe was last receiving data counts up whilst data is being received. If there is a gap of greater than 60 seconds then it is reset to 0.

The IP address shows the IP address of data received over the network and does not include data transmitted from this console.

The number of conflicts is increased if data for a particular universe is received from 2 or more consoles within 5 seconds. It is also increased if MagicQ transmits on a universe where data has been received from another console within the last 5 seconds. Note that MagicQ will not count conflicts when master/slave hot swaps are in progress.

46.5. Wing Settings

ChamSys manufacture the following wings that connect to PCs, Macs and consoles via USB

Table 46.9. Wings

ProductNo of PlaybacksPlayback nos.No of DMXNo of wings supported per PC / console

Mini Wing

10

Main (1-10)

1

1

PC Wing

10

Main (1-10)

2

1

Maxi Wing

10

Main (1-10)

4

1

Extra Wing

24

1 * Wing Playbacks

None

8

Playback Wing

24

1 * Wing Playbacks

None

8

Execute Wing

48

2 * Wing Playbacks

None

4

Stadium Playback Wing

30

2 * Wing Playbacks

4

1 (MQ500 only)


Note that the Mini Wing, PC Wing and Maxi Wing can be connected to a MagicQ console to enable extra DMX outputs from the console. Note that they duplicate the Main Playbacks (1-10) – they do not enable extra Playbacks.

46.5.1. Connecting a Mini Wing, PC Wing or Maxi Wing

Before you can use the MagicQ PC Wing the driver must be installed.

To enable the wing ensure that Setup, View Settings, Ports, MagicQ Wings & Interfaces is set to "Yes (auto DMX)".

The following short-cuts make programming on MagicQ PC Wing easier. The short cuts also work on MagicQ console.

Table 46.10. Programing Wing Shortcuts

Hold ALL and press a playback Select

Selects groups 1 to 10

Hold POS and press a playback Select

Selects position palette entry

Hold COL and press a playback Select

Selects colour palette entry

Hold BEAM and press a playback Select

Selects beam page or beam palette entry

Hold ALL and press Next Head

Selects next group

Hold ALL and press Prev Head

Selects previous group

Hold POS, COL, or BEAM and press Next Head

Selects next range for last encoder changed

Hold POS, COL or BEAM and press Prev Head

Selects previous range for last encoder changed


To connect a Mini, PC or Maxi Wing to a console simply enable the MagicQ Wings and Interfaces option.

46.5.2. Connecting Playback Wings and Extra Wings

To configure Playback Wings and Extra Wings open the Setup Window and choose View System, View Wings view.

In the Type field, choose "Playback / Extra Wing". When the console has detected the Playback wing it will show as "Fitted" in the status field.

If you wish to connect more than one Playback or Extra Wing then enable the required number of Wings.

Make sure you enable enough or the same number of wings as you connect to MagicQ. Connecting more Wings to MagicQ than you enable will cause unpredictable results.

Playback Wings and Extra Wings with Blue LCDs can have a Wing ID set for systems with more than one Playback or Extra wing. Hold down the lower NEXT PAGE and PREV PAGE buttons when powering on the Wing to get into the Wing config mode. From the menus you can then set a Wing ID.

In MagicQ, Setup, View System, View Wings you can configure which Wing IDs are expected.

46.5.3. Connecting an Execute Wing

The Execute Wing has 48 playbacks arranged as 12 fader playbacks and 36 button only playbacks. The Execute Wing can be configured simply to control Playbacks, or it can be set in a mode whereby the 36 button only playbacks become a 72 button matrix for use selecting heads, palettes, groups, media and execute buttons.

To configure the MagicQ Execute Wing it must be set up as two consecutive wings in Setup, View System, View Wings. The first wing must be configured as “Execute” and the second wing as “Execute Top”.

This corresponds to the 48 playbacks whereas with standard Playback Wings there are only 24 playbacks.

The Execute Wing has a mode button called MENU. When this is pressed and held then the 2nd row of buttons becomes a mode selection page. The mode button affects the top 3 rows of playbacks – it does not affect the bottom row of 12 playbacks – they are always configured as normal Playbacks.

The mode options are:

Playbacks

3 rows of 12 playbacks each with separate GO/PAUSE (default)

Exec

Access to the Execute Window, enabling complete user configuration of the buttons. Use PG UP and PG DN to select the Exec Page.

Heads

Selecting heads. Use PG UP / PG DN to scroll pages of heads.

Palet

The buttons are automatically split into 24 Groups, 16 position palettes, 16 colour palettes and 16 beam palettes.

Media

Access to the Media Window. Shows media page options, servers, layers and images as in the Media Window. Use the 2nd down PG UP/PG DN buttons to change the Media Bank. Use the 3rd down PG UP/PG DN buttons to change the Media Image.

Cues

Testing of Cues. Use PG UP / PG DN to scroll pages of cues.

Cue Stack

Testing of Cue Stacks. Use PG UP / PG DN to scroll pages of Cue Stacks.

DMX Test

Tests individual DMX channels. Use PG UP / PG DN to scroll pages of channels.

Head Test

Tests (locates) individual heads. Use PG UP / PG DN to scroll pages of heads.

When selecting the mode, you can choose to press the SELECT button or the FLASH button associated with the mode. In some of the modes this will alter the behaviour. For example, in the Heads Test, DMX Test, Cues and Cues Stack modes, this determines whether the test is latching or momentary.

In Playback mode the upper 3 rows of playbacks control playbacks in the usual way. Note that as they do not have a fader, the value the attributes that would normally be controlled by the fader (generally Intensity values) will automatically default to 100%. The Playbacks can still have times in the normal way, so that Intensity values can be faded in and out.**

46.5.4. Connecting MagicQ consoles together

It is possible to connect multiple MagicQ consoles together in order to control a larger number of Universes. The master MagicQ console then outputs some channels which act like playbacks for the slave consoles.

On the slave consoles, one of the wings is configured as "DMX In" and select a range of channels for it to respond to. Note that the universe that contains these channels must have input enabled in the "View DMX I/O" view. This causes the playbacks on the wing to be controlled by up to 24 DMX channels received into the console. The level of the playback is determined from the received channel.

46.5.5. Using an external DMX console for extra playbacks

It is possible to use an external DMX console to gain extra playback controls when using MagicQ consoles. This is not a replacement for a MagicQ Playback wing with its electronic legending and Cue Stack controls.

On MagicQ PC this option is only available to control Playbacks PB1 to PB10 and is only enabled when a MagicQ Wing or MagicQ USB Interface is connected. This feature allows synchronisation of MagicQ with other consoles.

Configure an unused wing to be "DMX In" and select a range of channels for it to respond to. Note that the universe that contains these channels must have input enabled in the "View DMX I/O" view.

In order to allow use of FLASH buttons on the external DMX console, MagicQ uses the top 5% of the channel range as an indication that a FLASH button has been pressed. On the external console the playback master fader should be configured at a maximum of 95% with the flash master set to 100%. If it is not possible to set the master levels independently on the external DMX console then set the grand maser on it to 95%.

46.6. Monitor Settings

46.6.1. MQ500 Operating System

On the MQ500 one external touch screen is supported up to 1920x1080 resolution. The MQ500 has a DVI-D connector which supports connection to an external DVI Digital monitor via DVI. The DVI-D connector does not support the use of DVI-VGA apapters.

In Setup, View System, View Monitors set Monitor 1 to the required resolution in the Resolution column, and enable it. You will be asked to restart - confirm No and set up the Type field.

46.6.2. Compact (MQ50/MQ70) Operating System

On the MQ50 and MQ70 one external touch screen is supported up to 1920x1080 resolution - display via the HDMI connector and touch via USB.

46.6.3. MQ80 Operating System

On the MQ80 one external touch screen is supported up to 1920x1080 resolution. The MQ80 has a DVI connector which supports connection to an external monitor via either DVI or VGA cable - unlike other MagicQ consoles you must configure which cable you are using.

In Setup, View System, View Monitors set Monitor 1 to the required resolution in the Resolution column, and enable it. You will be asked to restart - confirm No and set up the Type field.

Set the Type field to VGA or DVI depending on which input socket you are using on your monitor - VGA or DVI.

After configuring View Systems, View Monitor, the external monitor may still be showing as a clone of the internal monitor. Power the console off and on for the changes to take effect.

46.6.4. Old Compact (MQ40N/MQ60/old MQ70) Operating System

On MQ40N consoles one external monitor (not touch screen) is supported. The monitor is always fully enabled on the MQ40N, there are no settings to be set for this functionality.

On the MQ60 and MQ70 one external touch screen is supported. We recommend using a 1024x768 resolution monitor for best performance.

Touch screens are supported but note that the Linux operating system on use on these consoles does not currently support multi touch touch screens.

46.6.5. Pro 2014 Operating System

On MagicQ consoles running the Pro 2014 operating system there is support for 1 external monitor with resolution up to 1920x1080. The monitor can be a touch screen. Note that from September 2014 new Pro 2014 consoles only support one external monitor.

In Setup, View System, View Monitors set the required resolution in the Resolution column and enable it. Monitor 2, 3 and 4 are not used.

When using USB touch screens, go to Setup, View System, View Status, Touchscreens to determine which touch screen is Touch 1.

Choose the touch type as appropriate - generally Normal or Egalix. Use Board Test Mode (SHIFT + SHIFT) to prove that touch information is being received correctly by MagicQ.

46.6.6. Monitor settings on MagicQ PC / Mac

When using multiple monitors on a PC first enable the monitors in Windows by putting the Windows desktop onto all the monitors. Then start MagicQ PC and in Setup, View System, View Monitors enable the required monitors.

The first monitor is the main MagicQ Window and must always be enabled. Enable all the monitors that you wish to use for Multi Windows.

From the Toolbar select View, External or press the EXT button to move a Window between the different monitors.

Sizing of Windows on the other monitors occurs just like in the Main Window – you can select full windows, half windows and quarter windows.

The entire space on the other monitors is used for MagicQ Windows. When a Window is moved to another monitor the size is kept the same – for example, if it was a quarter window on the Main MagicQ Window it will be a quarter window on the other Window.

You can change the size on the other windows, just like on the Main MagicQ Window from the View menu on the Toolbar or by using the SIZE button.

46.6.7. Moving Windows to the External Monitor

Press EXT to move a Window to the External Monitor. The window that is currently in focus is transferred to the external monitor. Press EXT to return the window to the main monitor.

Press SHIFT + EXT to bring all windows to the internal monitor. On Compact consoles type 0 and press ALT MEDIA (EXT).

MagicQ includes an option to force a single window to the external monitor output. The Window will remain on the external monitor except when a SHIFT CLOSE is performed. This option is set in the Setup Window, View Settings, Windows, Force Window on External Monitor 2.

46.6.8. Additional Cue Stack, Output, Programmer, Media, Execute, Group Windows

MagicQ supports additional windows - accessed by pressing CTRL and the Window button or by typing 2 and the Window button to get the second window.

Up to four Output Windows are supported by pressing 2 OUT, 3 OUT and 4 OUT. Up to 3 Execute Windows are supported by pressing 2 EXEC and 3 EXEC.

Up to three Group Windows are supported by pressing 2 GROUP and 3 GROUP.

For instance by using both the Outputs and the Outputs Info windows you can view both the plan view and the data values simultaneously.

Similarly, the Cue Stack Info window is designed as a master window to keep track of the Cue Stack on the currently selected playback. The columns have been rearranged so that the comment field is shown as one of the first columns.

This is ideal for theatre playback where the operator wishes to see notes about the Cues during playback – you could for instance put a comment on a Cue “Call spots when actor enters stage right”.

46.6.9. Additional external screens (MultiWindows) on consoles

The MagicQ Compact, Pro 2010 and Pro 2014 consoles support an external monitor directly from the rear panel.

It is possible to connect more monitors (up to a total of 4) using the MagicQ Multi Window application running on a PC. The MagicQ MultiWindow application comes as part of the MagicQ PC installation. This can be used to display windows from remote MagicQ systems. These additional monitors can be touch screens if the PC supports them.

In order to enable Multi Windows connection on MagicQ enable the net monitor on the console in Setup, View System, View Monitors.

Connect the MagicQ console to the PC/Mac using a network cable and ensure that both PC/Mac and MagicQ console are on the same network IP address range (e.g. 2.x.x.x subnet 255.0.0.0).

On the PC or Mac, run the Multi Window Client application; it should automatically detect the console.

Note this function is not supported on the MQ40N console, and that the plot, curve editor, MagicVis, and MagicHD windows are not supported. (However, MagicVis and MagicHD both have their own networking capability in standalone mode).

46.7. Touch Screen Settings

On PC / Mac systems touch monitors are set up under the operating system not under MagicQ.

MagicQ consoles support many different touch protocols - however we are reliant on the drivers available in Linux, so not all touch screens will be supported. We strongly recommend you check the protocol is supported and test a sample with a MagicQ console before purchasing a touch screen. We can not guarantee that any touch screen will work with MagicQ - the list below is for guidance only.

We generally recommend iiyama, Protouch and ELO AccuTouch and ELO IntelliTouch touch screens. Note that ELO Acoustic Pulse Recognition (APR) touch screens are NOT supported. Note that we currently do not support touch screens with multi touch support on the MQ60 and MQ70 Compact consoles.

For MQ500, MQ50, MQ70, MQ80 and Pro 2014 we have tested and recommend the iiyama Prolite T2336MSC, Hanns G HT225HPB, Asus VT207N, Dell S2240T & P2418HT and Viewsonic TD2421 Touch screens. Note these are not supported on MQ60/70 or Pro 2010.

For MQ60/70 we recommend iiyama Prolite T1531SR-B1 or Iiyama Prolite T1561SR-B3 connected via RS232 serial port for the touch - note that this monitor is not supported via USB on MQ60/70

We also recommend the ELO1919L model no E176026 and viewsonic TD2210 single touch resistive touchscreen - these touch monitors are supported connected via USB to the MQ60/70.

46.7.1. Serial protocols

MagicQ Compact, Expert, Pro, and Pro 2014 consoles support the following serial protocols

  • Ideal
  • ProTouch
  • A1
  • ELO

46.7.2. USB protocols

MagicQ consoles have support for the following USB communication protocols

  • Elo 15 * E271-2210 10-byte protocol
  • Elo legacy E281A-4002 6-byte protocol
  • Elo 16 * legacy E271-140 4-byte protocol
  • Elo legacy E261-280 3-byte protocol
  • eGalax Touchkit
  • eTurboTouch CT-410/510/700
  • 3M/Microtouch EX II series
  • ITM
  • PanJit TouchSet
  • eTurboTouch
  • Gunze AHL61
  • DMC TSC-10/25
  • IRTOUCHSYSTEMS/UNITOP
  • IdealTEK URTC1000
  • General Touch
  • GoTop Super_Q2/GogoPen/PenPower tablets
  • JASTEC USB touch controller/DigiTech DTR-02U
  • Zytronic capacitive touchscreen
  • NEXIO/iNexio

We generally recommend iiyama, Protouch and ELO AccuTouch and ELO IntelliTouch touch screens. Note that ELO Acoustic Pulse Recognition (APR) touch screens are NOT supported.

For MQ50, MQ70, MQ80, MQ500 and Pro 2014 we have tested and recommend the iiyama Prolite T2336MSC, Hanns G HT225HPB, Asus VT207N, Dell S2240T and Viewsonic TD2421 Touch screens. Note these are not supported on MQ60/70 or Pro 2010.

For MQ60/70 we recommend iiyama Prolite T1531SR-B1 connected via RS232 serial port for the touch - note that this monitor is not supported via USB on MQ60/70

We also recommend the ELO1919L model no E176026 - this touch monitor is supported connected via USB to the MQ60/70.

MagicQ Pro2010, MQ60 and MQ70 consoles do not support multi touch touch screens.

MagicQ will show any detected touch screens in Setup, View System, View Monitors.

46.7.3. Configuring an external Touch Screen

To configure an external serial touch screen:

  • In Setup, View Settings, Ports set Serial Remote Protocol to one of Ideal Touch, Pro Touch, A1 Touch, Elo Touch.
  • In Setup, View Settings, Ports set Serial baud rate, parity, data bits, stops buts. If in doubt set baud rate to 9600, data to 8 bits, stop bits to 1 and no parity.
  • Select the Serial Touch Monitor to the monitor the serial touch is associated with.
  • Press ALT + CNTRL + SHIFT together to enter board test mode. Moving a finger around the edge of the screen should report increasing/decreasing X,Y values in the Status Window.
  • Exit board test mode (ALT + CNTRL + SHIFT).
  • Go to Setup, View Settings and select Calibrate Touch. Press 1 to confirm.
  • Now press the X on the external touch screen in the four different positions as requested. Do not press on any other monitors except the one being calibrated.

To configure an external USB touch screen:

  • Set up the Touch Type in Setup, View Settings, Monitors. Start with Normal or eGalax.
  • If a touch screen is detected then it will show up in the Touch Status field.
  • Press ALT + CNTRL + SHIFT together to enter board test mode. Moving a finger around the edge of the screen should report increasing/decreasing X,Y values in the Status Window.
  • Exit board test mode (ALT + CNTRL + SHIFT).
  • Go to Setup, View Settings and select Calibrate Touch. Press 1 to confirm.
  • Now press the X on the external touch screen in the four different positions as requested. Do not press on any other monitors except the one being calibrated.

If the Touch Screen shows a status but does not give consistent values in Board Test then try a different Touch Type.

If the Touch Screen shows consistent values in Board Test but does not respond correctly then recalibrate the touch screen.

46.8. Mode & Security Settings

The Settings View of the Setup Window uses tabs to group similar settingstogether.

image

46.8.1. Country

The country setting determines the locale of the installed MagicQ system. Currently MagicQ supports: UK, US, F (French), D (German), E (Spanish), P (Portugese), I (Italian) and NL (Dutch). When selected, menu items will be displayed in the appropriate language.

46.8.2. Time Zone

The time zone setting determines the current global time zone of the installed MagicQ system.

The time zone option is used when programming with scheduled events.

Enter the time zone in relation to UTC+0. For example, if 8 hours behind enter “-8”.

46.8.3. Latitude

The latitude setting determines the current latitudinal position of the installed MagicQ system.

The latitude option is used when programming with scheduled events.

Enter the latitude in degrees.

46.8.4. Longitude

The longitude setting determines the current longitudinal position of the installed MagicQ system.

The longitude option is used when programming with scheduled events.

Enter the longitude in degrees.

46.8.5. Console Mode (advanced settings)

This setting defines the operational mode of the console. The options for console mode are: “Normal”, “Simple” and “MQ500 as MQ100”.

When this option is set to “Simple”, some of the more advanced settings are hidden to simplify the user interface.

In versions prior to v1.8.7.3 there was an option “MQ500 as MQ100” which has now been removed. Playbacks can now be easily moved around in the Playbacks Window, View All.

Default: Normal

46.8.6. Programming

This setting enables and disables the recording of show data. When set to “disabled”, show data can not be recorded, moved, copied or updated, preventing the show from being changed.

Parameters of Cue Stacks and Cues such as Chase Speed, Shape Size and times can still be modified.

Default: Enabled

46.8.7. Modifications

This setting enables and disables modifications of Cues and Cue Stacks.

Parameters such as Chase Speed, Shape Size and times can not be modified, ensuring Cues and Cue Stacks are played back exactly how they were programmed.

Default: Enabled

46.8.8. Test Mode

The Test Mode setting enables and disables the testing of Cues, Cue Stacks, Playbacks and Patched heads from the Cue, Cue Stack, Playback and Patch windows respectively. It also disables play back of Cues and Cue Stacks from the Execute window.

Use this setting to avoid accidental testing of programmed show elements.

Default: Enabled

46.8.9. Macros

This setting enables and disables Macros.

Use this setting to turn off Macros where they have been mistakenly assigned to keys or other show programming elements.

Default: Enabled

46.8.10. Visualiser

The Visualiser setting determines how heads are inserted and operated within the Visualiser

When this option is set to “Disabled”, heads are not auto inserted and the user is prompted when patching the first head within a show.

When this option is set to “Auto Insert Into Visualiser”, heads are auto inserted into the visualiser upon patching within a show.

When this option is set to “Auto Insert, Auto Previs”, heads are auto inserted and Cue previsualistion is enabled by holding the playback S buttons.

When this option is set to “Auto Insert, No Patch Offsets”, heads are auto inserted but no patch offsets are added to the Visualiser output.

Default: Disabled

46.8.11. Auto Backup

This setting enables the console to create automatic backups of your show file.

When this option is set to “No”, no backups will be saved. “No” is recommended during playback of very large show files to avoid slowing the response of the console.

When this option is set to “On Changes”, MagicQ will only back up your show file after changes are made. The backup is scheduled up to 60 seconds after the change. “On Changes” is recommended when programming to avoid loss of show data.

When this option is set to “Always”, backups will be made every 60 seconds.

Default: On Changes

46.8.12. Keep a backup archive

This setting enables the console to keep periodic archives of previous auto backups created. If the Auto Backup setting is set to “No” then no archives will be made.

See archive.

Default: Yes

46.8.13. Show file path

This setting defines the location of saved show files and backups.

Users can save show files in custom-named folders, this may be useful within the education environment to separate different users.

Default: “show” (Recommended)

46.8.14. Show file format

This setting defines the format of saved show files.

When set to “High Res FX”, MagicQ will use an improved file format capable of saving higher resolution timing values.

When set to “Normal”, MagicQ will use a slightly smaller file format, excluding the higher resolution timing values found in “High Res FX”.

When set to “Reduced Size - Testing Only”, MagicQ will use a compressed file format designed for larger show files.

Default: High Res FX

46.9. Programming Settings

Programming settings are automatically changed when you select the mode – Normal, Theatre non-tracking, Theatre Tracking or Hog II Warp.

46.9.1. Activate Chans/Heads

This setting determines what gets activated in the programmer when you perform a change on an attribute of a Head.

"Chans" only activates the actual channels of a modified attribute within a head.

"Heads" activates all channels within that head whenever any attribute is modified.

"IPCB" activates all the attributes of the IPCB type that is being modified - for example if a position (P) attribute type is changed such as pan, then all other position attributes such as Tilt, Pos Speed are activated.

"IPC" activates all the attributes of the type that is being modified except that colour © attributes are modified individually.

"Beam" activates all Beam attributes whenever any Beam attribute is modified.

Default: Chans

46.9.2. Programmer Tracking

Turns the overall function of tracking On or Off for any future programming once the setting is changed. It does not change any previously programmed items. Tracking can still be modified on a cue by cue basis within the cue stack, via the "Track" column.

When set on, then only attributes that have been modified since the Cue was recorded are stored into the new Cue.

Attributes are determined as modified if their value had been changed using an encoder, using keypad entry, using a range button, using a palette or by a locate Head. Note that modifying an attribute to a new value and then returning it to its old value counts as modified.

When set off, then the entire contents of the programmer is recorded into Cues regardless of whether attributes have been change since the last Cue was recorded.

46.9.3. Unused Chans return to defaults

When set to "Yes, all heads" this forces all LTP channels to return to their defaults when not controlled by a playback or in the programmer. The default returned to will be the Default Cue if it exists, otherwise the default value from the Head personality.

When set to "Heads without Intensity only" it only returns to defaults for heads that do not have an Intensity attribute and do not have a VDIM applied.

When set to "No" then no channels return to their defaults.

Note that some channels can be specified in the Head personality not to have a default - in this case those channels never return to defaults.

Default: The default is dependent on the programming mode chosen - in Normal mode it is set to "Heads without Intensity only". In other modes it is set to "Yes, all heads".

46.9.4. Programmer overrides HTP

Determines whether the programmer overrides HTP (intensity) values on playbacks.

When set to "All Playbacks" any HTP channels in the programmer are no longer affected by the levels of those channels on playbacks.

When set to "Playbacks except highest priority" then it as for "All Playbacks" unless a Playback is set to highest priority in the Cue Stack, Advanced, Playback Priority setting.

When set to "All Playbacks except HTP base" then any HTP channels with a base value in the programmer will not be affected by Playbacks. HTP channels in that have only an FX but no base in the programmer can be affected by Playbacks if the "Intensity *HTP) FX can add,subtract" is set. Highest priority playbacks override the programmer when set to "Playbacks except highest priority".

When not set, the highest value of the channel from the Playbacks and the Programmer is output.

Default: All Playbacks

46.9.5. Programmer overrides FX

Allows the programmer to override FX on active playbacks. When set to Yes, any channels that have base levels in the programmer ignore FX for those channels from any active playbacks.

Default: No

46.9.6. Highlight mode

Changes the function and operation of highlight mode when trying to work with a specific Head within a group of Heads.

“Normal” - the intensities of the selected heads are reduced except for the one (or ones in Odd/Even mode) that are being sub selected. Highlighting of the sub selected head(s) makes programming of positions much easier.

"Advanced" honours the highlight and lowlight levels as set in the Head personality or as set by the user in the Cue Window.

"Advanced Highlight Only" is the same as Advanced but no Lowlighting occurs.

"Advanced No Reset" is the same as Advanced, but only clears when you press Highlight again.

Default: Advanced

46.9.7. Fan Mode

This setting determines the fan mode.

"Normal" is a latch type operation where the user has to turn Fan on and off manually. "No Toggle" is a momentary type operation. "Pan Only No Tilt" allows fanning of all attributes except for Tilt.

Default: Normal

46.9.8. Select Multiple Groups

This setting enables multiple groups to be selected without pressing SHIFT. To deselect all groups press the DESELECT ALL soft button in the Group window.

"No" allows the user to choose between only being able to select one group at a time.

"Multiple in one go" allows the selection of multiple groups at one time. The selection resets after an attribute has been modified.

"Multiple always" is the same as above but does not reset.

46.9.9. Recording to Palettes

This allows either all heads or only the selected heads to be recorded into Palettes

Default: Only selected heads

46.9.10. Record merge overrides times

When set "Yes" then Record Merge allows the time currently in the programmer to be merged into the Cue being updated

When set "No" Record Merge will not modify existing times in the merged Cue.

Default: Yes

46.9.11. Update Clears Programmer

When set the programmer is automatically cleared after using Update.

Default: No

46.9.12. Undo mode

Allows the user to choose between two levels of Undo - "Undo Programmer" and "Undo Programmer and Actions".

Undo Programmer is any changes that have modified values in the programmer such as locating Heads, clearing, setting intensities, choosing palettes, or using encoder wheels to change programmer values.

Undo Actions include changes to show data such as recording, moving, copying, and naming.

When set to "Undo Programmer, Action via Ctrl" then pressing Undo by itself will only undo the Programmer. Press CTRL + UNDO to undo action.

Default: Undo Programmer and Actions

46.10. Keypad / Encoder Settings

46.10.1. Auto enter on keypad intensity set

This setting determines whether the user is required to press ENTER when defining head intensity via the keypad. If set to Yes, then intensity levels are set immediately when 2 digits or “FULL” have been keyed in after “@”. e.g. “1 THRU 4 @ 50” or “1 THRU 4 @ FULL”.

Default: Yes.

46.10.2. Select heads on keypad intensity set

This setting determines whether the current head selection is modified when setting intensities via the keypad. When set to "No" the intensities are set without modifying the head selection. When set "yes" the intensities are set and then the head selection is modified, for example:

“1 THRU 4 @ 50” sets heads 1 to 4 at 50% intensity and selects heads 1 to 4.

“+5 @ FULL” sets head 5 to 100% intensity and adds it to the current selection.

Default: Yes.

46.10.3. Select Heads and Palettes from keypad

When enabled, select heads by typing the head selection and then pressing the appropriate Colour, Beam or Position window button. For example…

“1 THRU 4 COL” selects heads 1 through 4 and opens the colour window.

“1 THRU 4 COL 5” selects heads 1 through 4 and selects colour palette 5.

This option also enables copying of head data.

Default: Yes.

46.10.4. Select heads on include

This setting determines whether heads with levels in a cue or palette are automatically selected when including these cues and palettes into the programmer.

Default: Yes.

46.10.5. Keypad always selects heads

When set to Yes, entering head numbers on the keypad followed by the ENTER key always selects the heads, but some advanced features of MagicQ are not available directly from the keypad. When editing numeric fields in the spreadsheet style windows in this mode, the operator must use the SET button rather than editing the field directly.

Setting the “Strict” option means it is not possible to toggle or choose items simply using the ENTER key. You will always need to use SET first.

Default: No (Window items)

46.10.6. Keypad Syntax - Theatre Patch

This setting adjusts the syntax used for patching Heads. With this option set to No, the syntax for patching is <number of heads> @ <dmx address>. When set to Yes, the syntax is: <head number> @ <dmx address>.

Theatre Patch supports patching multiple DMX addresses to one head when using Theatre Patch syntax. For example, to patch Head no.10 at DMX addresses 1, 2 and 3, enter “10 @ 1 + 2 + 3”. There is a maximum of 6 DMX addresses per Head.

In Theatre Patch it is also possible to re-patch dimmer channels. If the head is already unpatched then just enter the new address – e.g. to repatch head number 20 to DMX channel 25, type “20 @ 25”. You can also re-patch to multiple DMX addresses – e.g. to repatch head number 20 to DMX channel 25 and 26, type “20 @ 25 + 26”.

Default: No (live mode) or Yes (theatre mode).

46.10.7. Encoder Mode

In "Normal" the encoder wheels function according to the currently active window. For example, when you change to the Colour window, the encoder wheels control colour attributes.

“Maintain Pos, Col, Beam” - The Position, Colour and Beam buttons will act as “Hard Buttons”, meaning the encoders will be maintained on Position, Colour or Beam even when the Group or Output windows are opened. At any time the encoders can be forced to their default settings for the Window by pressing SHIFT and the window button – e.g. SHIFT + GROUP. In addition, the “Intensity” attribute will also appear on Encoder F in the Position window if that encoder is not already in use.

“Intensity on X” - When setting an intensity level from the keypad, MagicQ will open the Intensity Window and the X encoder will control intensity.

“Pos, Col, Beam, Int X” - MagicQ performs both the above options.

“Intensity always on X” - Once the Group or Intensity windows are opened then Encoder X will remain as Intensity until a window is opened using SHIFT and the window button, forcing the normal encoder assignment.

“Keep as Window” - MagicQ will maintain the current window when functions like next/prev head are used, rather than jumping into the position window.

Default: Normal (live mode) or Intensity on X (theatre mode)

46.10.8. Swap pan and tilt encoders

This setting swaps over the pan and tilt encoders. By default, the X encoder is pan and the Y encoder is tilt.

Default: No

46.10.9. Swap Encoder direction

This setting changes the directions for adjusting values with encoders.

Default: Normal

46.10.10. Swap Palette and Cursor Page Buttons

Enables the Cursor Page buttons (Page Left, Home, Page Up, Page Right, End, Page Down) to be used as Palette buttons (Group, Int, Fx, Pos, Col, Beam). This makes it easier to select Palettes using the keypad.

When this mode is enabled the Palette Buttons become the Cursor Page buttons.

It is strongly recommended that you do not change the physical key caps of these buttons since this may cause irreparable damage to the front panel board.

Default: No

46.10.11. MagicQ keyboard mode

These options set the function of the keyboard.

In "Normal" the keyboard is used for naming items and selecting heads.

In "Programming shortcuts" the keyboard is set up for shortcuts to programming keys.

In "Playback shortcuts" the keyboard is set up for shortcuts to playback keys.

Default: Normal

Programming shortcuts

image

Windows are opened using CTRL and the alphanumeric keys

CTRL A CTRL D CTRL E Execute CTRL F Fx CTRL G Group CTRL H Help CTRL I Intensity CTRL J Beam CTRL K Colour CTRL L Cue Stack CTRL M Media CTRL N Macro CTRL O Outputs CTRL P Position CTRL Q Cue CTRL R Programmer CTRL S Setup CTRL T Patch CTRL U Page CTRL V Playback CTRL W Cue Stack Store CTRL X Cue Store CTRL Y CTRL Z

image

Playback shortcuts

1 to 0

Select playbacks 1 to 10

Q to P

GO button playbacks 1 to 10

A to ;

STOP button playbacks 1 to 10

\ to

Toggle test playback on at 100%. In Swap mode releases all others tested playbacks

`

Add / Swap mode

SPACE

Manual GO

#

Manual STOP

[

Next page

]

Prev page

-

Release

image

Note that in playback shortcuts mode many programming options will not work as expected because the keyboard keys are used for busking.

46.10.12. Map Keys to THRU, @, FULL

This setting allows the THRU, @ and FULL keys to be mapped to different keys on the keyboard. This is useful in some countries where the normal mappings (>, @ and #) are not easy to select. To set this setting, press the 3 keys you want to map to these functions, followed by ENTER.

Default: None set.

46.10.13. Enable Mouse to control pan/tilt

This setting enables a mouse or trackball to control pan and tilt. The sensitivity can be selected by choosing any of the “Enabled Div 2” through “Enabled Div 9” options.

Mouse control of pan/tilt is only supported on MagicQ consoles, or MagicQ PC systems unlocked from demo mode

See mouse controls pan/tilt.

Default: Disabled

46.10.14. Intensity Wheel

Determines the function of the Intensity Wheel on the MQ500.

When set to "Intensity" it controls Intensity of the selected Heads.

When set to "Intensity - Require ALT key" then holding ALT and turning the encoder will control Intensity in the Programmer. This is useful in high bass environments where the wheel could get accidentally nudged.

When set to "Rate" it controls the rate of the currently selected Playback.

When set to "No function" it is disabled.

Default: Intensity

46.11. Windows Settings

46.11.1. Colour Scheme

This setting defines the colour scheme of the installed MagicQ system.

“Black” turns the MagicQ interface completely black with grey option boxes and white text.

“Black Shaded” follows the same colour scheme as “Black” but with a higher contrast between the main background and the key programming areas.

“High Contrast” sets the MagicQ background to black (On Windows, Mac & Linux) but the central programming area to a lighter grey with black text.

Default: Black

46.11.2. Big Text Mode

Big Text Mode defines how text is displayed throughout MagicQ.

“ALL CAPS” displays all text in CAPITALS.

“First Letter” capitalises the First Letter Of Every Word.

“Large”, much like “ALL CAPS”, displays all text as CAPITALS but at a much larger font size.

Default: No

46.11.3. Icon Size

The Icon Size setting defines the size of all icons used throughout MagicQ.

“Small” will ensure icons only take up a portion of the window item.

“Large” sets icons to fill the whole window item.

“Large when no name” sets icons to “Large” but only where there is no text present within the same window item.

“Auto” allows icons to be auto-sized and auto-generated throughout MagicQ.

“Auto no Snapshot” disables Visualiser snapshotting when recording Cues, Cue Stacks and Playbacks.

“Auto no group / snapshot” disables Visualiser snapshotting and the generating of auto-group icons.

Default: Small

46.11.4. Col Tags

The Col Tags setting allows colour tags to be displayed, identifying different heads throughout MagicQ.

“None” disables the use of colour tags throughout the software.

“Head Types” separates Heads into colour groups depending on their type (Wash, Spot etc).

“Attach Objects” defines Heads based on the object they’re attached to within the Visualiser.

“Groups” separates Heads depending on their current group within the Group window.

“Multi Console Control” separates Heads depending on their current console control.

“Parked” colours parked Heads to separate them from unparked Heads.

“Patch” defines separate Heads depending on their sorting within the Patch window.

“Zones” separates Heads to signify which zone they are assigned to.

“Universes” separates Heads to signify which universe they are patched in.

“Users” separates Heads based on the current user.

Default: None

46.11.5. Playback Col Tags

The Playback Col Tags setting allows the RGB LEDs found in the Stadium range to indicate the different Playback functions.

“Default” sets MagicQ to use the default colour set for different types of Cue Stack. Standard Cue Stacks are blue, LTP faders & Group masters are allocated different colours.

Default: None

46.11.6. Speed Display

This setting determines how speed values are displayed throughout the installed MagicQ system. The options are seconds, BPM or frames.

When set to “Normal” MagicQ will determine the appropriate metric for that specific parameter.

Default: Normal

46.11.7. Attribute Display

This setting determines how attribute values are displayed throughout the installed MagicQ system.

When set to “Normal” MagicQ will display the attribute with the normal expected metric.

When set to “16bit” MagicQ will display all attribute values in 16bit format.

When set to “%” MagicQ will display all attribute values as percentages.

When set to “Pan and Tilt in %” MagicQ will display only pan and tilt attributes as percentages.

Default: Normal

46.11.8. Column Sizing

The Column Sizing setting determines how columns within windows are displayed.

When “Auto Size” is selected, MagicQ will auto size columns and hide any that are unused.

When “No sizing/hiding” is selected, the columns are set to a fixed width and are always present.

When “Hiding only” is selected, the columns are auto sized, but not hidden if not used.

Default: Auto Size

46.11.9. Units of measurement

This setting defines which unit of measurement MagicQ uses throughout the installed system.

When set to “Imperial” MagicQ will accept measurements of feet, inches and pounds.

When set to “Metric” it is still possible to input measurements in feet using the ‘ or / separator - e.g. enter “12/” for 12 ft and “12/4” or “12’4” for 12 ft 4 inches.

Default: Metric

46.11.10. Auto Row Ordering

This setting determines how rows are ordered within the Output, Programmer and Cue windows. The currently selected heads appear at the top of the window.

When this option is set to “No” the rows of the aforementioned windows are ordered according to the Sort option within the Patch window.

Default: Yes

46.11.11. Screen 1 fixed number of boxes

This setting determines the number of boxes (cells) allowed to be displayed across the total width of the main window. If two windows are open across the width then this number is halved.

When “Default” is selected, this number is determined by the console type.

Default: Default

46.11.12. Screen 2 fixed number of boxes

This setting determines the number of boxes (cells) allowed to be displayed across the total width of the second window. If two windows are open across the width then this number is halved.

When “Default” is selected, this number is determined by the console type.

Default: Default

46.11.13. Confirmation requests

This setting determines how confirmation requests are displayed and utilised throughout the installed MagicQ system.

When “Confirm (default no)” is selected, MagicQ will continue to confirm core functions with a default value of no.

When “Confirm (default yes)” is selected, MagicQ will continue to confirm core functions with a default value of yes.

When "Confirm critical only" is selected, MagicQ will confirm only critical functions with a default value of no.

When "Confirm critical (default yes)" is selected, MagicQ will confirm only critical functions with a default value of yes.

When “Never confirm” is selected, MagicQ will never ask for confirmation.

Please note: “Never confirm” should be used with great care.

Default: Confirm (default no)

46.11.14. Scroll bars

The Scroll Bars option determines how scroll bars are displayed throughout MagicQ.

When set to “Normal scroll bars” scroll bars are set to their standard width and appear on all scrollable windows.

When set to “No scroll bars”, scroll bars are hidden throughout all windows and selection boxes.

When set to “Wide scroll bars” the scroll bars are set to a larger width and appear on all scrollable windows.

When set to “Extra Wide scroll bars” the scroll bars are set to their largest width and appear on all scrollable windows.

Default: Normal scroll bars

46.11.15. Help Mode

Determines whether Tips are shown for settings.

When set to "Mouse Tips" MagicQ shows tips when the mouse is placed over settings fields in the first column of the Setup and Cue Stack windows.

When set to "Dialog Tips" MagicQ shows option details in the select Dialog box.

When set to "Mouse + Dialog Tips" both the above are shown.

Default: Mouse + Dialog Tips

46.11.16. Layout buttons always active

This settings determines whether the 12 available layouts are always visible on screen.

When set to “Yes”, MagicQ will display the 12 layout selection buttons above the display’s top soft buttons.

When set to “No”, MagicQ will hide the available layouts, only visible by pressing the CTRL key.

Note that on MQ500 the layout buttons are shown on the left side of the main display regardless of this option - therefore this option should be set to "No".

Default: No

46.11.17. Start mode

The Start Mode setting determines how MagicQ should operate when the software is started.

When “Splash Screen” is selected, MagicQ will display an image splash screen when the software is launched.

When “None” is selected, MagicQ will return to the last show loaded into the console.

When “Choose demo show” is selected, MagicQ will present the user with options to load the last show or a selection of preset and demo shows.

When “Visualiser” is selected, MagicQ will display the visualiser when launched.

When “Remote Control” is selected, MagicQ will launch in remote control mode.

When “Net Wing” is selected, MagicQ will launch in Net Wing mode.

When “Multi Windows Client” is selected, MagicQ will launch in Multi Windows mode and await for another MagicQ system’s connection.

Default: Choose demo show

46.11.18. Always show Record Options

This setting determines when the record options are displayed.

If set to “Yes”, MagicQ will always display the record options whenever the Record button is pressed.

If set to “No”, MagicQ will only display the record options when Shift + Record is pressed.

Default: No

46.11.19. Force Window on External Monitor

This setting determines which window is forced onto a secondary display. This can be used in addition to the manual positioning of windows on external monitors.

Windows that can be forced onto external monitors are: Output Info, Cue Stack Info, Programmer Info, Group, Execute & Plot.

This setting also provides sizing options for the different windows displayed on external monitors.

When set to “Normal Views”, no window will be forced to an external monitor.

When set to “Normal same res” MagicQ will use the same sizing options as the main monitor.

When set to “Normal 10 cols”, “Normal 12 cols”, “Normal 14 cols”, “Normal 16 cols”, “Normal 18 cols” or “Normal 20 cols”, MagicQ will set the width of manually positioned external windows to the fixed amount of columns.

Default: Normal views

46.11.20. Plan Intensity type

This setting determines how the Plan View within the Outputs Window shows intensities.

Default: None

46.11.21. Message Window

This Message Window setting determines where and how the message window box is shown.

When this is set to “Main” messages will only appear on the console’s main screen.

When this is set to “2nd Display” or “3rd Display”, MagicQ will only display messages on the defined external monitor.

When this is set to “Main No Net”, “2nd No Net or “3rd No Net”, MagicQ (when connected to a net session) will only display messages on the main monitor of the current console.

When this is set to “Net only”, MagicQ will display messages to all other consoles within the net session but not the current console.

When this is set to “Net Session”, all consoles, including the current console, will receive messages throughout the net session.

When this is set to “Main no flash”, “2nd Display no flash” or “3rd Display no flash”, MagicQ will display messages on the defined monitor without flashing.

Default: Main

46.12. Cue Storage Settings

46.12.1. Remove Cues when remove Cue Stacks

This option allows you to force Cues to be removed when the Cue Stack(s) that use them are removed.

Default: No

46.12.2. Remove Cue Stacks on remove Playbacks

This option allows the user to force Cue Stacks to be removed when Playbacks are removed.

Default: No

46.12.3. Use first free Cues, Stacks, Palettes

By default when making new Cues, Cue Stacks or Palettes, MagicQ will use the lowest free item to save it to.

When set to No, it will record these in the first free item after the last one that was saved

Default: Yes

46.12.4. Copy mode (linked/unlinked)

This setting determines how copies of your Cue Stacks are either linked or unlinked to the Cues that make up that Cue Stack.

When linked, changes you make to the copied Cue will carry through to the original Cue.

When unlinked, changes to the copied Cue do not update the original Cue.

When set to linked, this setting can be overriden using SHIFT + COPY.

The “unlinked, no state” option specifies that when Cues are copied within a Cue Stack only the “delta” values are copied not the state of the Cue at that step.

46.12.5. Copy heads

This setting determines if data recorded to playbacks is ignored when copying data between heads (when set to Prog only).

Default: Prog + Playback

46.12.6. Derive settings from previous Cue

This setting specifies how MagicQ sets the Cue settings for new Cues recorded on a Cue Stack.

When set to No, MagicQ derives cue setting from the Default setting found in Options, View Defaults.

When set to Yes, MagicQ will use the settings found in the previous Cue in the Cue Stack.

Default: Yes

46.12.7. Hide Cue Store Ids (Qids)

MagicQ supports two different ids for Cues – the Cue Id of the Cue within the specific Cue Stack, and the Qid of the Cue within the Cue Store.

When set to Yes, this will hide the Qid found in the Cue Store from the Cue Stack and Cue windows, only showing the Qid of the Cue within the Cue Stack itself.

Default: No

46.12.8. Hide Vdims

This setting allows Virtual Dimmers to be hidden from the Patch Window. Vdims are still denoted by a +V next to the head number.

Default: No

46.12.9. Expand palettes to same head type

This setting allows the building of a palette with one head type to then be expanded to all patched heads of that same type.

It is possible to choose just Colours and Beams to be expanded or all Palettes. Palettes are expanded when patching a new head and when recording palettes.

Default: No

46.12.10. Heads moved aside are unpatched

This setting determines that heads are unpatched rather than moved aside when repatching and morphing at an address with an existing head.

Default: No

46.12.11. Default mark/move when dark time

This specifies the default value for Mark cues and Move when dark.

Default: 3.00s

46.13. Playback Settings

46.13.1. Grand Master function

By default the Grand Master controls levels of channels from both the Playbacks and the Programmer.

The options enable changing the Grand Master to control only the level of preset faders, only the level of Programmer data, or both. In each of these configurations it does not control Playbacks or Add/Swap levels, as it deos by default.

See programmer data, playbacks and add/swap levels for more info.

When set as Cue Stack 1 it controls Cue Stack 1 from the Cue Stack Store, providing an extra Playback fader.

Default: Grand Master

46.13.2. Sub Master function

The Sub Master can be configured to control playback faders only, add/swap buttons only, or both (the default). It can also be set as a programmer master, a preset master or both.

When set as Cue Stack 2 it controls Cue Stack 2 from the Cue Stack Store, providing an extra Playback fader.

Default: Playback Master

46.13.3. Crossfade Master function

Configures the Crossfade master in different ways as described below:

  • “Manual Crossfade” - The Manual Crossfade function enables you to advance Cues within a Cue Stack using the Crossfader by holding the SELECT or SHIFT buttons and moving the Crossfader. The display window will show "pickup" until the crossfader level matches the current position in the fade - it will then change to "manual".
  • “Busking Rate Master” - In this mode the sub-master fader moves between 0 and 10 seconds. This rate is shown in the bottom right of the Status Display. The time is applied to selection of palettes and intensities.
  • “Sub Master” - Sub Master is useful on consoles which do not have a separate sub master fader. When set to sub master, the Sub Master function above determines its function.
  • “Cue Stack 3” - When set as Cue Stack 3 it controls Cue Stack 3 from the Cue Stack Store, providing an extra Playback fader.

The Crossfade master also has a number of rate master configurations. See manual control, rate master for further details.

Default: Manual Cross-fade Master

46.14. Crossfade button function

This option determines the function of the GO buttons in the crossfade master section.

When set to "Default" the function of the GO button is determined by the Crossfade Master function option.

  • For "Global Rate" and "Club Master" the button is set to Global Tap
  • For "Rate" and "Busking Master" it is set to Tap to Time for the selected playback.
  • For all other options it is set to the normal "Go/Back" function.

When set to "Tap To Time Selected" the GO button affects the absolute rate of the currently selected Playback. When set to "Global Tap to Time" affects the absolute rate of all active playbacks. Cue Stacks can be set to use a divisor of the tapped time via the Cue Stack Options, Audio tab. The rate divisor can also be set to "Inhibit", ignoring the tapped time.

Default: Default

46.14.1. Split Crossfade

Used to set up split crossfade functions, as below.

When set to any of the dual playback options, the two playbacks become Crossfade Masters for manual Fade in and out. Pressing the Pause button on either of the playbacks brings the current playback under manual. The faders can then be used to fade in each new Cue with separate control for fade in and out. Pressing the Go button on either Playback returns the current playback to normal Cue execution. When enabled, both playbacks can not be used as normal playbacks.

The "Stadium Split" option is used on MQ500 systems to set the two 100mm faders as split crossfaders - by default they are a crossfader and sub master.

The PB2 option is designed for Theatre use with the main Cue Stack on PB1 and the crossfader on PB2.

Default: No

46.14.2. Crossfade controls Playback

This setting enables is designed for theatrical use where one playback is the master Cue Stack.

The user can lock the manual playback section of MagicQ to Playback Fader 1, 2, 9, 10 or 15 regardless of the currently selected Playback.

Default: Selected

46.14.3. DBO function

This setting determines the function of the DBO button.

"DBO Momentary" and "DBO toggle" cause all intensity channels on the output to be set to 0%.

"No FX Momentary" and "No FX toggle" cause all FX size to be reduced immediately to zero size.

When set to "Tap to Time", the button sets the rate for the currently selected playback.

The “Flash taps when DBO held” option enables setting of speeds to playbacks by holding DBO and then pressing the flash button of the relevant playback.

Default: DBO Momentary

46.14.4. Stomp Playbacks

This option enables Stomping, the automatic releasing of Playbacks when they are fully overriden by other Playbacks.

When set to "Yes (LTP)" then when all the LTP channels on a Playback are overidden by other Playbacks then the Playback is released.

When set to "Yes (HTP and LTP)" then when all the channels (both HTP and LTP) on a Playback are overidden by other Playbacks then the Playback is released.

See Playback Stomping.

Default: No

46.14.5. Intensity (HTP) FX can add,subtract

This sets whether one Playback intensity level can subtract from another Playback’s level.

When set to “yes”, FX on one Playback can subtract from the level on another Playback.

When set to “no”, MagicQ performs pure HTP – i.e. the highest level (including FX) from all the Playbacks is output.

Default: No

46.14.6. Go reasserts channels

This setting determines which channels are reasserted when the Go button of a Playback is pressed.

When set to “All inc tracked”, then pressing GO on the Playback will reassert channels that are tracking through the Cue Stack even if they were being controlled by another Playback.

“All no fade” forces an immediate change of the channel values controlled by the Playback.

When set to “Non tracked”, only channels that are recorded as “hard values” in the current Cue will be reasserted.

When set to "Non tracked, Step then reassert", then the Cue any Cue Stack macros are executed before the channels that are recorded as "hard values" are reasserted, thus ensuring that it is possible to execute macros to release other playbacks first.

Default: All inc tracked

46.14.7. Fader off zero reasserts channels

This setting is used to reassert channels using the fader. When set to Yes, faders reassert the Playback when the level leaves zero. The setting “Go reasserts channels” specifies how the channels are reasserted.

Default: No

46.14.8. Next Page changes to next used

This enables page changes using the Next Page and Prev Page buttons to only access programmed pages rather than changing through all pages, including blank ones.

Other pages can still be accessed using the Page Window.

Default: No

46.14.9. Current Playback follows last touched

This setting makes the Current Playback follow the last Playback fader to be raised. If set to No then the Current Playback is not changed when faders are raised - it is only changed when SELECT buttons are pressed.

Default: No

46.14.10. Playbacks S + GO = PAUSE

This setting changes the function of S + GO on Playbacks to be a PAUSE function, when enabled. This is useful on wings that do not have physical PAUSE buttons. When set to "No", S + GO steps to the next step without time.

Default: No

46.14.11. Tap to Time buttons

Enables the SELECT, GO and PAUSE buttons, or a combination, to be set to Tap to Time for Playbacks.

Default: None

46.14.12. Int Master applies to LTP chans

This option makes Intensity Masters control any LTP channels that are recorded in the master Cue, rather than just HTP (Intensity) channels. This applies to existing masters, as well as newly created ones.

Default: No

46.14.13. Activate playbacks on start

This option enables one or more playbacks to be activated on startup.

When set to “Activate Playback PB”, Playback 1 is activated when MagicQ starts.

When set to “Last active” then after a reset, MagicQ will reactivate Cue Stacks that were running when the console was powered down or reset. MagicQ will start the Cue Stacks from the step that they were previously on.

Note that all the options except for the PB1 option are only available on MagicQ consoles or on MagicQ PC systems that are unlocked by a MagicQ Wing, Interface or SnakeSys device.

Default: None

46.14.14. Playback Go/Pause use Exec Grid 1

Enabling this option allows the GO and PAUSE Playback keys to control the first two rows of Execute grid 1. The GO keys will activate items on the first row, while the PAUSE keys will activate items on the second row.

Default: No

46.14.15. Playback holdover mode

This setting is used to enable Two Page Holdover mode, allowing Playbacks to be active on two different pages simultaneously.

When set to "Default" Playbacks can only be active one page - changing page causes the Playback to hold over active.

Default: Default

46.14.16. Run in Execute Window

This forces the Execute window into full screen mode when the system starts up.

See Execute Window

Default: No

46.15. Network Settings

46.15.1. IP Address

The IP address of the console ethernet network interface. This is stored as part of the console configuration; loading a new show does not change this setting.

On PC/Mac this must match the IP address of the network interface you are using. Double click on it to show the available network interfaces.

On PC/Mac you must also set the IP address of your adaptor in Windows Control Panel or Mac System Preferences.

For communicating with Art-Net the IP address is usually set to a number in the 2.x.x.x or 10.x.x.x range (e.g. 2.0.0.10) using subnet mask 255.0.0.0.

46.15.2. Subnet Mask

The subnet mask for the console ethernet network interface.

On PC/Mac this must match the network interface you are using.

For communicating with Art-Net the Subnet Mask is usually set to 255.0.0.0.

46.15.3. Gateway address

This should be set to 0.0.0.0 unless directed by ChamSys customer support.

Default: 0.0.0.0

46.15.4. Send to applications on this PC

This setting is used to send Output data internally to other applications on the same PC. This can be used to connect to a 3rd party Visualiser or the MagicQ Media Centre on the same PC.

This setting is valid for PCs and Macs only – it is ignored on MagicQ consoles.

Default : No

46.15.5. Art-Net Type

When set to "Normal" MagicQ transmits Art-Net protocol v3. MagicQ receives any Art-Net protocol. This is recommended when the universe count on the network is low.

When set to "V4 Unicast" MagicQ transmits Art-Net protocol v4, but also broadcasts packets on every universe once a second. This enables other Art-Net sources to determine that there is a transmitting Art-Net controller already outputting on that universe. and does not broadcast any Art-Net packets. This is the recommended protocol when using 32 or more Art-Net universes on the network.

When set to "V4 Unicast only" MagicQ transmits Art-Net protocol v4 and does not broadcast any Art-Net packets.

Default : Normal

46.15.6. sACN transmit priority

This is the sACN transmit priority.

If MagicQ receives sACN from more than one source to the same universe it will choose the highest priority source. If multiple sources have the same highest priority then the data will alternate between the various sources - avoid this.

46.15.7. RDMNet IP address

This is the IP address of the broker in RDMNet.

This should always be set 0 unless RDMNet is being used.

MagicQ RDMNet implementation is till under test.

Default: 0

46.15.8. RDMNet Port

This is the TCP port of the broker in RDMNet.

This should always be set 0 unless RDMNet is being used.

MagicQ RDMNet implementation is till under test.

Default: 0

46.15.9. Ethernet remote protocol

Enables transmit and receive of ChamSys Remote Ethernet Protocol (CREP) for communication over Ethernet (UDP/IP) with external 3rd party systems.

When using network sessions or multi console operation this option should be set to None.

There are options to enable tx, rx and both tx and rx. There are also options to use ChamSys Remote Ethernet Protocol without the header. Note that on receive (rx) MagicQ auto detects whether a header is present so can accept data CREP data with our without a header regardless of the header setting.

If set to None then any data received is ignored. When transmit (tx) is enabled, data can be transmitted from the Macro field of Cue steps in the Cue Stack.

See ChamSys Remote Ehthernet Protocol and Multiple Consoles for more details.

Default: None

46.15.10. Playback Sync Port

It is possible to configure the port used for synchronisation of playback between multiple MagicQ consoles. If this port interferes with other equipment for any reason then it is possible to change it.

Note that this port is also used for Net Sessions - so it must be the same on all systems using Net Sessions.

Default : 6553.

46.15.11. Web Server

This is used to enable the in-built Web server which enables remote access to the console functions from other equipment using web browsers.

The option “Enabled CSS” uses improved CSS style sheet web pages.

Default: Disabled

46.15.12. Web Server Port

The port used by the web server.

Default: 8080

46.15.13. Control net IP address

This can be used on PC and Mac systems as an alternative IP address for remote control from remote ChamSys systems. The PC/Mac must have a second network interface configured on the PC/Mac to a different IP network from the main IP Address.

Default: 0.0.0.0

46.15.14. Control net subnet mask

Subnet mask to go with the Control net IP address.

Default: 0.0.0.0

46.15.15. OSC Mode

The options are Disabled, Tx, Rx, Tx and Rx.

Default: Disabled

46.15.16. OSC Tx Port

The UDP port used for messages transmitted from MagicQ to external systems.

Default: 9000

46.15.17. OSC Rx Port

The UDP port used for messages received from MagicQ to external systems.

Default: 8000

46.15.18. OSC tx IP (0 = broadcast)

The IP address to send OSC messages to. When set to 0 the OSC messages are broadcast on the network.

Default: 0

46.15.19. Tracker rx

Enables connection to a remote tracker system. Remote tracker protocols are only supported on MagicQ consoles and MagicQ PC systems connected to MagicQ wings and interfaces or Rack Mount Dongle.

The options are None, DMX Input, MQ Track, PSN/SpotMe, Generic XYZ Tracker, Internal and Simulator.

When set to DMX Input, MagicQ receives tracker data for each Head directly on the DMX input corresponding to the output - for example if a Head is patched to Universe 1 channel 1 with pan and tilt on channels 10 and 12 respectively, then it will take the tracker data input for pan and tilt from input channels 10 and 12.

When set to MQ Track, MagicQ receives tracker data over a simple UDP protocol on UDP port 6549.

When set to OTP, MagicQ receives tracker data over Object Transform Protocol (OTP). The OTP function setting must be set to Tracker (rx).

When set to PSN/SpotMe, MagicQ receives tracker data from Robert Juliat tracking system.

When set to Generic XYZ Tracker the XYZ track information is received from a patched Generic XYZ Tracker head.

When set to Simulator, MagicQ generates a test pattern on the x and z positions of Trackers 1 and 2 in opposing directions for testing purposes. The simulator does not require MagicQ hardware.

When set to Internal, MagicQ does not receive tracking from any external devices, but it enables tracking from internal Trackers and MagicVis objects. When set to None, then Tracking is not enabled at all, even from internal Trackers and MagicVis objects.

The current value of received trackers can be seen in Setup, View System, View Status on the Trackers tab.

When tracker data is active MagicVis shows the tracker points as a green cross within the 3D space. If the tracker data is lost then the cross will turn red, and then after 2 seconds of not receiving any tracker data for that tracker the cross will disappear altogether.

The information from Trackers can be used by Palettes set as Track and also by Tracker Automations.

Default: None

46.15.20. Tracker tx

Enables transmitting of Tracker information to remote systems. Remote tracker protocols are only supported on MagicQ consoles and MagicQ PC systems connected to MagicQ wings and interfaces or Rack Mount Dongle.

The options are None, MQ Track, OTP, and Generate Track1, Generate Track2.

When set to MQ Track, MagicQ transmits tracker data over the MQ Track protocol whenever data for a Tracker changes. MQ Track protocol is a simple UDP protocol on UDP port 6549.

When set to OTP, MagicQ transmits tracker data over Object Transform Protocol (OTP). The OTP function setting must be set to Tracker (tx).

When set to Generate Track 1 or Generate Track 2 MagicQ transmits the respective Tracker only over MQ Track protocol.

Generate Track 1 and Generate Track 2 can be used on secondary MagicQ consoles / systems to send the Focus Hold XY position from the Plot view to a primary MagicQ console (using MQ Track protocol), thus enabling separate operators to control the tracking points in real time.

Default: None

46.15.21. OTP function

MagicQ supports E.159 Object Transfrom Protocol (OTP) for transmit and receive of tracker data and for transmitting and receiving MagicVis object position and rotation data.

When set to "Tracker (rx)" MagicQ receives Tracker data over OTP and acts as an OTP consumer. MagicQ assumes OTP System 1, Group 1 with the Point number mapping to the Tracker ID in MagicQ.

When set to "Tracker (tx)" MagicQ transmits Tracker data over OTP and acts as an OTP producer. MagicQ transmits OTP System 1, Group 1 with the Point number mapping to the Tracker ID in MagicQ and the name set to the relevant tracker - for example "Tracker 1".

When set to "MagicVis object (rx)" MagicQ accepts position and rotation data for the MagicVis objects modifying their position and rotation accordingly. MagicQ assumes OTP System 1, Group 1.

When set to "MagicVis object (tx)" MagicQ transmits position and rotation data for all the MagicVis objects and acts as an OTP producer. MagicQ transmits OTP System 1, Group 1 and Points starting from 1. MagicQ transmits the name for each point as the name of the object within MagicVis.

Receiving and transmitting Object Transfrom Protocol data is always supported on MagicQ consoles. On MagicQ PC and Mac systems it is only supported when unlocked with a MagicQ or SnakeSys interface.

46.15.22. MQ500 Network Switch

This controls the operation of the MQ500 internal network switch.

When set to "Normal" the network switch will only pass multicast messages on a particular network port when a device connected to the network on that network port has joined the multicast network.

When set to "Disable IGMP Snooping" the network switch will pass all multicast messages through the network switch regardless of whether any devices on the network have joined the multicast group.

"Disable IGMP Snooping" can be useful when connecting to some sACN devices that are not correctly joining the multicast group.

Default: Normal

46.16. WIFI Settings

46.16.1. Wireless mode

Some consoles have an inbuilt wireless access point for remote control from an iOS or Android tablet. Set to "Access Point" to enable.

This is only supported on MQ50 and MQ70. It is an option on Pro 2010 and Pro 2014 consoles via a USB adapter. The "Managed" and "Ad-hoc" options are deprecated and are not supported on new consoles.

On all other consoles and PC/Mac this setting must be set to "Disabled" - on these systems you can use an external wireless access point.

Default: Disabled

46.16.2. Wireless IP address

IP address of the console when using the inbuilt wireless access point. Must not be in the same range as the wired network address in the "Network" tab.

Default/recommended: 192.168.200.1

46.16.3. Wireless subnet mask

Subnet mask of the console when using the inbuilt wireless access point.

Default/recommended: 255.255.255.0

46.16.4. Wireless channel

Wireless channel (frequency) of the inbuilt wireless access point.

It is recommended to use either 1, 5, or 11.

Default: 1

46.16.5. Wireless SSID

Wireless network SSID (name) of the inbuilt wireless access point.

This will be the name that appears in the list of wireless networks on a device.

46.16.6. Wireless encryption

Wireless encryption type of the inbuilt wireless access point.

Should be set to WPA2. All other options are deprecated and are not supported on new consoles.

Default: WPA2

46.16.7. Wireless key

Wireless password of the inbuilt wireless access point.

Must be at least 8 characters.

46.16.8. Wireless DHCP Server

When enabled, MagicQ will automatically assign IP addresses to devices connected to the inbuilt wireless access point.

Default: Yes

46.16.9. Android tethering support

This feature is deprecated and should be set to "No".

46.17. Port Settings

46.17.1. MagicQ Wings and Interfaces

This setting enables MagicQ Wings and ChamSys USB interfaces to be connected. The options are No, Yes, and Yes – auto DMX.

On MagicQ consoles, when set to "Yes – auto DMX" then MagicQ automatically outputs on the rear DMX ports starting from Universe 1 – provided that none of the Universes have been explicitly set to “MQ Direct”.

On MagicQ PC/Mac when set to "Yes – auto DMX" then MagicQ automatically outputs DMX from a connected MagicQ Wing starting from Universe 1 – provided that none of the Universes have been explicitly set to “MQ Wing”.

There are additional options to choose betwen the VCP driver, the FTDI driver or both. Older products such as the MagicQ MiniWing, MagicQ Maxiwing, MagicQ Extra Wing and MagicQ PC Wing require the FTDI driver. MagicQ PC Wing Compact and Extra Wing Compact can use the VCP driver.

This option also enables MagicQ to search for SnakeSys products on the network to unlock demo mode on PCs and Macs.

If it is set to No" then MagicQ does not lock for USB interfaces or for SnakeSys products on the network.

Default: Yes - auto DMX

46.17.2. MagicDMX mode

The options are None, DMX Out or DMX In. This option defaults to DMX Out.

Setting the Out Type of Universe 1 in Setup, DMX I/O to MagicDMX will automatically set this option to DMX Out.

Note that DMX In is not available on the MagicDMX Basic version.

Default: DMX Output

46.17.3. Audio input

MagicQ supports 14 channels of audio - 7 frequencies each on a received left and right channel.

On MagicQ consoles with inbuilt audio ports use "Console inbuilt port".

On PC or Mac when using inbuilt sound card use "PC/Mac sound card". Audio input on PC/Mac is only supported when the system is unlocked by a MagicQ Wing or Interface or SnakeSys device.

The options “Energy only ChamSys audio”, “ChamSys audio interface” and “ChamSys audio left only” relate to the ChamSys USB Audio interface.

"Energy only ChamSys audio" analyses the 14 channels received and creates a single energy channel which is then copied to all the other channels. "ChamSys audio left only" copied the data received on the left channels to the right channels.

See Audio for full details on audio input.

Default: None

46.17.4. Audio min level

The minimum levels of the audio input. The minimum is used to adjust for noise.

When set to a non zero value any levels below the minimum are ignored and the levels above the minimum are scaled appropriately.

See Audio for full details on audio input.

Default: 0

46.17.5. Audio max level

The maximum level of the audio input. Useful if the audio signal is particularly weak.

When set to a non zero value any levels above the maximum are ignored and the levels below are scaled appropriately.

See Audio for full details on audio input.

Default: 0

46.17.6. Audio output volume %

The audio volume from 0% to 100%.

Default: 100%

46.17.7. Audio output mute

Options are "Not Muted" and "Muted".

Default: Not Muted

46.17.8. Remote trigger type

This setting specifies how the remote input port on MagicQ consoles, MagicQ PC Wings and MagicQ MaxiWings works.

It can be set to None, Make, Break or Make + Break.

It can also be set to MIDI Beat, MIDI Beat Half and MIDI Beat Qtr for triggering from the MIDI Beat Clock instead of from the remote input.

Default: None

46.17.9. Remote trigger action

This setting specifies specific global actions to be taken on a remote trigger input. The options are:

The options are:

  • None
  • Current Playback GO
  • Current Playback FLASH
  • Add/Swap
  • Swap
  • DBO
  • Wing1 PB1 GO
  • Wing1 PB1 FLASH
  • Wing1 PB12 GO
  • Wing1 PB12 FLASH
  • PB10 GO
  • PB10 FLASH
  • Audio Bump
  • Tap to time select

The remote trigger can be used on a per Cue Stack basis by setting the Halt field of Cue step in the Cue Stack to “Remote”. This is independent of any global action specified by the Remote trigger action setting.

Audio bump simulates audio received at full level. It is processed by MagicQ just as if the "bump" had been received from the audio port or the MagicQ Audio Interface, bumping any Cue Stacks set to Audio Bump.

Default: None

46.17.10. 10Scene mode

Specifies mode of 10Scene devices.

When set to "Execute 1" the 10Scene controls items 1 to 10 on Execute Grid 1.

When set to "PB 1 to 10" the 10Scene controls Playbacks 1 to 10.

Default: Disabled

46.17.11. Serial COM port

MagicQ supports one serial port for remote connections. On MagicQ consoles select COM1.

On MagicQ PC select a COM port from COM1 to COM8 depending on which COM port you wish to use.

Default: COM1

46.17.12. Serial baud rate

MagicQ consoles support baud rates from 300 to 57600. Baud rates supported on MagicQ PC will depend on the PC.

Default: 9600

46.17.13. Serial parity

MagicQ PC supports None, Odd, Even, Mark and Space. MagicQ consoles only support None, Odd, Even.

Default: None

46.17.14. Serial data bits

Data bit sizes of 4,5,6,7 and 8 are supported.

Default: 8

46.17.15. Serial stop bits

MagicQ PC Supports 1,1.5 or 2 stop bits. MagicQ consoles support 1 or 2 stop bits.

Default: 1

46.17.16. Serial remote protocol

Determines what protocol is used on the serial port. If set to "None" then any data received is ignored. Data can be transmitted from the Macro field of Cue steps in the Cue Stack.

The other protocols are:

  • ChamSys Rem (rx)
  • ChamSys Rem (tx & rx)
  • ChamSys Rem (tx)
  • Ideal Touch
  • A1 Touch
  • Elo Touch

The Touch protocols are for the use of external RS232 serial touch screens with the MQ50 (old), MQ100, MQ200 and MQ300 consoles. Refer to the instruction manual of your touch screen for other serial settings.

See Controlling MagicQ using the serial port for more details.

Default: None

46.17.17. Serial touch monitor

Determines which monitor on the MagicQ system has a touch screen connected to the serial port.

46.17.18. Monitor Settings

The Monitor settings have been moved to Setup, View System, View Monitors.

46.18. MIDI / Timecode Settings

46.18.1. Timecode frame type

The timecode type can be set to EBU 25, SMPTE30, NTSC30 and Film 24.

When enabled the Status Display will show the current timecode being received from the module.

Default: EBU 25

46.18.2. Timecode continue frames

When MagicQ is set to external timecode and the external timecode source is temporarily lost MagicQ automatically continues to increment the timecode. This parameter specifies how many frames MagicQ continues generating for before it stops. After this number of frames the timecode will be frozen until a signal is received again.

Default: 50

46.18.3. Timecode jump detect frames

The timecode jump detect parameter is the number of frames that MagicQ waits before performing a jump. This allows spurious timecode values to be ignored.

Default: 10

46.18.4. Timecode decode

This option controls which external source is used for timecode input.

The main options are None, LTC, MIDI, Art-Net, Winamp, Virtual (USB) MIDI, TCNet, and Internal MagicHD.

LTC and MIDI are for use with the inbuilt LTC and MIDI ports on MagicQ consoles and when connecting to a ChamSys MIDI/SMPTE interface.

Art-Net enables receiving timecode over Art-Net protocol whilst Winamp is received from a Winamp instance running on the same PC and Virtual (USB) MIDI receives from any USN MIDI device or another application on the same PC with virtual MIDI.

Internal MagicHD receive directly from MagicHD when it is running as part of the same MagicQ application.

The options "LTC+Art-Net" and "MIDI+Art-Net" provide resilience where the LTC or MIDI is the primary source, but if this is not available then MagicQ will fall back to using received Art-Net timecode.

When set to "None" then timecode is not accepted from any source.

When this option is set to anything other than None, then timecode generation (below) should be set to either "None", or "Art-Net (retransmit)".

On MagicQ PC/Mac systems Winamp, Art-Net timecode and Virtual (USB) MIDI are only available when the system is unlocked via a MagicQ USB Wing or Interface, or a SnakeSys device.

Default: None

46.18.5. Timecode generation

The options are None, LTC, MIDI, Art-Net (retransmit) and Virtual (USB) MIDI.

When set to LTC or MIDI the MagicQ system generates timecode. The timecode values can be set be initialised, reset and modified using Cue Stack commands W and Q. W1 to enable, W2 to disable. Q Timecode where Timecode is value in frames.

Art-Net (retransmit) causes any timecode received via sources other than Art-Net to be retransmitted on the network as Art-Net timecode. This allows resilience to be built up in multi console systems where timecode is received into multiple MagicQ consoles and forwarded over the network using Art-Net timecode.

When this option is set to LTC or MIDI, then timecode decode should be set to None.

Default: None

46.18.6. Timecode backward jumps

The options are Normal, Adv backward Jump, Backward Jumps > 1 second.

Normal is the original MagicQ backward jump handling.

Advanced is the handling that was previously available on a debug option.

Backward Jumps > 1 second ignores backward jumps unless they are greater than 1 second - this option may help with some systems which can send small backwards jumps when they stop.

Default: Normal

46.18.7. Timecode activate/release

The options are Normal, Activate/Release TC Playbacks and Activate/Release TC Playbacks at Full.

When set to either of the Activate/Release options TC Playbacks will automatically activate when the TC value for the first cue is received and release after the last cue TC value is received.

The Activate at Full option can be used to ensure that the Playback activates at Full, ignoring the physical fader level on the console.

Default: Normal

46.18.8. MIDI In Type

Setting for determining how MIDI channel messages are processed. The options are None, Any Channel or Requested Channel.

When set to Any Channel MagicQ will process MIDI notes received on any MIDI channel.

When set to Requested Channel then MagicQ will only process MIDI notes received on the MIDI In Channel that is set.

This option can be used at the same time as timecode in / timecode generation.

Default: None

46.18.9. MIDI In Chan

The MIDI Channel that MagicQ will listen to. When set to 0 it accepts MIDI commands on any MIDI channel.

Default: 0

46.18.10. MIDI Out Type

Setting for determining how MIDI channel messages are sent.

The options are None, Any Channel or Requested Channel.

When set to Any Channel MagicQ will send MIDI notes on the channel specified in the macro field in the Cue Stack.

When set to Requested Channel then MagicQ will always send the MIDI notes on the MIDI Out Channel that is set regardless of the channel specified in the macro field in the Cue Stack.

This option can be used at the same time as timecode in / timecode generation.

To send notes from the macro field in the Cue Stack:

<note on/off> <note> <velocity>

For example, to send a note for middle C set the macro field to the following:

N144,60,127 // Note 60 on velocity 127

N128,60,0 // Note 60 off

Default: None

46.18.11. Midi Out Chan

The MIDI channel that MagicQ will send out on.

When set to 0 it outputs on the MIDI channel specified in the Cue Stack macro field. When set to non zero it overrides the MIDI channel.

Default: 0

46.18.12. MIDI Show Control Type

The options are Normal, Cue Stack 1, Playback 1. This determines which Cue Stack is triggered when MIDI Show Control (MSC) commands are received.

In Normal, MSC commands with two parameters (Q number, Q list) will trigger Cue Stacks in the Cue Stack Store. MSC commands with one parameter (Q number) will trigger Cues in the Cue Store.

Default: Normal

46.19. Multiple Console Settings

46.19.1. Enable remote access

Enables other devices or consoles to communicate with MagicQ over the network.

This option must be set to Yes when using Net Sessions, Show Sync, remote file access, and when using MagicQ Remote apps.

It must also be set when operating a MagicQ console with the stand alone MagicVis.

Default: No

46.19.2. Enable remote control

Enables devices and consoles to remote control MagicQ using the MagicQ remote control feature.

This setting must be set to Yes for remote controlling one MagicQ console from another, when using external Multiwindow and when using MagicQ Remote Apps.

Default: No

46.19.3. Net Session Mode

Enables network sessions, allowing multiple consoles to communicate show and playback information over a network. The options are:

  • “None” - No network communication or show/playback sync is allowed to or from this console.
  • “Manual Takeover” - Show and playback Sync will be allowed with Consoles in the same session. However, the console will not take over outputting DMX if the master is lost, until told to do so by the user.
  • “Auto Takeover” - Show and playback Sync will be allowed with Consoles in the same session. The console will automatically take over outputting DMX if the master is lost after a period of time without any interaction from the user.

Im most situations we recommend "Manual Takeover" rather than "Auto Takeover".

See Multiple Consoles for full details on using multiple MagicQ consoles in a network.

Default: None

46.19.4. Net Session ID

For use in Network Sessions to specify the current session the console is a member of.

Consoles in a session should be set to a number other than 0 when using net sessions, to avoid an unconfigured console attempting to join a session when it is started.

Default = 0

46.19.5. Playback Sync Slave Mode

When Network Session Mode is set then this specifies whether the Slave synchronises its playbacks to the Master.

When set to "PB Sync" the Slave playbacks are synchronised to the Master playbacks. Pressing playback buttons or changing fader levels on the Slave has no effect.

When set to "PB Sync, multi control" the playbacks on the Master and Slave are synchronised together, with either console being able to make changes via playback buttons and fader levels.

When set to “Inhibit PB Sync” the Slave playbacks are not synchronised – this is useful during the programming phase when creating a show using multiple consoles.

When set to "Inhibit, sync on swap" the Slave playbacks are not synchronised, but the Slave stores the Master state and if the Slave swaps to become the Master then it starts from the stored state.

For show playback, the Slave playbacks are normally synchronised to the Master.

Default: Inhibit PB sync

46.19.6. Programmer sync mode

When Network Session Mode is set then this specifies whether the Slave synchronises its programmer to the Master.

When set to "No Sync" the Master and Slave consoles operate separate programmers. Any changes in the Programmer on the Master are completely independent to changes in the Programmer on the Slave. Each console can record, and update different Cues independently.

When set to "Sync Programmers" the programmers are synchronised - any changes in either programmer immediately modify the other programmer. This allows to operates to control different lights but to record and update the same Cue at the same time. When a Cue is recorded or updated the complete programmer is used for the record or update.

Default: No Sync

46.19.7. Hot Takeover Mode

This option is now superceeded by the Network Session Mode. For manual monfiguration of this option see Manual Configuration of Multi Console.

The options are:

  • "Split Unis" – Universe enable/disable is controlled independently on each console, allowing each console to send a specific set of universes.
  • "Equal" – Each Console has equal Priority to be a master or slave, the first console to start will be the Master.
  • "Manual" – Hot takeover will only enabled/disable universe when told to do so by the user.
  • "Prefer Master" – This console will always be designated the master in a multi console network.
  • "Prefer Slave" – This console will always be a slave in a multiconsole network unless no other consoles are found then it will promote itself to master when alone.
  • "Inhibit Outputs" – Prevents any console in the system, master or slave, from outputting DMX. This can be used to disable the data from a system when a “Guest” console is being used.

Default: Split Unis

46.19.8. Hot Takeover Detect Time

When Network Session Mode is set to “Auto Takeover”, this setting specifies how long after a Slave detects there is no Master on the network that it takes over control as Master.

Default: 5.00 sec

46.19.9. Hot Takeover Fade Type

When Network Session Mode is set to “Auto Takeover”, this setting specifies when a Slave becomes a Master, whether the output state is held or an automatic fade is carried out to the output of the new Master.

  • "Automatic" - Loads a snapshot of the last data from that universe into the Programmer and then automatically clears the programmer using the hot takeover fade time.
  • "Manual" - Loads a snapshot of the last data into the Programmer. The universe will be completely controlled from within the Programme. The operator can then set up the playbacks as they wish and then clear the programmer to change to this new look. Clearing the programmer with time enables the operator to specify a fade time to the new look.

Default: Automatic

46.19.10. Hot Takeover Fade Time

When Network Session Mode is set to “Auto Takeover” and Hot Takeover Fade Type is set to "Automatic", then this setting specifies how long it takes to fade the output when a Slave becomes a Master.

Default: 3.00 sec

46.19.11. Playback Sync Type

This option is now superseded by the Network Session Mode.

For manual configuration of this option see Manual Configuration of Multi Console.

46.19.12. Playback Sync IP

This setting is now superseded by the Network Session Mode which automatically configures this setting.

For manual configuration of this option see Manual Configuration of Multi Console.

When set to 0, playback sync is accepted from any MagicQ console on the network.

46.19.13. Show data Sync Type

This setting is now superseded by the Network Session Mode which automatically configures this setting.

For manual configuration of this option see Manual Configuration of Multi Console.

46.19.14. Show data Sync IP

This setting is now superseded by the Network Session Mode which automatically configures this setting.

For manual configuration of this option see Manual Configuration of MultiConsole.

46.20. Hardware Settings

46.20.1. Level above 0 to activate LTP

This setting can prevent playbacks being triggered in error by reducing their initial sensitivity. Setting this to a level above 0 (e.g. 5) may remove any accidental triggers.

Default: 000

46.20.2. Hysteresis on fader / encoder moves

In some circumstances where faders or encoders have become faulty and generate excess noise, setting this to a level above 0 (e.g. 5) may remove the noise.

Default: 000

46.20.3. Encoder Damping

Use this option on a MagicQ PC Wing to improve the performance of the encoder wheels. This option does not have any effect on MagicQ consoles.

Default: Damped

46.20.4. Touch Screen

The console touch screen can be disabled with this setting for cases where it may be faulty and causing issues.

Default: Enabled

46.20.5. Encoders

The encoders can be disabled for cases where they may be faulty and causing issues.

Default: Enabled

46.20.6. Faulty Faders Mask

The faders can be disabled for cases where they may be faulty and causing issues.

The following values can be used:

  • Set to 1 to disable the main faders.
  • Set to 2 to disable Wing 1 lower faders.
  • Set to 4 to disable Wing 1 upper faders.
  • Set to 8 to disable Wing 2 lower faders.
  • Set to 10 to disable Wing 2 upper faders.

Default: 00000000

46.20.7. Power Fail Detection

This setting disables power fail detection for the current session in case the console has developed a fault and is falsely reporting power fails.

This setting will return to default upon a reset / power on.

Default: Enabled

46.20.8. Screen Save

This setting can be used to disable screen save for the current session.

This setting will return to Enabled upon a reset / power on to protect display life.

Default: Enabled

46.20.9. Reduced rate output

This setting determines how output data is sent.

When set to "Continuous" MagicQ outputs data regardless of whether it is changing. This can cause high network loads.

When set to "Changes only" MagicQ only outputs data only on changes, except once per second where it will send regardless of whether data has changed. This means that when data is not changing it reduces the output data from 39 frames a second down to 1 frame.

When set to "Mixed" MagicQ interleaves the output frames from the different universes so that network devices with small buffers will still be able to decode the correct universes on heavily loaded networks.

When set to "Mixed and Changes only" this has the benefit of both above options - this is the recommended setting.

When set to "M+C Repeat" it is the same as "Mixed and Changes only" except that after data changes MagicQ sends the data one extra time after it changes to give the network device two chances of seeing the change.

When set to "M+C No Broadcast" it is the same as "Mixed and Changes only" except that MagicQ never broadcasts Art-Net packets.

The "M+C MQ80 Reduced" and "No Seq" setting should not be used unless directed by ChamSys customer support.

Some older DMX equipment is not able to work at full DMX speed. In these cases, use the “Reduced rate output” to reduce the DMX data and/or refresh rate. This option reduces the rate of data MagicQ sends over the network or via USB to the interface. It may not affect the actual DMX rate as this may be controlled by the interface itself.

Some older DMX equipment may not be able to receive full DMX packets at the required rate. If less than 120 are used in the Patch then the "Short packet (120 chans)" option can be tried.

Data packets sent to MagicVis, WYSIWYG and Capture are sent only when the data changes. The reduced rate options do not affect the MagioVis, WYSIWYG or Capture data.

Default: Mixed + Changes only

46.20.10. DMX512 Frame Timing

This setting determines the timing for the direct DMX512 frame. This setting only applies to MagicQ Compact Consoles, this is the MQ80, MQ70 and MQ50.

When set to "Maximum (default)" the console will output direct DMX512 data at its fastest speed, which is its default option. The break will be 100 μs, the mark after break (mab) will be 12 μs and the slot time will be 50 μs giving a inter-byte time of 6 μs.

The following settings below can help when some fixtures flicker due to missed frames as they can’t keep up with the defalt frame timing.

When set to "Fast" the console will output direct DMX512 data with a break of 150 μs, mab of 50 μs and a slot time of 53 μs giving a inter-byte time of 9 μs.

When set to "Slow" the console will output direct DMX512 data with a break of 250 μs, mab of 100 μs and a slot time of 56 μs giving a inter-byte time of 12 μs.

46.20.11. Display Edge

The MQ50 and MQ70 consoles are designed for minimum size to fit in hand carry restrictions and therefore the display edge is closer to the surrounding bezel than on other MagicQ consoles. The display edge option enables the window edge to be modified so that they are more visible.

Default: 0

46.20.12. Movie Buffer frames (0=use default)

MagicQ uses buffering for Movie clips. By default (when this is set to 0) MagicQ uses a buffer size of 128 frames. MagicQ will always use a minimum of 128 frames regardless of this setting.

On consoles using a solid state drive, this setting won’t make a significant difference.

Default: 000

46.20.13. Debug Mode (Must be 0)

For ChamSys internal debugging only. Must be set to 000.

Default: 000

46.20.14. Standard Logging

This option should always be enabled, except when directed by ChamSys support.

Default: Yes

46.20.15. Extended Logging

This option allows extended logging to be enabled. ChamSys support may request that Extended Logging is enabled in order to investigate any issues.

Default: No

46.21. General Settings

46.21.1. Splash screen image

Users can now add their own splash screen by copying their splash image named usersplash.bmp into the MagicQ folder. This will be used in favour of the default splash.bmp.

46.22. Individual Playback Settings

Settings for individual Playbacks (Cue Stacks) are configured from the View Options and View Defaults views in the Cue Stacks Window. See Playbacks.

46.23. Calibrating the touch screen

If the touch screen does not respond accurately to the position that you are pressing on the screen then you may need to re-calibrate the touch screen. Don’t be afraid, this is a painless exercise!

In the Setup Window press the Cal Touch button - use the physical button rather than the pressing the touch screen. This puts the screen into calibration mode. To calibrate the touch screen simply press the screen in the bottom left corner of the screen and then the top right corner of the screen. Press the screen on the corners where the displayed graphics starts/ends.

It does not matter which order you press the screen in. If you feel you have pressed the wrong bit of the screen just press the screen again in the correct position.

When you are satisfied you have pressed the correct position then press Cal Touch button to leave the calibration mode. Make sure you use the physical button rather than pressing the touch screen, as pressing the touch screen messes up the calibration.

You should now find that the touch screen is more accurate. If you continue to have problems then try pressing the screen with a small blunt object, but don’t use a sharp object as it may damage the touch screen.

When calibrating external touch screens calibrate only 1 touch screen at a time. Pressing in more than one screen will cause unpredictable results.

46.24. Displays brightness and contrast

To modify the brightness of the main display, press CTRL and adjust the bottom right encoder.

To modify the brightness of the LCD displays on the wing, press CTRL and adjust the next encoder up on the right.

To turn all the displays off press CTRL and the button associated with the bottom right encoder.

To turn off the all the lights on the console (i.e. the displays, the console lights and the LEDs) press CTRL and the "All Lights" off button.

To modify the contrast of Playback wings use the Wing Contrast encoder.

When multiple Playback wings are connected press CTRL and the Next Page button of the Wing you wish to change the contrast on.

46.25. Console lamp brightness

To modify the brightness of the console lamps press CTRL and adjust the top right encoder. To turn all console lamps on or off, press CTRL and the button associated with the top right encoder.

46.26. Button LED brightness

To modify the brightness of the LEDs on the buttons, press CTRL and adjust the bottom left encoder.

Note that the brightness of the LEDs can only be adjusted from full to dim - they can not be turned off completely. This ensures that there is always an indication that the console is powered.

46.27. Controlling console lamp from the programmed show

The console lamp brightness, display brightness and LED brightness can now be controlled as a Head within the programming of the show.

Patch one “Generic MQlamps” at any free address. The Head can be unpatched to ensure that it does not affect any real channel outputs. The Head has the following attributes:

  • activate set to 255 to take control of the console brightness
  • master master level for brightness
  • white lamp brightness
  • blue lamp brightness
  • main display brightness of display – 0 is off
  • wing display
  • led brightness of the LEDs

Note that the screen saver will still blank the display.

46.28. Locking the console

The console supports a simple locking mode to avoid accidental button presses affecting the output or programmed data. Press CTRL and the button associated with the top left encoder to lock / unlock the console. The console will not accept any button presses while it is unlocked.

A more advanced password system will be included in future software releases.

46.29. Button test mode

The console supports a button test mode for checking suspect buttons and faders. To enter button test mode on MQ100/200/300 consoles press the two SHIFT buttons either side of the touch screen together (i.e. hold one down and press the other).

To enter button test mode on Compact consoles MQ40/60/70, press CTRL + ALT + SHIFT together to enter and exit board test mode.

In button test mode the buttons do not have their usual function - instead when pressed a message will be displayed in the status display indicating which button has been pressed. Faders and encoders also can be tested in a similar way.

In button test mode the Window shows a map of all the buttons, encoders and faders. When a button is pressed the map turns green to indicate that the button has been pressed and released o.k.

For encoders it turns green when the encoder has been turned both ways. For faders it turns green when the fader has been lowered to 0 and raised to full.

To test LEDs, enter button test mode and then press CTRL 1 and CTRL 2 to test the different colour LEDs. Press CTRL 0 to go back to normal state of the LEDs.

Button test mode is exited in the same way that it is entered.

On MagicQ PC to enter button test mode type “test” on the keyboard then hold SHIFT and CONTROL. Hold SHIFT and press CONTROL to exit button test mode.