Introduction: The Reality of Mixed Rigs

Modern lighting systems are rarely homogenous. From global touring productions to local rental shows, it's common to encounter fixtures from different brands serving the same function—be it wash, beam, or profile. Managing these inconsistencies effectively is critical for maintaining visual coherence across cue stacks.

Enter fixture cloning: a powerful feature found in most professional lighting consoles, enabling you to duplicate programming data from one fixture type to another, even if the hardware models differ.

But cloning across different brands isn’t always plug-and-play. It requires a deep understanding of fixture parameters, control logic, and show structure. This article explores how to manage this process strategically for professional, scalable results.

What Is Fixture Cloning?

Fixture cloning refers to the process of copying programmed data—such as intensity, color, position, beam, and effect—from one group of fixtures (the "source") to another (the "target"). This is typically used when:

• A rig change introduces different fixture models

• Touring shows adapt to venue-specific inventories

• You need to scale up or down with minimal reprogramming

• Rental houses substitute brands between stops

Most major consoles—like MA2/MA3, Avolites, Chamsys, ETC EOS—support fixture cloning, but success depends on how closely matched the source and target fixtures are.

Cross-Brand Cloning: Where the Problems Begin

Cloning between identical fixtures is straightforward. The challenge arises when fixtures differ in:

• Channel layout or mode

• Color system (e.g. RGB vs. CMY)

• Zoom and focus parameters

• Gobo wheels or prism configurations

• Pan/tilt ranges or physical orientation

For example, cloning from a Martin MAC Aura (RGBW) to a Robe Spiider (RGBW + Flower Effect) might partially succeed—but without intentional mapping, effects could behave unpredictably.

Step-by-Step: Cloning Across Different Brands

1. Prepare Your Show File with Placeholders

Design your show with fixture groups and presets from the start. This ensures that when you clone later, your data structure is reusable and logical.

2. Identify Source and Target Fixture Types

Before cloning, compare the fixture profiles (personalities) in your console. Key aspects to compare:

• Number of channels

• Color mixing method (RGBW, CMY, RGBWA+UV)

• Movement ranges

• Beam attributes

3. Use Console's Clone/Swap Feature

On platforms like MA3:

plaintext 
Clone Fixture 101 Thru 106 At 201 Thru 206 If Sequence 1

This copies all relevant data in the specified sequence, preserving cue timing and fade/delay values.

On Chamsys MagicQ, use:

• [Clone Fixtures]

• Map color, position, and beam manually if modes differ

4. Validate Parameters

After cloning:

• Check preset references—particularly for color and position

• Validate effects—since waveform or phase settings may interpret differently

• Watch for default pan/tilt inversions between brands

Use visualizer tools (Capture, Depence, MA3D) to pre-check how cloned fixtures respond.

Best Practices for Mixed Fixture Environments

Use Preset-Based Programming

Fixtures cloned by raw values (e.g. DMX 120) will not translate well. Programming via parameter-specific presets (like Position: “Downstage Right”) allows better interpolation across models.

Label Groups Clearly

Group similar fixture types by function and brand (e.g. "Wash_Aura", "Wash_Spiider"). This simplifies tracking of source-target relationships when cloning.

Store in Recipes or Sequences

In MA3 and EOS, using recipes or magic sheets provides flexibility in fixture substitution without needing full cue reprogramming.

Real-World Scenario: Touring with Fixture Variants

A touring company programs their show using Robe MegaPointe profiles. Upon arrival at a regional venue, the inventory only includes Clay Paky Sharpy Plus. The lighting programmer does the following:

1. Adds Sharpy Plus into the patch

2. Clones MegaPointe data to Sharpy Plus using presets

3. Reviews position and gobo differences

4. Adjusts color correction to match CTO behavior

5. Locks intensity and position for showtime

While full 1:1 matching is impossible, a seamless visual handoff is achieved.

Challenges in Cross-Brand Cloning

The Role of Virtual Fixture Mapping

Some advanced lighting platforms (e.g. MA3, EOS Augment3d) support virtual fixture mapping, where abstracted parameter values (e.g., Color Temperature 3200K) are rendered across compatible outputs.

This enhances cloning across:

• CMY vs. RGB

• 3-channel vs. 6-channel LED engines

• Fixtures with or without CTO

When paired with fixture-specific calibration curves, results can be surprisingly accurate.

Tips for Success in a Mixed-Brand Workflow

• Maintain a library of commonly used fixture profiles and showfiles

• Familiarize yourself with multiple brands’ feature sets

• Use console macros to automate cloning and validation tasks

• Partner with rental vendors early to verify inventory before show day

• Build your programming style around function-based logic, not device-specific tricks

When Cloning Isn’t Enough

In some cases, cloning is not practical or advisable:

• Cloning from effect-rich fixtures to basic LEDs may yield unsatisfying results

• Mismatched gobos or pixel mappers often require full preset rebuilding

• When timing precision is critical (e.g., televised events), manual tweaks are unavoidable

Use cloning as a tool, not a crutch.