Dave Rogers - thank you for a reasonable reply.
No problem. Even if I think your theories are insane, you're at least making an effort to do some analysis.
Adding control samples is a great idea. I'm quite sure that planes don't leave trails of pink pixels behind them. I'm quite sure that noses of airplanes don't ever look like a swipe with a digital paintbrush.
Now that's a bit of a problem with your theory - you're suggesting that this video was composited in real time, so who was quick enough with the digital paintbrush to edit out a few inconvenient details in 1/25 of a second before the next frame needed reviewing and editing? Please don't try and say that the video you're analysing has been doctored after the fact, because that would invalidate every word you've said.
I have certainly considered measurement accuracy. This is why I chose to track the outline of the entire plane. Shifting the outline even 1 or 2 pixels causes an obvious misplacement. To say that the placement of the outline could be off by 4 pixels in either direction, is simply not plausible to me. 1 pixel, quite possibly. 2 pixels, I doubt it but maybe. 3 pixels, no. 4, certainly not.
That's a highly subjective analysis. Remember that this is compressed images and that the edges are spread over several pixels either way. Do you know the accuracy of the frame rate of the original video? Was the source MPEG compressed? I don't know a huge amount about MPEG, but as I understand it only every ninth frame is stored as a complete image, two frames in between are stored as partial images for interpretation, and the remaining six in every nine are completely interpolated, not having been stored in any way at all. (I may be wrong here - somebody tell me if I am.) Any idea how all that affects the accuracy of the position of objects moving across the field of view? Given the very small errors in position you're looking at here, there are plenty of sources of error. You need to eliminate all of them, including the ones I haven't thought of, before you have the beginnings of an argument.
There would be strong anti-correlation between tower movement and velocity variations ONLY if the camera movement was significant, compared to the camera movement on the plane. It isn't. The chopper 5 camera movement is quite smooth. It was the camera movement on the original plane video that was unsteady.
Stop right there Dave. I clearly state that the airplane video is NOT at a constant velocity, rather that it has unstable velocity due to camera motion.
It makes sense to have an unstable airplane video, knowing that the live shot will be from a helicopter. If the airplane flew at a steady apparent velocity, while the Chopper 5 camera moved, this would be a dead giveaway.
Now the three quotes above reveal a striking logical flaw in your theory. You're suggesting that the conspirators deliberately chose an airplane video with unstable velocity due to camera motion so that it would look right on the composite picture, and
as a direct result of that choice it looks wrong on the composite picture because the camera motion from the helicopter doesn't cause unstable velocity. It's hard to comprehend the mental confusion you're attributing to the conspirators here, but I'll try. The reasoning goes like this, I think.
1. We know that camera shake causes apparent velocity variations in moving objects. We can do some experiments to determine the magnitude of the effect - that's quite easy.
2. If we don't reproduce that camera shake effect, it will be obvious that the video is faked, because a +/- 1 pixel variation between where the plane is and where it should be will make the fakery clearly visible.
3. Therefore, we need to choose a video that precisely matches the camera shake of the helicopter video we're adding it to in real time.
4. So, let's use a video with a random +/- 3 pixel variation that is of necessity uncorrelated to the helicopter footage (because that will be filmed live) and that will give an overall +/- 4 pixel error in position.
So the conspirators have deliberately and predictably introduced an additional source of error that makes the video appear four times worse than it would have been if they'd chosen to use a video without camera shake. They're clever enough to come up with an unknown new real-time video compositing program to do the fakery, but not clever enough to know that 4 > 1 or that uncorrelated noise signals are additive.
They chose a video where the plane appears to slow down in the middle of the frame, because they wanted it to disappear inside the tower. They did everything pretty much right, except, the chopper drifted to the left during the shot just enough to screw up their masking by that amount. That's why the darn nose appeared to come out the other side.
OOPS.
But choosing a video where the plane appears to slow down means that any drift either way by the chopper will screw up the masking. This would all have been obvious before the fact to anyone who spent longer than a few minutes actually thinking about the implications of these details. Again, you're assuming that the planners didn't do some very simple and basic thinking about what could go wrong - assuming the viewpoint of a shot taken from a helicopter will be fixed is simply insanely risky, and nobody in their right mind would stake their life on it. Because that's what it boils down to - get this wrong, and it's a treason charge and execution.
I know we talk about Occam's razor a lot here, but this is a prime example of its application. Your original hypothesis was shown not to be a good explanation of the facts. Your response has been to invent a new postulate with no supporting evidence to explain the discrepancy. The next level, of course, is that you'll say that the camera was supposed to drift right so it would look like the plane was slowing down as it entered the tower, but it drifted left instead by mistake, or something like that. At every step you have to tack new bits on to your theory to hold it together, and it just gets even more implausible. And all you have is a +/- 4 pixel error on a compressed video.
Dave