Honored Contributor
Honored Contributorhi,
I'm now able to change the single Y color plane to 3 * Y color planes in parallel without getting the on/off switching on the output screen. It looks like the on/off switching on the output screen was due to characteristics in the videostream. The deinterlacer (which is providing the source to my custom module) is actually providing two control data packets(only the parameters from the last received control data packet is used by the VIP modules). One of the control data packets contain width and height payload as expected with width = 640 and height = 480 while the interlacing payload is "0000". The other control data packet contains width = 640 while the height is 240 and the interlacing payload is "1010", this control packet is the one that should be discarded. In my custom module, where I'm monitoring the input from the deinterlacer inorder to detect control data packets, the 640x240 control data packet was causing missmatch between what is received and what is sendt from my custom module(mainly due to different characteristics of the valid signal durring the control data packets. The startofpacket for the videodata packet going out from my custom module was set at the wrong time). Regarding the noise, I still havent been able to solve that issue. This noise can sometimes be present after I compile my design, while other times it's not. Could this be timing related ? I tryed placing some assignments in Quartus2, inorder to improve timing characteristics. For instance, I used the "Fast Output Register" assigment for the video data and sync signals going to the output screen and also I set "Fast Input Register" for the video stream received from the camera, however this only increased the noise.
