ENC-400-HDMI
™ H.264 Encoder
User Guide V 2.1
29
ENC-
300 is the ‘TCP/SERVER’. For more information, please see chapter 4.3 on
page 67.
Send
Buffer
Size:
The ’Send Buffer Size’ specifies how much TCP data are maximal stored at the
sender side (at the encoder side). The higher the value, the more network
problems can be absorbed, but the higher is the delay at the decoder in error case.
After an error case, the delay decreases again. The delay increases only, if an
error occurs in the network. That means: If no network problems occur, the delay
does not increase, even though a high value is set in the ’Send Buffer Size’ field.
For more information, please see chapter 4.3 on page 67.
.!.
This field is only available when TCP is chosen as transport
protocol.
Stop Interval:
Specifies the time interval in sec. for reconnecting in error case. This field is active
when ‘TCP/CLIENT’ or ‘UDP’ is used as ‘Transport Protocol’ in the ENC-300™.
For more information about TCP, please see chapter 4.3 on page 67.
Source Port (1-
65535):
Specifies the port number of the source in the UDP/TCP datagram. You can set
the source port to static port number which is entered manually. Or you can set
the source port to port number which is set automatically by the encoder. As
default the source port is set to 9200. The automatically mode can be set by
entering the value ‘0’ in the text field and by confirming this entry with the 'APPLY'
button.
.!.
If you change the ‘source port’ manually, please be sure, that your
entered port number is smaller than 1024 and higher than 9200,
because in the range from 1024 and 9200 there are some reserved
and used port numbers. For example GPIO uses the port number
7778 and the comport 7777. Talkback uses the port number 9177
and SNMP and SAP uses also reserved port numbers.
FEC Dimension: Specifies the FEC dimension. You can choose between:
1D-FEC
2D-FEC
A packet matrix must be defined at the Forward Error Correction (FEC). Therefore,
the user specifies FEC rows and FEC columns from which row check sums and
column check sums will be generated (FEC algorithm = XOR). These check sums
will be send to the destination and the destination can correct an occurred packet
loss via these check sums. At ‘2D-FEC’ you have a packet matrix, which has FEC
rows and FEC columns, and the check sums of the rows and columns will be send
to the destination. See also chapter 4.4 on page 72.
At ‘1D-FEC’ you have also a packet matrix which has FEC rows and columns, but
only the column check sums will be send to the destination. The overhead of ‘1D-
FEC’ is lower than ‘2D-FEC’.
FEC Rows:
Specifies the FEC row value. The value range is between 4 and 20. A packet
matrix must be defined at the Forward Error Correction (FEC). Therefore, the user
specifies FEC rows and FEC columns from which row check sums and column
check sums will be generated (FEC algorithm = XOR). These check sums will be
send to the destination and the destination can correct an occurred packet loss
via these check sums. See chapter 4.4.
.!.
For the lowest overhead (+5%) Teracu
e recommends using a ‘FEC
Rows’ value of ‘20’, a ‘FEC Columns’ value of ‘5’, the ‘1D-FEC’
dimension and ‘Block Aligned’ as ‘FEC Traffic Shaping’.
FEC Columns:
Specifies the FEC column value. The value range is between 1 and 20. A packet
matrix must be defined at the Forward Error Correction (FEC). Therefore, the user
specifies FEC rows and FEC columns from which row check sums and column
check sums will be generated (FEC algorithm = XOR). These check sums will be
send to the destination and the destination can correct an occurred packet loss
via these check sums. See chapter 4.4.
.!.
For the lowest overhead (+5%) Teracue recommends using a
‘FEC Rows’ value of ‘20’, a ‘FEC Columns’ value of ‘5’, the ‘1D-
FEC’ dimension and ‘Block Aligned’ as ‘FEC Traffic Shaping’.
FEC
Traffic
Shaping:
Specifies the FEC traffic arrangement. You can choose between:
Block Aligned (for a linear use of the bandwidth)
Non Block Aligned (for a time-linear packet flow)
Low Delay
