--- Quote Start ---
Can I ask what you saw or read that made you assume the scaler would simply discard any data that existed beyond the length specified in the control packet? I would be surprised if that were the case. The control packet is simply to inform the scaler of how many pixels are in each line, and how many lines there are. Using this information it can determine things like:
- Which phase to use given a certain scaling ratio.
- When to begin reading in the next line vs. continuing to operate on a currently buffered line.
Maybe if you give the "endofpacket" signal with the 1024th pixel, the following extra pixels will be ignored. I guess I'm thinking if we lie to the scaler, we can't expect it to behave in any certain way.
Jake
--- Quote End ---
I saw the error recovery section of the used guide and understood the extra data discarding
behaviour.At last i could able to solve the scaler runtime controlling problem. But still some issues are there regarding the algorithm and my kit.
I had no problem using the nearest neithbour,bilinear , bicubic and polyphase upto 12 taps and 16 phases but with 12 taps and 16 phased the error led on my cyclone 3 development kit is glowing and i could not get the output.
Do u have any idea regarding the phase and tap selections and their effects regarding my problem.
Do u have used the deinterlacer megacore with motion adaptive algorithm,since i had some doubts regarding it.can u help me in clearing them.
Honored Contributor
