NovaStar MCTRL660 PRO: wiring and configuring the 6-port controller

The NovaStar MCTRL660 PRO is an independent controller: it takes a video source, splits it and sends it to the receiving cards, without storing content. It fills the gap between the standalone Taurus players and the large processors such as the MCTRL4K.

Its technical case is clear: six Gigabit Ethernet ports at 650,000 pixels each in 8-bit, two 10G optical ports where the second duplicates the first for redundancy, and three video inputs including one 3G-SDI. It also works as a fibre converter, which simplifies touring architectures where the control position sits far from the screen.

This tutorial covers the inputs and their real limits, copper and optical wiring, load calculation by colour depth, cascading up to eight units, Genlock, NovaLCT configuration and troubleshooting. Every figure comes from the MCTRL660 PRO specifications sheet V1.4.2.

1. What an independent controller is

An independent controller has neither content memory nor a publishing system: it turns an incoming video signal into frames destined for the receiving cards. The source stays external — media server, control desk, computer, camera — and the controller only distributes it across the wall.

That architecture suits three project families: live events, where the source changes with every job; control rooms, where the source is a third-party system; and fixed installations driven by an existing media server. In all of those, an asynchronous player would be the wrong tool.

• No content storage: the video source stays external.
• Six Gigabit Ethernet output ports plus two 10G optical ports.
• Also works as a standalone fibre converter.
• Three video inputs: 3G-SDI, HDMI 1.4a and single-link DVI.
• Cascade of eight units over a USB link.

2. Official technical specifications

The figures below come from the MCTRL660 PRO specifications sheet, revision V1.4.2.

3. The three inputs and their real limits

The three inputs are not equivalent, and the choice determines usable resolution. The 3G-SDI input accepts SMPTE ST 425-1 A/B as well as ST 274, ST 296 and ST 295, capped at 1920 × 1080 at 60 Hz. It offers neither resolution nor bit-depth settings: the signal is taken as it arrives.

The HDMI 1.4a input handles HDCP 1.4, allowing common protected sources. The single-link DVI input handles HDCP 1.3. Each input has a loop-through, essential to feed a confidence monitor or a second controller without an external splitter.

On a set, prefer the SDI input as soon as the cable run exceeds ten metres: coaxial SDI handles distance far better than HDMI, and the loop-through lets you chain a confidence feed with no extra hardware.

4. Calculating the load port by port

This is the decisive calculation of any deployment. In 8-bit, each Ethernet port carries 650,000 pixels; in 10 or 12-bit that drops to 325,000. Moving to extended depth therefore halves capacity, which catches out teams that size in 8-bit then enable 10-bit for image quality.

Six ports in 8-bit give 3,900,000 pixels in total; the same six ports in 10-bit give only 1,950,000. The colour-depth question must be settled at design stage, not while adjusting on site.

Never size a wall at 8-bit capacity if the brief mentions 10-bit or broadcast. Halving the per-port load is a hardware constraint, not a software setting you can work around.

5. Using the two 10G optical ports

Each 10G optical port carries the equivalent of the six Ethernet ports. Port OPT2 duplicates OPT1: it does not double capacity, it provides a backup path. That distinction is essential for sizing — two fibres do not mean twice the pixels.

The typical use is the long-distance link between the control position and the screen: one fibre runs from the controller to a converter at the base of the wall, which redistributes over copper. The second fibre follows a different physical route, protecting against an accidental cut of one cable path.

• OPT1: primary path, capacity of the six Ethernet ports.
• OPT2: duplicate of OPT1, backup path, no additional capacity.
• Route the two fibres through physically separate paths.
• The MCTRL660 PRO can act as a fibre converter alone, without controller duties.

6. Cascading eight units

Up to eight MCTRL660 PRO units can be chained over their USB link, allowing the whole set to be driven from a single NovaLCT station. The cascade serves administration: each unit keeps its own video source and its own screen zone.

In practice the units must be numbered physically and that numbering respected in software. On tour, a rack whose controllers are not labelled in the same order as the screen zones always costs time at the next build.

• Chain the units over USB, in the physical order of the rack.
• Label each unit visibly with its cascade number.
• Drive the whole set from a single NovaLCT station.
• Back up each unit's configuration separately.

7. Genlock and synchronisation

The MCTRL660 PRO accepts a Genlock reference in Bi-Level, Tri-Level or Blackburst, with loop-through. It is essential as soon as several controllers feed one wall or the wall is filmed: without a common reference, surfaces scroll with an offset visible on camera.

Declared latency is one frame in vertical configuration. On a television set or a live capture, that figure must be given to the vision desk so it can be compensated in the mixer.

• Distribute a single Genlock reference to every controller on a wall.
• Use the loop-through to chain the reference without a distributor.
• Report the one-frame latency to the vision desk.
• Verify synchronisation with a moving test pattern, not a still image.

8. Configuring with NovaLCT

Configuration follows the standard NovaLCT procedure: connect the PC to the controller, establish the link in software, set the input source, light the screen, then load or build the cabinet configuration. The configuration must be saved to the receiving cards to survive a power cut.

The MCTRL660 PRO adds independent gamma adjustment per red, green and blue channel in 10 and 12-bit, compatibility with pixel-level calibration, image mirroring and a web interface for backing up and restoring settings.

• Set the input source: SDI, HDMI or DVI.
• Load the cabinet configuration file and declare the wiring.
• Enter the output resolution and the chosen colour depth.
• Adjust gamma per channel if colorimetry requires it.
• Save to the receiving cards then back up the settings from the web interface.

Use the web interface backup at the end of every commissioning and archive the file with the site folder. On tour that backup restores a full configuration within minutes after a hardware swap.

9. Custom resolutions

The controller's standard resolution is 1920 × 1200 at 60 Hz. For unusual formats it accepts custom resolutions up to 3840 pixels in width or height: for example 3840 × 600 at 60 Hz for a very wide ribbon, or 800 × 3840 at 30 Hz for a vertical totem.

Those two examples show the logic: as total surface grows, the available refresh rate falls. A trade-off between definition and smoothness is therefore needed, and it must be approved with the customer before panels are manufactured.

10. Field troubleshooting

In rental work, faults are diagnosed under pressure and often in front of the client. This table gives the most efficient check order for the most frequent symptoms.

Deployment procedure

1. Choose the colour depth

   Settle between 8-bit (650,000 px per port) and 10/12-bit (325,000 px per port) before sizing the wall.

2. Select the video input

   Use 3G-SDI for long runs, HDMI 1.4a or DVI for computer sources, checking HDCP compatibility.

3. Wire the outputs

   Connect the six Ethernet ports to the approved split, and engage OPT1 to the remote converter if the run is long.

4. Set up optical redundancy

   Connect OPT2 as the backup path for OPT1, on a physically separate route.

5. Cascade controllers if needed

   Link up to eight units over USB in the physical order of the rack, labelling each unit.

6. Distribute Genlock

   Send a common Bi-Level, Tri-Level or Blackburst reference and verify sync with a moving test pattern.

7. Configure and back up

   Set the source, load the cabinet configuration, save to the receiving cards then back up settings from the web interface.

Frequently asked questions

Official documentation

• MCTRL660 PRO Independent Controller Specifications V1.4.2 (official PDF) — Datasheet
• NovaLCT — NovaStar downloads — Software

Related tutorials

• NovaStar MCTRL4K tutorial: 16 ports and 8.8 Mpx
• NovaStar VX16s tutorial: all-in-one controller
• NovaLCT tutorial: LED screen configuration
• NovaStar TB60 tutorial: 4-port 2.3 Mpx player

A controller to fit in your rack?

We validate the per-port load for your colour depth and deliver the MCTRL660 PRO with its configuration backed up.

• Request a quote
• Tutorials