Current location:
Home
> News > Product News > LCD video wall
Release date: 2026-10-31
Clicks:0
Equipment connection decision-making reference for security integrators pre-sales, project managers and Party A informatization leaders
The most familiar action of the engineer is to plug a monitor directly into the HDMI port of the NVR, and the picture comes out. But as soon as the screen is measured, I am confused: NVR has only one or two HDMI ports. How can I divide the 16 splicing screens? The essence of this problem is The number of NVR output ports is not equal to the number of splicing screens.There must be a "translation" in the middle ". This layer of translation can be an HDMI distributor, a video integration platform, a splicing controller, or a distributed node. The complexity is three orders of magnitude lower, and the cost and debugging cycle are several times lower.
This article explains the four architectures from simple to complex. Each one gives topology, flow mode, equipment selection, configuration steps, obstacle removal table and cost level. Finally, it gives a horizontal comparison table and a selection Checklist that can be directly sent to customers to fill in. After reading, you can judge: which scheme should be used for the project at hand, which equipment should be equipped, how to get the cable, and what range the budget probably falls in.
NVR can do three things: the built-in decoding chip directly outputs the picture through HDMI port, but the number of ways is limited; Support the separation of main and sub-stream, and save bandwidth by walking sub-stream on the wall; HDMI output port supports 4, 9 and 16 divisions. It cannot do three things: generally there are only one or two HDMI ports, which cannot drive large-scale splicing walls; Without splicing processing capability, cross-screen roaming and window opening cannot be done. Only recognize your own IPC or ONVIF, and the compatibility of third-party brands varies. Put this capability table at the beginning of the plan, and the customer will understand why NVR alone can't support a wall.
The key parameter is the decoding capability, but look at it separately according to the three constraints. The first is the number of 1080P simultaneous decoding channels, 16 NVR channels are about 4 to 8, 32 channels are about 8 to 16, 64 channels are about 16 to 32, and 128 channels are about 32 to 64 storage servers. The second is the number of 4K simultaneous decoding channels, which is converted according to the 1/4 of 1080P. The specification usually reads "16 channels 1080P or 4 channels 4K". The third is the number of road rounds on the wall, time-sharing multiplexing, which can be much larger than the number of simultaneous decoding roads. Here is the most common pit:The number of channels 64 is not equal to 64 pictures that can be solved at the same time.At the same time, decoding is not equal to round the wall. The number of output ports and the number of decoding paths are two constraints, and all three must be stuck.
Scheme selection can follow the decision tree according to the project scale: scheme a within 9 screens and within 32 roads, NVR is directly connected and grouped by distributor or multiple NVR; 9 to 36 screens, 32 to 200 paths B,NVR plus video integrated platform or decoder; 36 to 100 screens, 200 to 500 paths C,NVR plus splicing controller plus decoding cluster; plan D, distributed IP architecture, above 100 screens and above 500 roads.
Before entering the specific plan, string through the derivation chain of "from screen count to equipment number. Taking 36 screens and 9 divisions of a single screen as an example, the total number of paths on the wall is 36 times 9 equal to 324 paths, and the decoding capability is not less than 389 paths according to 1.2 times of margin. The number of decoder outputs is equal to the number of screens, that is, 36; The number of decoders takes the greater of the two results of "the number of decoding channels divided by the number of single decoding channels" and "the number of output ports divided by the number of output ports. If the splicing controller, the number of input ports of the controller is not less than the total number of output ports of the decoder, and the number of output ports is equal to 36. This derivation chain serves as the common basis for equipment selection in the four subsequent schemes.How to calculate the number of splicing screensIs the starting point, the number of equipment is the end point, the middle is connected by these two constraints.
Scheme A has two sub-schemes, which must be said separately. If mixed together, it is easy to contradict each other. A- 1 is the distributor mode: the HDMI port of NVR is connected to a four-point or eight-point HDMI distributor, and the output of the distributor is connected to multiple screens,All screens display the same picture. A- 2 is a multi-NVR grouping mode: NVR-1 screen group 1 and NVR-2 screen group 2. The content of each screen group is independent, but it cannot be scheduled uniformly.
The applicable scenes should be clearly written: the A- 1 is suitable for projects with less than 9 screens, all screens looking at the same group of pictures or NVR built-in segmentation and extremely tight budget; It is A- 2 suitable for scenes where each area looks at each area and does not need unified scheduling between screen groups. If the customer requires that "each screen displays different contents independently", only the A- 2 can be taken, and the distributor cannot do it. This must be made clear in the plan, otherwise it is easy to wrangle during acceptance.
In terms of equipment selection, NVR selects models with HDMI 2.0 output and supports 4K. HDMI distributor selects one-to-four active mode and requires power supply. HDMI optical transceiver is used for distances over 15 meters. In terms of cables, HDMI copper cables are used within 7 meters, active optical HDMI is used for 7 to 15 meters, and optical HDMI or HDBaseT is used for more than 15 meters. However, it should be noted that special transmitters and receivers are required for HDBaseT, instead of direct plug-in network cables. The configuration steps are very simple: the HDMI port of NVR is connected to the input of the distributor, the output of the distributor is connected to each screen, the HDMI output resolution is set in the NVR menu, the screen is split and the channel is selected, the screen end is set to HDMI automatic input, and finally all screens are verified to be consistent, free of black screen and flicker.
Limitations to inform customers in advance: A- 1 all screens are the same, cannot be spliced across screens, and cannot be roaming to open windows; Under the limit of the number of NVR decoding channels, 9 channels are divided but only 4 channels are solved, and the picture will circle or black screen. A- 2 multiple NVR's each in charge, they cannot be scheduled in a unified way, and there is no scene plan and alarm linkage pop-up window. The cost level is in the thousands of yuan (excluding screen and hard disk, subject to actual inquiry), which is suitable for small monitoring rooms with extremely tight budgets.
This is the most used structure in domestic projects. The core logic is division of labor: NVR is responsible for recording and playback, decoder is responsible for throwing the picture onto the screen, the two are decoupled through IP network, and decoder pulls sub-code stream from NVR through SDK, ONVIF or RTSP. On the network link, NVR goes through CAT6 or optical fiber to the core switch, decoder goes through optical fiber to the core switch, 2 times 10G LACP takes stream bandwidth concentration, decoder goes through HDMI 2.0 or optical fiber HDMI to the splicing screen, and the control computer is connected to the decoder management port and goes through independent management VLAN.Network Wiring Scheme of Monitoring Splice ScreenFor the full details, please refer to another dedicated article on the site; here we will only discuss the connection logic.
The three ways to take the stream should be compared with the choice. RTSP is universal and cross-brand, but RTSP of some NVR is unstable. Samsung is recommended. SDK docking is the built-in NVR brand SDK of the decoder, which is stable and supports playback on the wall, but binds the brand and recommends five stars. ONVIF is a standard protocol and is open, but the sub-code stream negotiation depends on the firmware version of the device and needs actual measurement. Two to Samsung are recommended. The actual combat suggestion is: use SDK for the same brand, mix and match RTSP and test in advance, ONVIF is only the bottom line.
The selection of video integrated platform requires two constraints, not just one. The number of decoding paths is calculated by multiplying the total number of paths on the wall by the 1.2 margin. The number of output ports is equal to the number of splicing screen blocks, and the larger of the two is equipped with equipment. In HDMI version, 4K screen can be 2.0 and 1080P can be 1.4. The splicing capability should support the maximum splicing scale of the project. At least 16 scene plans, supporting one-key switching; If audio is required on the wall, confirm decoder support.
The configuration steps are divided into seven steps: the network is opened up, so that the decoder and NVR can be reached on the same network segment or route; Add equipment, add NVR IP, port and account password in the decoder management interface; Channel binding, select NVR channel and assign sub-stream or main stream; Output configuration, set which screen or screen group each HDMI port corresponds to; Layout editing, dragging channels to screen positions and setting the number of divisions; the scene is saved and stored in daily mode, emergency mode, etc. Finally, the test wheel patrol, alarm linkage pop-up window and playback on the wall. The first five steps are suitable to be structured, and the last two steps are used as verification instructions.
The troubleshooting table is the most practical part of this section. There is a black screen on the wall but there is a channel number. Most of the sub-code stream negotiation fails, forcing the sub-code stream parameters to be specified. The picture stuck is that the decoder takes the stream bandwidth to run full, reduces the number of splits or rotor the main code stream. The slow switching scene is that the decoder CPU is high, reducing the number of active channels at the same time; Some channels have no pictures. Check whether NVR channel serial number is offset. Time on-screen is not synchronized, have the NVR and the decoder point to the same NTP server.How to Choose DecoderFor more comparison, you can see the article on decoder selection in the station. In terms of cost magnitude, 200 channels of projects, 36 screens, video integrated platform plus switches and cables are in the order of tens of thousands of dollars, excluding screens and NVR. When quoting, please indicate whether boards, installation and taxes are included.
When do you need a splicing controller? You need to cross-screen roaming and open windows, and one screen spans three screens; you need to mix multiple signal sources, and IPC screen, computer desktop, GIS map, and video conference are on the wall at the same time; when the number of screens reaches 36 or more, the output port of a single decoder is not enough; you need to cooperate with the agent, and the keyboard and mouse control the content of the large screen. If any two of these four conditions are met, option C should be considered.
Architecturally, IPC enters the NVR cluster, NVR cluster to the core switch, the core switch sends the stream to the decoding server cluster, the decoding server HDMI output enters the input board pool of the splicing controller, the controller output board is output to the LCD splicing screen array screen by screen, and the control server and client are managed through the control switch. The splicing controller is used for input convergence, output mapping, picture processing, scene management and signal switching. Each output port is bound with a physical screen. Scaling, superposition, cross-screen, roaming and picture-in-picture are all completed at this layer. Dozens of scenes can be saved. The switching from input source to any screen position is in seconds.
In terms of connection details, the decoder to the controller is that each decoder HDMI output is connected to the controller input board, the total number of decoder output ports does not exceed the controller input slot, HDMI copper cable within 7 meters, long-distance optical HDMI; The controller to the screen recommends that one screen and one mouth be independently controllable, or two screens can share one output port for division and splitting, but the independent controllability will decrease; the control link is from the controller network port to the control switch and then to the control client. The protocol uses RS232, RS485 or TCP, which is mostly proprietary to the manufacturer.
Bandwidth and equipment ratio to complement the output port derivation, can not only count the number of decoding. Or take 36 screens and 9 divisions of a single screen as an example. The total number of roads on the wall is 324, and not less than 389 roads need to be decoded according to 1.2 times of margin. A single decoding server has 64 channels and needs 7 sets. The output port requires 36 ports. If a single decoder only needs 5 ports, whichever is larger, it is equipped with 7 sets. The input board of the splicing controller is matched according to the total number of outputs of 7 decoders, for example, 7 times 8 equals 56 in, and the output board has 36 ports. It should be noted that the controller input board has a single-port bandwidth limit and EDID negotiation problem, which is not a simple sum, but must be calculated according to the manufacturer's specifications.
The configuration steps are: each decoder in the decoding cluster adds NVR and allocates channels; Initialize splicing controller, identify input and output boards and do EDID management; Input source binding, name each HDMI input port; Output mapping, defining which screen the output port corresponds to; Layout design, drag the input source to the output area and set the zoom position; Scene saving, naming daily monitoring, emergency command, video conference; Linkage settings, the alarm triggers the automatic pop-up window of the controller API. 500-way project, 49 screens, decoding server cluster plus splicing controller in the order of hundreds of thousands of yuan, excluding screens and NVR, indicate whether domestic or imported, including board cards.
The core idea of Scheme D is to abandon the mode of "centralized decoding and lengthening HDMI cable" and change it to one node box per screen, all of which go through the network. Topologically, IPC, NVR or streaming media server to the core switch, the core switch to the distributed decoding node behind each screen, the node uses a 1-meter short jumper to connect the screen, and the control server makes a software-defined layout through an independent control network.
NVR's role in it needs to be supplemented with an alternative path: the conventional practice is that NVR does storage and streaming media forwarding, and RTSP or RTMP forwarding is turned on for nodes to pull streams. Some platforms support GB/T 28181, and nodes directly register for streaming. However, in super-large projects, distributed nodes can directly fetch streams from IPC or independent streaming media servers, bypassing the NVR forwarding bottleneck. NVR is only responsible for storage, which many schemes will be missed. On the connection medium, NVR goes through optical fiber to the switch, 10G streaming media forwarding throughput, CAT6A or optical fiber from the switch to the node box, 1G port per node, 1 m HDMI short jumper from the node box to the screen, and the control network is independent gigabit.
The advantages are unlimited expansion and addition of nodes, no central failure point, screen positions can cross floors and buildings, and seat KVM is naturally supported. The disadvantage is that the network requirements are extremely high, the need for non-blocking 10 trillion, the node box heat dissipation and power supply are scattered, the cost is the highest, and the debugging is complicated. The applicable scenario is that the public security command center has more than 100 screens and multiple signal sources, the monitoring room and computer room in the cross-building park are not on the first floor, and the mobile phone flat panel is required to wirelessly project the screen to the splicing wall.
According to the maximum number of screens in a single set, scheme a is 9 pieces, scheme B is 64 pieces stackable in a single set, scheme c is more than 144 pieces, and scheme d is infinite. The number of roads on the wall is within 16, 512 and 2000 respectively, with no upper limit. Cross-screen roaming is only supported by schemes C and D, multi-signal mixing scheme A is not supported, scheme B is limited, and schemes C and D are supported. The construction difficulty is from low to high, the commissioning period is from half a day to two to four weeks, and the equipment cost is from several thousand yuan to hundreds of thousands of yuan to more than 300000 yuan. The recommended project scale is less than 50 roads, 50 to 300 roads, 300 to 1000 roads and more than 1000 roads respectively. This form can be directly pasted into the tender document or used as a decision-making basis when communicating with customers.
This checklist can be directly converted into an Excel file and sent to the client for completion. The number of splicing screens in the first item is compared with the plan selected in the table in section 6. The second item is the number of IPC channels that need to be added to the wall at the same time, and the decoding capability is calculated by multiplying the 1.2 margin. The third single-screen plan is divided into 4, 9 or 16, which determines the number of output ports and decoding channels. Whether the fourth item needs to roam across screens and open windows; Whether the fifth item needs computers, GIS and video conference are mixed, the unified recommendation scheme B is the same as the brand SDK, and RTSP is not used to test in advance. The maximum distance between the seventh decoder and the screen determines whether HDMI copper cable, AOC or optical HDMI; How much is the budget range of item 8, which is stuck at the upper limit of the scheme; Whether there is equal guarantee or trust creation requirements in item 9 affects the compatibility of domestic decoding platforms and domestic switches; Whether item 10 crosses floors and buildings, it is the priority to evaluate scheme d.
A derivation example is attached at the back of the list: 36 screens, 9 divisions, 324 total roads on the wall, not less than 389 roads to be decoded by 1.2, 36 output ports, the number of decoders is the larger of the two requirements, the input port of the splicing controller is not less than the total number of decoder output ports, and the output port is equal to 36, in the number of cables, the HDMI line from the decoder to the controller is equal to the total number of output ports of the decoder, and the HDMI line from the controller to the screen is equal to 36. After filling out the list, it will be clear to match some equipment and buy some wires.
In the factory park, there are 120 channels and 16 55-inch screens, plan B, four NVR plus 64 channels of decoded video integrated platform, NVR to core switch to integrated platform and then to HDMI optical fiber to screen, docking with brand SDK, playing back one-click call on the wall, and stepping on the pit is that the integrated platform defaults to take the bandwidth of the main code stream and explodes, and it is normal after changing the sub-code stream.
区级指挥中心 800 路、72 块屏，走方案 C，NVR 集群加 12 台解码服务器加 144 入 72 出的拼接控制器，解码服务器 HDMI 进控制器输入再输出到屏，GIS 地图跨 12 块屏、告警弹窗自动置顶，踩过的坑是 HDMI 线 25 米信号衰减，换光纤 HDMI 解决。
连锁门店集控总部看 200 家店、9 块屏，走方案 B，门店 NVR 经专网到总部解码器再到 9 块屏，专网 VPN 回传子码流，每家店 1 路轮巡、25 店每屏乘 9 屏覆盖 225 店，踩过的坑是专网带宽不够，每家店限 512Kbps 子码流。
园区监控室改造 200 路、24 块 55 寸屏，走方案 B，六台 NVR 加 48 路解码、24 输出的视频综合平台。屏体侧选用了 LCD splicing screen China source manufacturers群茂显示的 55 寸 3.5mm 拼缝拼接单元，4 乘 6 阵列，配伸缩支架前维护。这个项目值得说的是屏体侧协同：屏后接线盒位置、HDMI 线长、垂直走线空间在方案阶段就和厂家对齐，避免了屏装好后线到不了的尴尬；出厂统一色彩校准让拼接色差很小，低功耗面板降低了配电压力，智能运维模块能远程监测屏体状态。踩过的坑是解码器默认输出 1080P、屏体支持 4K，EDID 协商阶段没对齐，厂家提供 EDID 参数表后解决。这种屏体侧配合，走品牌代理往往要绕几道，直接对接源头厂家反而快。
NVR 能不能直接接拼接屏？能，但只适合 9 块屏以内、同画面的小项目，大项目必须加解码设备。
NVR 和解码器怎么对接？同品牌 SDK 最稳，混搭用 RTSP 并提前测试，ONVIF 视固件版本而定。
解码器输出口不够屏数怎么办？加拼接控制器，或换更多输出口的解码器，先把输出口和解码路数两条约束算清。
NVR 取流和解码器取流有什么区别？NVR 是“存加解”，解码器是“纯解加显”，分工不同，不能互相替代。
子码流上墙模糊吗？9 分割下每块占屏面积小，720P 子码流够用；单画面放大必须主码流。
海康 NVR 能接大华解码器吗？可以走 RTSP，但回放上墙、PTZ 等功能可能不全，重要项目提前实测。
拼接屏后面 HDMI 线经常松怎么办？用带锁 HDMI 线加理线支架固定，屏后留检修空间，施工前出屏后走线图。
NVR 通道数 64 路，能同时上墙 64 路吗？不能，要看同时解码路数，4K 还要按四分之一折算。
同时解码和轮巡上墙有什么区别？同时解码是并发压力，轮巡是分时复用，轮巡路数可以远大于同时解码路数。
解码器到屏超过 15 米怎么办？AOC 有源光纤 HDMI，超过 50 米用 HDMI 光端机，不建议用信号放大器。
分布式架构一定要万兆网络吗？节点多、码流高时需要无阻塞万兆，小规模可千兆起步但要留余量。
视频专网能不能和办公网共用交换机？等保二级以上要求物理隔离或严格 VLAN 隔离，建议独立交换机。
NVR 和拼接屏之间不是一根 HDMI 线的事，项目规模决定架构复杂度。选型铁律是：小项目别过度设计，大项目别将就，解码路数和输出口数两条约束取大者配设备。建议在方案设计阶段就把 NVR 型号、解码能力、屏数、分割数、距离列一张表，对照本文决策树选方案。
屏体侧的接线盒位置、HDMI 线长、屏后理线空间、EDID 参数，建议在方案阶段就和 LCD splicing screen China source manufacturers对齐。像群茂显示这样覆盖 46、49、55、65 寸，拼缝从 0 到 3.5mm，支持伸缩支架和定制线长的工贸一体厂家，能把屏体侧配合前置到布线设计阶段，减少现场返工。具体产品参数和应用案例可以访问网站 www.szqunmao.com 查看，也可以直接搜索“群茂显示”联系售前技术团队。
如果你正在做监控中心或指挥大厅的连接方案，拿不准该走哪种架构、设备配几台、线缆怎么走，可以把项目路数、屏数、单屏分割数、解码器到屏的距离和 NVR 品牌组合整理一下发过来，我们可以帮你出一版架构建议和屏体侧配合方案。相关阅读可以看站内“拼接屏数量怎么算”“监控拼接屏网络布线方案”“解码器怎么选”三篇，三篇连起来就是从算屏数到布好线再到接对设备的完整链路。
Previous:Complete Guide to Network Wiring Scheme for Monitoring Splice Screen (2026 Edition)-Qunmao Display
Return to list
Next post: Not yet. 
Partner Links:
en
中文 
