Visible to Intel only — GUID: jbo1660918515331
Ixiasoft
Visible to Intel only — GUID: jbo1660918515331
Ixiasoft
33.3. Interlacer IP Functional Description
It may not be appropriate for the interlacer to produce an interlaced sequence according to the original interlaced history for the progressive frames. For example, if frame rate conversion occurs after deinterlacing and before the interlacer, the rate conversion may destroy the original sequence of alternating F0 and F1 fields. You can set a parameter for this feature if you do not turn on Memory-mapped control interface via the register map, or via a register map setting if Memory-mapped control interface is on. This feature is only available when using the full variant of the Intel FPGA Streaming Video protocol as image information packets make it work. Image information packets are not available with the lite variant.
If you do not turn on run-time control of the IP through the register map, the IP converts all progressive input frames to interlaced fields. After any change to the height, width, or interlace identifier specified in the incoming image information packets, the IP resets the sequence of F0 and F1 fields at the output. The Send F1 first parameter sets whether F0 or F1 is sent first after any reset. If you turn on run-time control via the register map, you can select whether the output sequence restarts with an F0 or an F1 field at run time, and the parameter is unused. Run-time control also allows you to turn off interlacing and pass through the progressive frames unaltered. If you turn on Lite mode, you must set the image information values (input frame width, input frame height and input interlace nibble) via the register map. Any edits to these registers cause a reset of the output interlacing sequence. Similarly, changes to these values in the incoming image information packets cause a reset with the full variant of the protocol.
Override of interlace sequence from image information packet
The interlaced nibble field in the Intel FPGA Streaming Video image information packets indicates the progressive or interlaced format for each video field.
Interlaced nibble | Frame format |
0 | Progressive frame, deinterlaced from an F0 field |
1 | Progressive frame, deinterlaced from an F1 field |
2 | Progressive frame |
3 | Progressive frame |
4 | Progressive frame, deinterlaced from an F0 field |
5 | Progressive frame, deinterlaced from an F1 field |
6 | Progressive frame |
7 | Progressive frame |
8 | Interlaced F0 field, paired with the F1 field preceding it |
9 | Interlaced F0 field, paired with the F1 field following it |
10 | Interlaced F0 field, pairing unknown |
11 | Interlaced F0 field, pairing none |
12 | Interlaced F1 field, paired with the F0 field following it |
13 | Interlaced F1 field, paired with the F0 field preceding it |
14 | Interlaced F1 field, pairing unknown |
15 | Interlaced F1 field, pairing none |
By default, the IP passes through fields preceded by image information packets that specify interlaced unaltered. The IP converts progressive frames to an alternating sequence of F0 and F1 fields. However, if a progressive frame has been created as a result of deinterlacing original interlaced content, you may want the interlacer to restore this original interlaced content. Interlace nibble values 0, 1, 4 and 5 allow a system to communicate the original interlaced format of a progressive frame to the interlacer so that this process can be reliably implemented.
If you do not want the interlacer to process any original interlaced history for the progressive frames, the IP does not preserve the original sequence of alternating F0 and F1. For example, if the applies frame fate conversion to progressive frames. You can set a parameter for this feature if you do not turn on Memory-mapped control interface via the register map, or via a register map setting if Memory-mapped control interface is on. This feature is only available when using the full variant of the Intel FPGA Streaming Video protocol as image information packets make it work. Image information packets are not available with the lite variant.