Video · Practical guide
NovaStar H2: native input and LED screens repeating an image
When an LED pixel matrix changes or more surfaces are added, record the incoming signal and the region each screen should display. This guide brings together two H2 inquiries and suggests checks for the technical rehearsal.
A wide screen: identify the card before preparing the signal
The mention of dual HDMI 2.1 does not by itself identify the installed card.
The H2 V1.17.0 document, pp. 13 and 20 distinguishes these cards. The figures are published formats, not verified acceptance of any intermediate resolution. The H_1xHDMI2.1+1xDP1.4 uses one connector at a time, selected in the web interface; its initial selection is DP1.4. The recommendation for certified HDMI2.1/DP1.4 cables applies to that card.
We suggest requesting a legible photo of the cards and slots, along with the installed version, from the supplier. Compare the label with the datasheet; counting connectors or saying the H2 is 4K leaves a decisive part of the setup unresolved. Complete the width, height, refresh rate, and color format of the signal you actually want to send.
| Exact card | Published format at 60 Hz | What remains to be checked |
|---|---|---|
| H_1xHDMI2.1+1xDP1.4 | Custom: 8192×2304; one active connector | Timing, bit depth, and actual PC output |
| H_2xHDMI2.0 | Per connector: 4096×2160; custom: 8192×1152. Two simultaneous inputs | Identification and full format; 8192 pixels wide does not prove support for any height |
5824×1664: prepare a native input test
The calculation of 9,691,136 active pixels per frame describes the request; input timing acceptance and port distribution for that setup still need to be checked.
The H Series V1.15.0 manual, §6.4.1.1, pp. 77–78 lets you view the card, version, and received signal in Device; Capacity depends on the connector. For HDMI2.1/DP1.4, it includes 8K. In EDID, pp. 53–54, select Input and the connector, set width, height, and refresh rate, then apply. Export the existing EDID before the rehearsal.
Suggested test: with the card identified and the format agreed, send a pattern with borders, numbers, and fine text from the event PC. Record the signal reported by the PC and the one received by the H2; compare them with the request. If the source rejects the format, save the message and return to the initial setting before changing another element. Do not repeat advanced timing adjustments without GPU and card data.
If the setup requires a scaled signal, agree on the visible area with design and production, and rehearse the crops. If splitting the source across two outputs is proposed, prepare a separate plan: each GPU’s output, region sent, synchronization, and join. Connect the request with presentations for panoramic LED screens.
Two screens repeat the image: check the coordinates
Dimensions and versions are missing to reproduce that result on another screen.
The H Series V1.15.0 manual, §3.1, pp. 6–9 shows a virtual 4K connector for H_16xRJ45+2xfiber and requires configuring the LED in NovaLCT. Select the sending card, receiving card, and port there according to the cabling; do not expect an independent layer for each RJ45 in Configuration.
The NovaLCT synchronous V5.4.4.5 manual, §5.2.3, pp. 24–28 distinguishes areas of one screen from separate screens, allows reading the configuration with Read from HW, and adjusting Coordinate. Enable Mapping identifies the cabinet and port. This is a reference documentation edition; compare it with the interface of the installed version.
An error to avoid when sending parameters to receiving cards: check Reset the Starting Coordinate of Receiving Card. The cited NovaLCT manual (p. 24) warns that it resets all origins to (0,0), making the upper-left corner repeat. Do not check that option to try to correct duplication.
We suggest reading and preserving the current mapping with the LED lead before writing changes. Draw the region each surface should display and compare it with the cabling. During the rehearsal, use different letters on each region and compare one screen at a time. If both display the same letter, record coordinates, layers, and crops before moving connections.
Coordinate example for checking two regions
Teaching example: two 960×540 surfaces share a 1920×540 canvas. Region A starts at (0,0); B at (960,0). A occupies X from 0 to 959 and B from 960 to 1919. These are adjacent, non-overlapping regions. This is a proposal for understanding the distribution; it does not assign actual ports or validate your card’s load.
Prepare the pattern with large A and B letters and corner marks. Compare the production diagram, H2 composition, and data read from NovaLCT. Do not transfer these numbers to a screen with a different pixel matrix. A useful result should state which surface changed and with which setting, not just that an image appeared.
| Example surface | Origin X,Y | Intended area | Pending observation |
|---|---|---|---|
| A | 0,0 | 960×540; X 0–959 | Does it show A and all four corners? |
| B | 960,0 | 960×540; X 960–1919 | Does it show B without repeating A? |
H2 rehearsal worksheet and documentation
Use the H2 input and LED region worksheet. Leave results blank until the rehearsal is performed. Record one change at a time, a screenshot of the setting, and an image of each surface; keep the initial configuration so you can restore it.
For a conference, corporate presentation, or stage with multiple screens, bring the region plan together with the content request. This help connects with video and screens, black screen diagnosis and GLMedia’s video processing service. The cited procedures apply to the H2 and its identified cards; document differences in the installed equipment.
H2: a 16:9 presentation without distorting the image
Documented control: in Programming, select the layer; W/H defines its size and X/Y its position from the upper-left corner. For an input crop, open Input Signal → source menu → Input Crop; identify the crop by name, origin, and dimensions. That crop selects content before scaling. Reference: NovaStar H Series V1.15.0, §4.1 p. 14 and §4.10 pp. 41–42.
The manual distinguishes Live and Pre-Edit: Live displays changes in real time; unchecking it prepares the edit. Figure 4-10 shows the Take button for sending it to the screen. Compare that step with the installed interface before using it: p. 18, PDF 22.
Suggested test for a conference presentation: first preserve the dimensions and screenshots of the current setting. With a full 1920×1080 source and an 896×512 canvas, we calculate an 896×504 layer centered at (0,4). Width and height are multiplied by 7/15; four pixels remain above and below. These are teaching numbers, without image or output capacity approval.
For that example, we suggest entering both calculated dimensions and displaying a pattern with a circle, small text, and border marks. Compare with the previous framing using the same content. If letters or corners disappear, record what is missing and which crops were active; enlarging the layer by trial and error may hide that information.
Common error: accepting a filled image even though the circle is oval. If production requests filling the entire LED, agree on a crop or adapted composition before receiving the final presentation. The panoramic presentation guide helps decide that framing; the VX600 layers and sidebars case helps review another cause of an image outside the intended area.
Record the comparison in the H2/VX600 scaling worksheet, with the installed version and results pending until testing. To prepare the event’s signal path, consult GLMedia video processing.
| Calculated example | Size | Origin | What to check in the rehearsal |
|---|---|---|---|
| Full source | 1920×1080 | No crop planned | Four corners and circle |
| LED canvas | 896×512 | 0,0 | Actual pixel matrix before applying the example |
| Proportional layer | 896×504 | 0,4 | 4-pixel bands above and below; round circle |
Frequently asked questions
Does the H2 accept a 5824×1664 screen through a single input?
The 5824×1664 pixel matrix is not enough to decide: the input card, full signal format, and sending PC still need identification. Request the card label and compare width, height, and refresh rate with its datasheet. During the rehearsal, record what the PC outputs and what the H2 receives, and display a pattern with borders and fine text. If the source rejects the format, save the message and return to the initial setting before changing another variable.
Does the HDMI2.1 and DP1.4 card allow both connectors to be used together?
The documented H_1xHDMI2.1+1xDP1.4 uses one at a time. Confirm the label before applying that limit to another card.
Why do RJ45 ports 1 and 2 on the H2 show the same image?
Review the surface coordinates in NovaLCT and the regions in the H2 composition. Before writing changes, read and preserve the current mapping with the LED lead. For the rehearsal, use a pattern with different letters in each region and record which appears on each screen. If the letter repeats, record coordinates, layers, and crops before moving cables.
Can I load the example coordinates directly?
Use them to understand the distribution. First read the actual configuration, record each surface’s pixel matrix, and prepare the rehearsal with its lead.
What should I check if I connect HDMI to the combined card and get no signal?
On the H_1xHDMI2.1+1xDP1.4, check the selected connector; the documented initial selection is DP1.4. Then record the received signal before changing more settings.
Does each RJ45 on the H_16xRJ45+2xfiber appear as an independent output on the H2 web interface?
The H_16xRJ45+2xfiber web configuration shows a virtual 4K connector. Cabinet and port distribution is configured in NovaLCT. Compare that distribution with the cabling and region plan; do not expect an independent layer for each RJ45 in Configuration.
How do I check the H2 input after applying an EDID?
Compare the signal output by the PC with the one reported by the H2 and the requested format. During the rehearsal, use the event’s actual source and a pattern with borders, numbers, and fine text; record rejections, crops, and legibility. If the source rejects the format, save the message and restore the initial setting before continuing. Applying the EDID is a configuration step; input approval remains pending until that check is completed.
Should firmware be updated before investigating this problem?
First record versions, configuration, and symptom. An update requires compatibility documentation and a recovery plan; this guide does not prescribe updating the unit.
What size should I test for a 16:9 source on an 896×512 LED with H2?
For the example’s full 1920×1080 source, the calculated layer is 896×504, positioned at (0,4) within the 896×512 LED. Four pixels remain above and below. This is a calculation for testing: preserve the current setting and compare a circle, text, and all four corners with the actual source. If any border is missing, review active crops before enlarging the layer by trial and error.
Does resizing the H2 layer replace an input crop?
These are different settings: W/H defines layer size, and Input Crop selects which part of the source is used before scaling. If borders or text are missing, record layer dimensions and crop origin and size. Compare them with the intended framing before changing both at once.