The video wall has a 12 camera limit to protect users from inadvertently creating network congestion, and to ensure browser stability on almost all computing platforms. Each video tile in a video wall is a 720p resolution video stream at the configured bit rate. At the 'Enhanced Quality' setting this will equate to a 12 tile video wall using 9180kbps.
Playback speed increases will increase the bandwidth required per camera by the playback speed multiplier. For example a camera at ‘Enhanced Quality’ settings will go from 765kbps to 1530kbps at 2x. Importantly this also includes the video wall bandwidth usage and could lead to a bandwidth requirement of up to 18460kbps for a video wall of 12 cameras at 2x or 27540kbps at 3x.
This type of bandwidth consumption is inconsequential on the LAN but due to the seamless cloud proxy, a remote user could suddenly saturate most uplink speeds at small locations. The 12 camera limit tries to put some upper bounds on the potential bandwidth consumption under normal circumstances.
As has been stated in this post, our recommend way of simultaneously displaying more than one video wall is to use independent browser tabs or windows. This has the added advantage of allowing video walls to be pinned to monitors and increasing stability as it distributes video decode over numerous threads and processes.
In our testing we have run 50+ concurrent streams on an 8 monitor setup using a 4 core current generation Xeon processor with 16GB of RAM and a dedicated NVDIA GPU. Ultimately browser stability at such loads can become an issue, but <30 streams should be achievable on most systems.