COEX feature questions: multi-mode, adaptive frame rate, Image Booster, bit depth, calibration and 3D LUT.
Multi-mode refers to the capability of a receiving card to support multiple display modes. This is suitable for scenarios where the same batch of cabinets needs to be used in different requirements. Previously, to achieve this, multiple sets of rcfgx files had to be prepared in advance, switched different files which matched for different scenarios. Now, before producing the NCP, engineers collect the user’s scenarios in advance, involving different receiving card and chip driver IC parameters. Different modes are provided for switching based on different scenarios. Users can easily switch between display modes according to different usage scenarios, allowing the LED screen to display effects configured with different parameters.
Scenarios:
V1.0: A single fixed frame rate, typically 60Hz. The performance is consistent with NovaLCT, and there is only one parameter set. (Selectable fixed rates: 24Hz, 25Hz, 30Hz, 48Hz, 50Hz, 60Hz, 100Hz, up to 120Hz). Switching to other frame rates may cause screen flickering or blackout. This function is suitable for most common usage scenarios.
V2.0: Multiple fixed frame rates (e.g., 24Hz, 25Hz, 30Hz, 48Hz, 50Hz, 60Hz, 100Hz, 120Hz, up to 240Hz). Supports independent image booster files for the above fixed frame rates. It ensures normal display when switching between these specified frame rates, but other frame rates may result to abnormal display. This function is suitable for certain rental and broadcasting scenarios.
V3.0: Multiple frame rate bands (e.g., 23-60Hz, 61-120Hz, 121-240Hz). Guarantees normal display when switching to any frame rate within the supported frame rates range, with 0.01Hz increments. This function is suitable for virtual production.
NovaStar launched a high image quality solution fine pitch LED screens- Image boost engine. Including 22 Bit+, Precise Grayscale, and Color Management, it can restore the real world colors, making small-pitch LED screens to satisfy the requirements for high-end display from different dimensions.
22bit+ is a gray-scale coding technology developed by Novastar that combines the visual characteristics of the human eye. This technology combines the characteristics of the human eye with the new gray-scale coding design,which increases grayscale levels by 64 times.It effectively deal with the loss of low-brightness grayscale, makes it smoother, and bring better details to the image.
Precise grayscale technology implements level-by-level measurement on 16bits (65536 levels) grayscale of the driver IC.By utilizing the software algorithm, it can achieve level-by-level calibration, bring smoother transitions, improve quality on the low-grayscale display.
Color management can achieve effective control of the color of the display screen, using certain algorithm logic, and the combination of software and hardware to automatically and uniformly manage and adjust the color to ensure the display effect of the same color gamut of the image, showing the consistency of the color and the color. accuracy. Color management can accurately manage the intersection of the color gamut of the LED screen and the standard display color gamut to ensure that the color of the screen is consistent and solve the problem of color cast.
.cube is the format of 3D LUT file. COEX supports loading 17x17x17/33x33x33/65x65x65 3D LUT files.
At low grayscale levels during actual operation, due to excessively narrow pulse widths (1-pulse width), inconsistent channel switching speeds cause deviations in the rising/falling edges and ON-time of different driver ICs/LEDs compared to ideal conditions. This variation, combined with inherent differences in the luminescent characteristics of the epitaxial wafers, further amplifies discrepancies between chips and individual LEDs at low brightness levels.
Low grayscale correction technology specifically addresses uniformity variations caused by inherent chip characteristics by compensating the pulse width of individual subfields based on measured brightness differences. After pulse width compensation, the brightness of different ICs and LEDs tends to become consistent.
As the grayscale level increases, the influence of low grayscale correction coefficients on screen uniformity and brightness gradually diminishes due to subfield blending. For mid-to-high grayscale ranges, this effect becomes minimal.
Low grayscale calibration means performing a separate calibration specifically for the low grayscale area, and the coefficients for this area affect all grayscale. After low grayscale calibration, the screen still requires a brightness and chroma calibration (or full grayscale calibration) to correct the overall display performance for all grayscale levels.
The color replacement feature replaces one color in the image with another without affecting other colors. For example, when producing advertising videos, only one color of a product is typically filmed. To promote other colors in the same series, re-rendering the video would be time-consuming and labor-intensive. Using the color replacement feature, the specified color in the advertising video can be directly replaced with the desired color.
No, no rectangular limitation is a function of the COEX controller. When used with receiving cards supported by COEX, this function is available.
This feature is bound to the adaptive frame rate 3.0 feature. Therefore, receiving cards supporting adaptive frame rate 3.0, such as A10s Pro ,XA50 Pro and XA100 OPT, are required to use the shutter fit feature.
There are no requirements for the cabinet connection wiring. The low-latency function is enabled by default on A10s Pro.
To avoid wasting loading capacity, the topmost cabinet of each column of a single-port cabinet topology must align with the top of the canvas.
If the topmost cabinet of a column is not aligned with the top of the canvas, the loading capacity of the vacant area up to the top will be wasted.
Only A10s Pro supports adaptive thermal compensation.
The mainline version of A10s Pro ,XA50 Pro and XA100 OPT supports this function. Other COEX-compatible Armor series receiving cards require a firmware version of V4.9.0.0 or later.
A5s Plus, A8s, A8s-N, A8s Pro, A10s Plus-N with version V4.6.9.0 or above, A10s Pro.
Art-Net and SNMP belong to the UDP protocol; API belongs to the HTTP protocol.
Red, green, blue, and the three secondary colors have independent matrices. They do not affect each other and can be adjusted individually for these six components, ultimately making the performance of multiple batches of modules effects towards consistency.
The system automatically determines whether an alert is a alarm or a fault based on its content, and by default, distinguishes between alarm and fault according to system thresholds.
Users cannot set thresholds. If you need to modify threshold-related information, please contact an NovaStar FAE.
Only the save and read functions are related to the module flash. If the module has flash, calibration coefficients can be read from the module flash to the receiving card. With a calibration coefficient management license, calibration coefficients can be saved to the module flash.
Receiving Card Models: A10s Pro,XA50 Pro and XA100 OPT with V1.5.3.0 or later version.
Resettable Data: 1) All parameters within the NCP file. 2) Factory area parameters (cabinet parameters, gamma, thermal compensation, brightness, and module flash) are reset. Firmware programs are not restored.
This depends on the receiving card’s hardware capability. If module has module flash, read can performed from module flash. If there is no module flash, read can only be performed from the receiving card flash user area.
The “Add Starting Address” function in the Art-Net protocol allows a single Art-Net node (e.g., a lighting controller, pixel driver, etc.) to output multiple consecutive DMX Universe data to different physical ports or channel groups.
Its core function can be summarized as: flexibly and efficiently allocating and managing large-scale DMX512 data under limited network resources and node counts.
This license requires users to communicate their requirements with a NovaStar FAE and apply for it. After the application is approved, the license can be imported into VMP software for use.
After a power cycle, the screen temperature decreases. The system needs to determine whether the blank screen is caused by source turning black or a power cycle. The process of restoring the effect requires sensing the trend of screen temperature change to restore the correct compensation effect.
Yes，If users are equipPed with supported cameras,novastar will provide guidance and support for thermal compensation 3.1 calibration.
Module pixel fault detect, module flat cable, module temperature, and module voltage. These four functions require smart modules to be supported.
Using 3D and frame multiplication features will increase the output frame rate, which affects the device’s loading capacity.
This depends on which type of adaptive frame rate file is used, and does NCP or rcfgx is used. If there is an NCP file with adaptive frame rate 3.0, it can support any frame rate between 23.98Hz and 240 Hz, with 0.01 Hz increments. It can be used to transmit video sources with such frame rates.
Currently, all COEX devices support full grayscale calibration technology. But there are some compatibility for receiving card; only A10s Pro, XA50 Pro and XA100 OPT are supported.
multi mode refers to let a single NCP file has multiple sets of parameters, configurations, and calibration files for the cabinets which has the same specification. After being loaded via VMP software, modes can be changed in the user interface to match different parameter usage needs in various scenarios.
Scenarios:
To ensure good display quality and minimize shooting scan lines, virtual production projects have stricter requirements for both screens and control systems. For the control system, considerations include the loading capacity under high bit depth and high frame rate, screen heating causing color temperature shift requires thermal compensation; and functions like Genlock, phase offset, and shutter fit are needed to solve scan line issues. For screen parameters, such as currently NovaStar-adapted chips, the scan count should preferably be 16 scans or less, with 8 scans or fewer recommended. The screen refresh rate should be at least 3840Hz, with 7680Hz or higher recommended.
COEX devices support synchronization via NTP. The device time synchronization and schedule functions can prove it.
PTP synchronization is the timing method used in ST.2110 solutions. It requires MX2000/6000 Pro paired with ST.2110 cards and relies on the IP switcher in the control link to achieve synchronization.
For fixed-design COEX devices, under send-only mode, the front panel can be used to switch video sources, but this is not supported under all-in-one mode. For modular-design COEX devices, it is not supported in either working mode.
If the processor outputs 8bit to the receiving card (common default or when bandwidth/load is constrained), it effectively performs down-quantization before transmission. This results in loss of low-grayscale and transition details, particularly visible as banding (color/gray banding) or stepped gradients in dark areas, skies, skin tones, etc.
Even with a 10bit source, 8bit output limits the full benefit of the source, though the processor’s internal high-precision processing still provides some improvement over a native 8bit source.
MX40 Pro + A10s Pro or 5G receiving cards
10bit output to the receiving card significantly enhances low-grayscale performance and overall gradient smoothness. The receiving card and driver IC receive higher-precision raw data (1024 levels per channel vs. 256 for 8bit), which—combined with NCP-configured Image Booster (precise grayscale + 22bit+ enhancement)—delivers richer dark-area details, reduced contouring, lower color shift, and higher dynamic contrast.
Testing recommendations (perform side-by-side comparisons under identical content and brightness):
Use VMP software to force 8bit vs. 10bit output in the sending settings (some models allow direct bit-depth selection on output cards; otherwise, verify indirectly via load calculations).
Input 10bit HDR test patterns (e.g., grayscale ramps, dark gradients, skin-tone charts, SMPTE HDR patterns).
Observe from close range (1–2 meters) for banding/jumping in dark areas, smoothness in skies, and noise in black fields.
Record the screen with a camera (professional or smartphone in slow motion) and check footage for visible banding (more pronounced in 8bit).
With a colorimeter (e.g., CA-410), measure low-brightness grayscale uniformity and ΔE values—10bit typically shows lower ΔE and smoother transitions.
No, scan mode (e.g., 16, 32 scan number) and bit depth processing are independent. Any scan configuration can handle different bit depths (8/10/12bit).
Scan mode primarily affects visual refresh rate—the smaller the scan ratio (e.g., 8 scan number vs. 32 scan number), the higher the perceived refresh, reducing flicker and scan lines visible to the eye or in camera shots.
The notion that 10bit “requires” 16 scan number likely stems from older systems or specific high-end setups where higher bit depth + high refresh rate are combined for premium performance. In modern COEX systems, bit depth influences color/gradient quality, while scan mode affects flicker and camera compatibility—no direct linkage exists.
In term of image quality:
The difference is substantial, especially in low-brightness gradients and fine details.
8bit input → Receiving card gets 256 levels/channel → Even if the driver IC extends to 16bit internally, it’s merely upward filling/interpolation; lost original details cannot be recovered → Dark areas prone to banding, stepping, noise, and color shifts.
10bit input → Receiving card gets 1024 levels/channel → Provides richer raw grayscale data → Driver IC has a stronger foundation for 16bit extension → Combined with Image Booster’s precise grayscale correction and 22bit+, dark transitions become extremely smooth, details richer, and dynamic range superior.
In term of loading capacity:
For most receiving cards, 10bit output reduces sender net port loading by ~30–33% (due to ~1.33× data volume). For A10s Pro specifically, it maintains full single-card loading capacity for 10bit (no reduction), while sender-side loading decreases accordingly.
In summary, the jump from 8bit to 10bit primarily improves low-brightness gradient quality and overall image finesse—critical for fine-pitch screens and directly supporting the “10bit or higher” requirement.
22bit+ (also called 22bit low-gray enhancement) is a core feature of NovaStar’s Image Booster function. It is implemented primarily on supported receiving cards (e.g., A10s Pro, A8s, A8s-N, and above)—not exclusively in the processor or driver IC.
The algorithm dynamically boosts low-grayscale (especially 0 to low-brightness regions) from standard 16bit to an effective 22bit+ level (up to 64× dynamic contrast improvement), eliminating common LED issues like grayscale loss, contouring, and dark-area blocking at low brightness.
Workflow: Processor outputs highbit data → Receiving card applies NCP file’s precise grayscale correction + 22bit+ algorithm → Delivers ultra-high precision control to the driver IC in low-gray areas.
This significantly improves dark-field performance, delivering rich layering without breaks—even at very low brightness—making it ideal for indoor fine-pitch, xR/VP, and broadcast-grade applications.
For brightness, gamma, and RGB brightness components, VMP supports adjustment at the cabinet level. However, it is important to note that adjusting RGB brightness components requires receiving card models A10s Pro, CA50E, or XA50 Pro, with firmware version V1.5.3.0 or above.
For color temperature, which is a function of the image booster, it can currently only be adjusted based on the entire canvas. The V1.6.0 version of VMP will introduce image booster adjustment functions at the port level.
← Back to Technical Support · Still need help? Email [email protected].