Why does the Deinterlacer II IP core GUI erroneously create a deinterlacer IP with no I/O ports? - Why does the Deinterlacer II IP core GUI erroneously create a deinterlacer IP with no I/O ports? Description Due to a problem with the v16.1.2 version of the Deinterlacer II® IP, the GUI will erroneously create a deinterlacer with no I/O if motion adaptive mode is selected without cadence detection and reverse pulldown, but with 3:2 & 2:2 detector with video over film still showing as a grayed-out cadence detection algorithm selection. Resolution To work around this issue in v16.1.2, enable cadence detection and select one of the other cadence detection modes. This problem has been fixed starting in software version 17.0. Custom Fields values: ['novalue'] Troubleshooting FB: 452928; True ['Video and Image Processing'] ['FPGA Dev Tools Quartus® Prime Software Pro'] 17.0 16.1.2 ['Programmable Logic Devices'] ['novalue'] ['novalue'] ['novalue']