On Sat, 30 Apr 2016 22:49:01 +0100, Christopher Woods wrote: > The deinterlacing algorithm is doing no resizing - it's interpolating > between the frames and then 'printing' that to 50 progressive frames. The > resulting image will have slightly lower definition due to the bob > artifacts as it's reconstructing the frame from two sequentially > interlaced fields, but it hasn't changed resolution.
Sorry, I'm still missing what is actually going on but I think I'm getting there. Is the first reference to "frames" refering to a frame constructed from the two fields designed to be shown at 25 fps? Lets call this F1. At 50 fps we need twice as many frames so an F1 and an F2. F2 doesn't exist and is created by interpolation between the current F1 and the next F1. -- Cheers Dave. _______________________________________________ get_iplayer mailing list [email protected] http://lists.infradead.org/mailman/listinfo/get_iplayer
