Cinegy Encode 22.12
Reading time ~2 minutes
Operating Systems Support
Note
|
Cinegy products work only on machines with CPU supporting minimum instruction set SSE4.1 |
Cinegy Encode is certified to run on the 64 bit editions of the following operating systems: Windows 10*, Windows Server 2012 R2*, Windows Server 2016*, Windows Server 2019.
Caution
|
We recommend updating Windows OS to include the latest Microsoft updates and hotfixes. |
Supported SDI I/O Boards
Cinegy Encode supports the SDI boards for baseband I/O described in the Input and Output Boards Recommendations section.
Note
|
Please note that DeckLink SDI, Decklink Studio, Decklink Extreme, Decklink Duo and Decklink Quad legacy boards do not support full duplex mode, therefore live pass through is only possible with two boards, first serving the input and second providing the output. |
Hardware Recommendations
The actual performance of a machine depends on the number of running channels and their resolution, enabled inputs and outputs and RTP encoding/decoding, therefore no precise hardware recommendation can be given.
Nevertheless, as we keep optimizing our software tools for better performance, the following typical configurations have been tested for our own and our customer’s reference:
Application |
Single Xeon E5 2620v3 CPU 16GB DDR4 RAM |
Dual Xeon E5 2630v3 CPU 32GB DDR4 RAM |
Dual Xeon E5 2697v3 CPU 128GB DDR4 RAM |
---|---|---|---|
Recommended Number of Simultaneous Channel Instances |
|||
SD |
1 |
4 |
16 |
HD |
– |
2 |
4 |
Ultra HD |
– |
– |
1 |
Note
|
These system recommendations use older hardware which has been previously tested. The CPU’s listed should be used as a guide to select modern equivalent options and not as direct requirements. |
RTP Streaming Network
It is highly recommended to split the file and streaming operations between two physically separate networks. Therefore please consider that all your servers and workstations have two Gigabit Ethernet adapters.
Please disable the "File and Printer Sharing for Microsoft Networks" and "Client for Microsoft Networks" options for the adapters connected to RTP network, and uncheck the "Register these connection’s addresses in DNS" in this adapter’s TCP/IPv4 settings (see Advanced/DNS tab).