NovaStar MX30: low latency, panels per port, and Genlock

Before the rehearsal: record signal, receiving card, and path

Save a copy of the project and screenshots of the initial state. Record MX30 and firmware, VMP, exact receiving card model, panel configuration file, and driver IC. Draw each chain with its panels, port, dimensions, and coordinates in the software. Check the refresh rate and bit depth you are using on the unit.

Separate three observations: a cropped image on the LED, delay in displaying an action, and visible bands when filming the screen. Record where each appears; resolving one does not demonstrate that the others are resolved. For detection failures, first consult USB and network connections on NovaStar (Spanish).

MX30 with A8s Pro: capacity and chains for low latency

The MX30 V1.5.0 manual, §6.5.3, p. 26 (PDF 27) requires vertical chains with the same Y coordinate for low latency; a free layout reduces capacity. Check both the physical path and its position in VMP. For a different topology, VMP V1.5.0, §5.1, p. 18 (PDF 22) refers the specific calculation to NovaStar support.

The MX30 V1.5.0 datasheet, pp. 8 and 13–14 (PDF 9/14/15) distinguishes 10-bit operation at 60 Hz: other Armor cards, 329,861 pixels; A8s Pro/A10s Pro, 494,791 on p. 8 and 494,792 on p. 14. We preserve the discrepancy and use the lower value for comparison. It also requires a load width of at least 128 pixels to reach the published maximum. This is a reference before accounting for topology restrictions.

Our calculation: a 384×216 panel contains 82,944 pixels. The table only compares sums. To validate low latency, coordinates, firmware, total capacity, and effective load per port are still needed; review the plan with support before the rehearsal.

The A8s Pro V1.3.1 datasheet, p. 3 (PDF 4) makes reduction to one frame in the receiving card conditional on using modules with a driver IC incorporating RAM. Request the IC model and configuration from the panel supplier; the A8s Pro name does not verify that condition.

Suggested test: identify the missing area with a pattern numbering all panels. Compare a VMP screenshot, physical map, and LED photo; record the first panel that does not show what is expected. Keep signal, bit depth, and mode unchanged while reviewing one chain. A port change needs an updated plan and a new record; do not declare it a solution based on one correct image.

Tip: when sending the case to support, attach load per port and coordinates as well as the number of panels.

Low Latency and Genlock: record which function you need

We do not prescribe camera settings with incomplete models and versions.

In the MX30 V1.5.0 manual, §6.5.3, p. 26 (PDF 27), Low Latency is set in Advanced Functions > Output Settings and does not allow Genlock as the synchronization source. With low latency, the controller specifies less than 1 ms in Send-Only and one frame in All-In-One. These values apply to the controller, not the entire camera-to-screen path.

In VMP V1.5.0, §§5.1 and 9.2.2, pp. 17–18 and 57–58 (PDF 21/22/61/62), mode and Low Latency are reviewed under Layout > Edit; synchronization under Screen Settings > Output. Phase adjustment is also unavailable with Low Latency active. Genlock applies to the selected controller: check which one you are viewing.

For Shutter Fit, review the following section: it distinguishes MX30 from MX40 Pro and documents the receiving card and reference the system requires. Preserve models and versions before selecting the procedure.

Suggested test: first save mode, Low Latency, synchronization source, and observed image. If production requires an external reference, prepare a comparison with low latency disabled, keeping the rest of the setup unchanged. Record Genlock availability, indicated lock state, LED image, and camera recording. The change helps check the restriction; it does not guarantee eliminating bands.

If the goal is to reduce IMAG delay, we suggest recording the same action and its screen image in one test shot. Count the difference using a consistent method and record the recording frame rate; repeat with the initial state. Do not turn a unit’s published latency into a measured system result.

If the option is still missing, keep screenshots and versions for support. If it appears but does not indicate lock, also record the generator, signal, and reference path to check them with their manuals. No specific camera, generator, or converter was validated here.

Test worksheet and handover to the next operator

Use the MX30 worksheet to save the initial state, changes, screenshots, and result to be completed. Mark each entry as documentation, calculation, or a setup test. When finished, restore the agreed state and leave the copy the next operator should load.

Connect the record with video and screens, image and speech out of sync and video processing. The tests in this guide are proposed; they are not completed tests or GLMedia’s own cases.

Shutter Fit: check controller, receiving card, and reference

Having a GENLOCK input does not demonstrate that the controller has Shutter Fit. The MX30 V1.5.1, rear panel p. 8 (PDF 9) documents that input. Also identify firmware, VMP version, and receiving card; the physical connection is only part of the check.

The VMP V1.5.0 manual, §9.2.4, p. 59 (PDF 63) includes MX40 Pro with A10s Pro for Shutter Fit; MX30 and A5s Plus do not appear among the enabled models. Review the full list if using other equipment and check your version’s documentation.

The manuals MX30 V1.5.1, §6.5.3, p. 24 (PDF 25) and MX40 Pro V1.5.1, §6.5.4, pp. 27–28 (PDF 28/29) retain the incompatibility between active Low Latency and Genlock. These are document revisions, not verified versions of your equipment. If the rehearsal requires a reference, record that state before changing it.

The xR V1.0.1 manual, §§2.4.1–2.4.2, pp. 13–17 (PDF 17–21) requires a common Genlock for controller and camera. It instructs you to set Shutter Fit in Screen Settings > Output using the actual shutter setting (Angle or Speed). After changing it or Frame Multiplication, it requires phase readjustment. Its examples are not universal values.

Suggested test: save the initial state and first check each condition in the table. With the compatible system prepared, record a reference sample. Change one parameter at a time, save a screenshot of the value, and repeat the shot with the same framing and content. Compare the recorded files and note whether bands disappear, change, or return after restarting. There is no measured result for this procedure yet.

To identify FX3/FX30 controls and firmware, follow the camera guide (Spanish).

A5s Plus to A10s Pro: what to review before changing the receiving card

Identify manufacturer, IC, and scan before selecting the panel configuration.

The A10s Pro V1.3.0 datasheet, Features > Shutter Fit, p. 3 (PDF 4) describes driver IC adjustments based on the shutter to address lines and grayscale irregularities. That function does not prove compatibility with the existing cabinet. Request a response from the panel manufacturer for the exact module, IC, HUB, receiving card, and processor.

Compare the physical drawings: A5s Plus V1.3.0, Dimensions, p. 7 (PDF 8) shows 70×45 mm; A10s Pro V1.3.0, Dimensions, p. 7 (PDF 8) shows 80×45 mm. Request confirmation of space, mounting, power, and HUB pin assignment. A photo of similar connectors does not establish interchangeability; confirm the cabinet’s wiring and pin assignment before connecting it.

The xR V1.0.1 manual, §§2.1 and 2.4.2, pp. 4 and 16 (PDF 8/20) requires Shutter Fit to work with Frame Rate Adaptive and NovaStar to prepare those parameters in the cabinet’s .ncp file. Coordinate that preparation with the panel manufacturer; do not load another module’s file to try to enable the function.

Suggested test after confirming compatibility: preserve the project and original files; agree with the supplier on how to restore the initial state. First test one identified unit with the camera and signal planned for the event. Record normal image and grayscale, bands, uniformity, settings, and indicated temperature. Compare with the original unit under the same conditions. Physical replacement and the result remain pending.

Tip: request scan and refresh rate in separate fields on the module datasheet. Complete the compatibility and test worksheet and attach module identification and samples; saying the screen looks good to the naked eye is not enough.

Connect the case with video and screens and the video processing service. In a production with LED and cameras, the result must be checked using the equipment and settings that will work at the event.