RT Software has many years of experience building and testing PC hardware intended for broadcast use. The grids below allow you to select the most cost effective but reliable PC build to satisfy your graphics requirements.
In many cases customers will provide the hardware themselves as this is usually the cheaper route, but it must meet or exceed the specifications listed here. Alternatively, for peace of mind, we can provide HP PCs to you.
Please refer to the notes to ensure you are selecting the most suitable system. If in any doubt please contact us and we can help.
How to use this page.
1. Start by deciding if you are using HD or UHD resolutions. UHD will add additional cost, especially for the GPU and Video cards.
2. Find the product you will be using. RT Software’s Swift range is modular so in many of our products (for example Swift News, Swift Studio) the core components will use 1 or more Swift Engine renderers. If you are unsure which products your project will be using please talk to us.
3. Use the grid to find the numbers of outputs, previews and inputs you expect to use.
4. Select the PC Build and Video card from the relevant columns. Note there are 2 sets of these – 1 pair for SDI, 1 pair for uncompressed IP (ST 2110). The reason for the different PC types is due to the additional air cooling required for the ST2110 IP video card*. The specification for these build types is shown further down.
5. You will need to add the NVidia GPU card to the PC build as shown in the grid. If more than 1 GPU is listed, the choice will be determined by the complexity of the graphics. Please contact us if you are unsure what to choose.
5. Video cards – either AJA for SDI, or NVIDIA/Mellanox for ST2110*. If more than 1 AJA is shown, this is down to the quantity of I/Os available. In some cases you may be able to combine cards to reach the number of I/Os required, subject to the number of PCIe slots (and PCIe lanes) available.
Laptops – Please refer to the Laptop tab at the bottom.
* Please note that the NVIDIA/Mellanox ST2110 cards require forced-cooling and we only recommend their use in a server-class chassis. Both the HP ZCentral 4R** and the Dell 7920R have been validated, with different builds of the HP ZC4R listed further down this page.
** We have listed the ZC4R to be used for uncompressed IP (ST 2110). It would be equally suitable for SDI, but it does add a little extra cost. We have shown both options to allow customers to make the best decision for themselves.
Swift CG / CG+
Swift Engine
Ref: | Video out | Preview out | Video in | GPU | Option 1 (Desktop) | PC Build | Video I/O (SDI) | Option 2 (Rack Mounted) | PC Build | Video I/O (ST2110) |
---|---|---|---|---|---|---|---|---|---|---|
H3 | 1 | 0 | 1 | RTX A4000 | Z2 | Kona 1 | ZC4R - Entry | NVIDIA Bluefield-2 | ||
H4 | 1 | 1 | 1 | RTX A4000 | Z2 | Kona 1 | ZC4R - Entry | NVIDIA Bluefield-2 | ||
H5 | 1 | 0 | 2 | RTX A4000 | Z4 | Kona 4 or Corvid 44 | ZC4R-Single | NVIDIA Bluefield-2 | ||
H6 | 1 | 1 | 2 | RTX A4000 | Z4 | Kona 4 or Corvid 44 | ZC4R-Single | NVIDIA Bluefield-2 | ||
H7 | 2 | 0 | 0 | RTX A4000 | Z8-HD | Kona 4 or Corvid 44 | ZC4R - Dual | NVIDIA Bluefield-2 | ||
H8 | 2 | 1 | 2 | RTX A4000 | Z8-HD | Kona 4 or Corvid 44 | ZC4R - Dual | NVIDIA Bluefield-2 | ||
H9 | 2 | 2 | 0 | RTX A4000 / A5000 | Z8-HD | Kona 4 or Corvid 44 | ZC4R - Dual | NVIDIA Bluefield-2 | ||
H10 | 2 | 0 | 2 | RTX A4000 | Z8-HD | Kona 4 or Corvid 44 | ZC4R - Dual | NVIDIA Bluefield-2 | ||
H11 | 2 | 2 | 2 | RTX A4000 / A5000 | Z8-HD | Kona 4 or Corvid 44 | ZC4R - Dual | NVIDIA Bluefield-2 | ||
H12 | 2 | 0 | 4 | RTX A4000 | Z8-HD | Kona 5 or Corvid 88 | ZC4R - Dual | NVIDIA Bluefield-2 | ||
H13 | 2 | 1 | 4 | RTX A4000 | Z8-HD | Kona 5 or Corvid 88 | ZC4R - Dual | NVIDIA Bluefield-2 | ||
H14 | 2 | 2 | 4 | RTX A4000 / A5000 | Z8-HD | Kona 5 or Corvid 88 | ZC4R - Dual | NVIDIA Bluefield-2 |
If you are considering Swift Screens for videowall applications, the number of outputs can be much higher than shown here and might be HDMI. Please talk to us so we can explain the options.
Tactic Lite (see below for Tactic Pro)
Tactic Draw
Tactic Live
Ref: | Video out | Preview out | Video in | GPU | Option 1 (Desktop) | PC Build | Video I/O (SDI) | Option 2 (Rack Mounted) | PC Build | ...................... |
---|---|---|---|---|---|---|---|---|---|---|
H16 | 1 | 0 | 1 | RTX A2000 | Z2 | Kona 1 | ZC4R - Entry | |||
H17 | 1 | 0 | 2 | RTX A2000 | Z4 | Corvid 44 or Kona 4 | ZC4R - Single |
Tactic Pro (see above for Tactic Lite)
Tactic Pro supports record to disk. For each channel of record an additional SSD should be included in the build. You could use various sizes, but example capacities for a 1TB disk using DNxHD is shown below:
* Using Record to Disk is CPU intensive and therefore we would recommend using a Z4 as the entry level spec, not Z2 as shown in the list.
Ref: | Video out | Preview out | Video in | GPU | Option 1 (Desktop) | PC Build | Video I/O (SDI) | Option 2 (Rack Mounted) | PC Build | ...................... |
---|---|---|---|---|---|---|---|---|---|---|
H20 | 1 | 0 | 1 | RTX A4000 | Z2 | Kona 1 | ZC4R - Entry | |||
H21 | 1 | 0 | 2 | RTX A4000 | Z4 | Corvid 44 or Kona 4 | ZC4R - Single |
Swift CG / CG+
Swift Engine
Ref: | Video out | Preview out | Video in | GPU | Option 1 (Desktop) | PC Build | Video I/O (SDI) | Option 2 (Rack Mounted) | PC Build (Rack Mounted) | Video I/O (IP-ST2110) |
---|---|---|---|---|---|---|---|---|---|---|
U1 | 1 | 0 | 0 | RTX A4000* / A5000 / A6000 | Z4 | Corvid 44 | ZC4R - Dual | NVIDIA Bluefield-2 | ||
U2 | 1 | 1 | 0 | RTX A5000 / A6000 | Z8-UHD | Corvid 44 | ZC4R - Dual | NVIDIA Bluefield-2 | ||
U3 | 1 | 0 | 1 | RTX A4000* / A5000 / A6000 | Z8-UHD | Kona 5 or Corvid 88 | ZC4R - Dual | NVIDIA Bluefield-2 | ||
U4 | 1 | 1 | 1 | RTX A5000 / A6000 | Z8-UHD | Kona 5 or Corvid 88 | ZC4R - Dual | NVIDIA Bluefield-2 | ||
U5 | 1 | 0 | 2 | RTX A5000 / A6000 | Z8-UHD | Kona 5 or 2x Corvid 88 | ZC4R - Dual | NVIDIA Bluefield-2 | ||
U6 | 1 | 1 | 2 | RTX A5000 / A6000 | Z8-UHD | Kona 5 or 2x Corvid 88 | ZC4R - Dual | NVIDIA Bluefield-2 |
*Offline CG Editor only. In order to keep costs low we have provided a range of card options in the GPU column. Please refer to the comments in the GPU section below for further guidance.
If you are considering Swift Screens for videowall applications, the number of outputs can be much higher than shown here and might be HDMI. Please talk to us so we can explain the options.
Tactic Pro
Ref: | Video out | Preview Out | Video In | GPU | Option 1 (Desktop) | PC Build | Video I/O (SDI) | Option 2 (Rack Mounted) | PC Build | .................... |
---|---|---|---|---|---|---|---|---|---|---|
U21 | 1 | 0 | 0 | RTX A5000 / A6000 | Z4 | Kona 5 or Corvid 88 | ZC4R - Single | |||
U22 | 1 | 0 | 1 | RTX A5000 / A6000 | Z4 | Kona 5 or Corvid 88 | ZC4R - Single | |||
U23 | 1 | 0 | 2 | RTX A5000 / A6000 | Z4 | Kona 5 or 2x Corvid 88 | ZC4R - Single |
Additional Notes for Graphics PCs/Servers
Swift Services –
DataServer, MediaWatcher, Repository
Spec | Typical systems can run multiple applications on the same PC* |
---|---|
CPU | 2 core or higher, running at 3GHz or higher. |
Disk | 512 GB or higher |
RAM | 8GB or higher |
These management applications will not require the same level of resources as graphics rendering machines. Typical specs above could support all 3 applications on the same hardware simultaneously. For larger workloads, long term storage of assets might require a larger 1TB disk, which will not add much cost.
*System designs that require Data Server to serve large quantities of rendered graphics streams to Swift Live or NRCS clients may require more hardware. We will advise on a project by project basis on the specs required for this.
Core server system design supports single or dual redundant modes. Various architectures are possible, all come with a balance of cost vs performance.