Chopper 5 Velocity Study Proves Video Composite, Reveals Sloppy Photoshopping

Making the assumption that real planes invalidates video fakery, then if you are correct, logically there must be some error with my paper. What is the error?

The error is that you are interpreting common video compression artifacts as "cut and paste" fakery. The video you are using is the compressed version of probably another compressed version of probably another compressed version of the original footage. You also fiddled around with contrast settings in your examples, and god knows what else. IOW, this is worthless.

Back to reality: Maybe you want to address how Chopper 5 got to the exact spot at the exact time in order to match the perspective of the pre-recorded movie, how the filmakers were able to predict the weather on September 11 (I remember it rained two days earlier with a lot of fog) how the explosion of the WTC2 could have been fired off on cue. And maybe you want to tell us where the engine parts on Church Street came from (maybe they were photoshopped in too?). The eyewitness accounts were already addressed ad infinitum.

And maybe, at some point, you want to expand on why ANYONE would go through such a ludicrous effort in order to do WHAT EXACTLY? And why they still flew a plane into the North Tower?

What's your point?
 
The error is that you are interpreting common video compression artifacts as "cut and paste" fakery.

Show me a legitimate video frame of an object against a sky where it appears there is a swipe of digital paint that does not match the sky, and and area around the object that does not match the sky.

PastedPlane-Contrast.jpg


The video you are using is the compressed version of probably another compressed version of probably another compressed version of the original footage. You also fiddled around with contrast settings in your examples, and god knows what else. IOW, this is worthless.

No, it was digitized once, at 640 x 480 .mov file, by Eric Salter. The original is here.

Back to reality: Maybe you want to address how Chopper 5 got to the exact spot at the exact time in order to match the perspective of the pre-recorded movie,

It wasn't necessary to match anything that precisely. A plane flying north at around 9 am would do.

how the filmakers were able to predict the weather on September 11 (I remember it rained two days earlier with a lot of fog)

Crystal clear days are the easiest to repeat, in fact, the only type of weather it is possible to repeat. I suppose they were prepared to postpone the whole thing if weather didn't cooperate.

how the explosion of the WTC2 could have been fired off on cue.

It appears there was a 17 second delay between when the explosion went off, and the video was actually broadcast.

And maybe you want to tell us where the engine parts on Church Street came from (maybe they were photoshopped in too?).

You mean the one on the sidewalk underneath the tarp? Please. And the fuselage piece the roof of WTC5, that wasn't even in the photo from September 23, yet somehow gets "discovered" in October? And the passport? Have I missed anything?

The eyewitness accounts were already addressed ad infinitum.

Actually, on the other thread, we'll get into people like reporter Don Dahler, and the caller to Katie Couric, and firefighters, and others who were there, and didn't hear or see a plane.

And maybe, at some point, you want to expand on why ANYONE would go through such a ludicrous effort in order to do WHAT EXACTLY? And why they still flew a plane into the North Tower?

No, there was no plane at any of the 4 "crash sites". They did all this to justify the institution of a police state at home, and endless war abroad. They love power, and the vast riches ain't bad either.

What's your point?

That the entire government/media version of 9/11 is a provable hoax.
 
That the entire government/media version of 9/11 is a provable hoax.

With all due respect that is TOTAL BS. Your 'analysis' will never go further than ramblings on a web forum.

You have proved nothing. Your theory is on the fringe even among those who believe 911 was an inside job.
 
Assertions without substance.


Please, I know you all pride yourselves on being so scientific. If my study is "BS", then point out any error(s).
 
No, it was digitized once, at 640 x 480 .mov file, by Eric Salter.

Is NTSC video 640x480? Does NTSC video run at a 30.45 fps rate? Will compressing and downconverting an NTSC video to computer not introduce unpredictable errors? Do you know if this video has gone through other conversions before ending up in your hands? (It looks to my trained eye as if it's been recorded to VHS and then digitized). Do you not notice how everything in the video, including the overlay graphics, "wobbles" back and forth as a result of this conversion upon conversion? Can you really watch this video and not mourn the innocent people who died the instant that plane crashed into that building?
 
Assertions without substance.


Please, I know you all pride yourselves on being so scientific. If my study is "BS", then point out any error(s).

Assertions without substance? Wow that's calling the kettle black, don't you think?

For the love of God your study has been picked apart in this very thread. You just don't seem to realize it.

At least the people here have given your analysis some time. Most rational people, knowing the sheer volume of evidence and eye-witness accounts that directly conflict with your theory, would simply dismiss you without comment--and they would be totally correct in doing so.

At least give some people credit here for analyzing your analysis and quit claiming that nobody has pointed out any errors; your entire premise is one big error!
 
Last edited:
I've already proven to you that I can make fake videos on my little laptop that you can't tell are fake.
No, you didn't, because as I said at the time, I don't do QuickTime movies. Sorry, just an irrational dislike of the format. Try making something that will play in the standard Windows Media Player next time (I'm a neanderthal that way).

Besides, you didn't actually create a fake, you just cloned a real aircraft. That's not the same thing at all.

There are little details of motion that betray the fakery. That's what my paper is all about.
What's that old saying... "You can't see the forest for the trees." That's exactly the trap your study fell into.

You went frame by frame and tried to analyze each one individually to try and discern some sort of fakery. When you try going that deep into a moving image, and ending up with individual images, you actually lose the essence of the motion you're studying. Sometimes the best way to detect incorrect motion is by simply watching a video in real-time, and watching the suspect sequence over and over. That can be far more effective, since you can see how the motion looks.

I wish I had a clip from Aliens when Ripley first drives the powerloader so that you could watch it. Then I'd ask you what, if anything, looks odd about the way it moves. It's only by watching the clip at normal speed that the motion can be studied and the oddity noticed (it's very subtle; I doubt most people caught it). If you went frame by frame trying to analyze what's wrong with the motion you'd fail to see the problem because frame by frame you're not studying motion anymore - you're studying each frame as a self-contained entity.

To catch problems in motion, the image needs to be, well, in motion.

Here's another example: consider the case of a reaction shot close-up of an actor. In the shot the actor doesn't move or speak, but just blinks a couple of times. If that shot was shown to you in normal motion and with the shot reversed so that it played backwards without knowing which was which ahead of time, could you tell the difference? Could you tell which shot was forwards and which had been reversed to backwards? Remember, there's no speaking and no movement other than eye blinks. In other words, there's very little in the way of visual cues to differentiate between the forwards and backwards versions.

I could tell the difference. How? By the eye blinks. The way a blink looks in normal forwards motion is different from how it looks in reverse. It's subtle but definitely different.

That's the kind of fine detail in terms of motion I'm talking about.
 
Besides, you didn't actually create a fake, you just cloned a real aircraft. That's not the same thing at all.

Corsair, cloning a real aircraft is exactly what I think the perpetrators did. Clearly you did not read the paper you now pretend to criticize.
 
truthseeker your "paper' is irrelevant, it does not matter what you were able to reproduce on your laptop. We are not interested. The million or so who witnessed it live with their own eyes trumps anything you believe didn't happen. It is equivalent claiming the sun didn't rise in the sky in Atlanta today because it may have been cloudy and obscured, even though tens of millions witnessed the sun rise on the east coast. Your fantasy has no legs. Get professional help.
 
You went frame by frame and tried to analyze each one individually to try and discern some sort of fakery. When you try going that deep into a moving image, and ending up with individual images, you actually lose the essence of the motion you're studying. Sometimes the best way to detect incorrect motion is by simply watching a video in real-time, and watching the suspect sequence over and over. That can be far more effective, since you can see how the motion looks.


To catch problems in motion, the image needs to be, well, in motion.

Essence of motion? What is that?

Corsair, look. Velocity is the distance covered in a given amount of time. Each frame of video represents the same amount of time, 1/30 of a second. Actually, 1/29.97 of a second. Measuring changes in position per frame is the scientific way to analyze velocity on video.

Your suggestion is pseudoscientific new-age gibberish. I'll work on the Windows version of the RealOrFake plane for you. I have some very high quality ones coming too.
 
Last edited:
the Eyewitness statements have EVERYTHING to do with your paper. if you want to prove fakery , you have to prove that anything else (witnesses) weren't there to witness that actual event.


your continued dismissal of those witnesses is the sure sign of a poor researcher. YOU dont write paper to prove fakery until you address all possibilities to prove its not.


you have failed at the simplest form of research
 
the Eyewitness statements have EVERYTHING to do with your paper. if you want to prove fakery , you have to prove that anything else (witnesses) weren't there to witness that actual event.


your continued dismissal of those witnesses is the sure sign of a poor researcher. YOU dont write paper to prove fakery until you address all possibilities to prove its not.


you have failed at the simplest form of research
He hasn't failed! How can you fail at something you haven't done?
 
Corsair, cloning a real aircraft is exactly what I think the perpetrators did.
No, you've said an actual aircraft was shot as a separate element and then composited into a shot of the towers. What you did, from what others have said, is take a shot with an actual aircraft already in it and simply cloned a second aircraft into the same shot. That's not the same thing.

If you had taken an aircraft from one shot and then inserted into a completely different shot, that would be closer to what you claim (leaving aside the issue that you say the 9/11 composition was done in real-time and not prepared beforehand).

Velocity is the distance covered in a given amount of time. Each frame of video represents the same amount of time, 1/30 of a second. Actually, 1/29.97 of a second. Measuring changes in position per frame is the scientific way to analyze velocity on video.
And is meaningless due to the measuring errors arising from the quality of the material you're working with. This has been pointed out to you before.

Again, if you want to spot something wrong in the way something moves, you have to watch it move. Single frames are no longer movement.

If there was fakery in that video, then anyone with good eyes watching it at normal speed would see something wrong. They may not know what exactly, but they would feel something was wrong with the motion. That's precisely what happened when I first watched Aliens on the big screen - I knew something was wrong with the way the full-sized version of the powerloader moved. Then when I read about how that on-set effect was done, it explained exactly what the problem was that I had noticed.

Your suggestion is pseudoscientific new-age gibberish.
I've given you two concrete examples to assess your abilities in regards to analyzing motion - the scene from Aliens and the close-up question. Can you or can you not tell me if you see anything wrong with the way the powerloader moved in Aliens? Can you or can you not tell the difference between a shot played forwards and backwards which has no obvious visual cues?

If you cannot do either, then your analytical skills in regards to judging the incorrectness of a motion are suspect. Again: if a shot is faked it'll be visible at normal speed on repeated viewings. Frame by frame analysis is not a prerequisite to determine the authenticity of a shot.
 
Last edited:
Ace, three things that might be wrong (not enough information is given to tell for sure) with your control case. These are potential identifiable flaws in your study, regardless of what the results were.

1. The distance to the building.

Since your stabilization process requires locating the position of the edge of the building in the frame, any error in that process will cause just as much variation or error in the inter-frame movement (for the stablilized case) as error in determining the position of the plane. You positioned your control shot so that the plane is a similar distance to the 9/11 chopper shot. (Is that true, by the way? Was four miles the distance of the Fox 5 helicopter from the wtc?) But the buidling appears much closer than that, and it has a much sharper edge. That eliminates a significant source of error from your control that is present in the 9/11 footage.

2. Video Compression

Your paper says nothing about whether, and how, you compressed the control video to match the treatment of the 9/11 footage. Even if compression doesn't change the frame rate, it changes the positions of edges in individual frames. The apparent lack of comparable compression eliminates a significant source of error from your control that is present in the 9/11 footage.

3. Non-Blind Testing

When researchers perform a study that involves subjective measurements, such as the best estimate of the position of a partially blurred object in the video, they must be careful that the person or people performing the subjective measurements are not aware of which case (test or control) they are measuring. The determinations must in other words be "blind." Otherwise, bias comes in because the testers, without necessarily even being aware of it, alter their judgments based on what they want or expect the result to be. In fact, even when the tester is blind, it is well established that having an un-blind researcher with them as they make the measurement is enough to introduce bias. This happens because the testers react to the reactions (including non-verbal expressions) of the un-blind researcher.

Your study has the worst possible conditions for introducing this kind of bias: you have strong preconceptions about what the results "should" be to validate your beliefs, only one set of measurements was made, and you made them all yourself! You should not only have not made them yourself, you should not even have been in the same room when other people made them, and the people making them must not have any way of knowing which case they're working on. You know that you want to find, which is more variation in movement in the 9/11 footage and less in the test footage. It is very likely that this affects the decisions you make when you determine the pixel positions of the planes and the building edges. Therefore, bias toward those results is extremely likely to appear in the data.

This is not a question of deliberate dishonesty. No researcher, no matter how careful or honest, can trust his own judgment in such cases. The reputations of good, experienced scientists have been ruined when they think they're an exception, when they think they can make un-blinded judgments about test results without bias. You are not an exception either.

Respectfully,
Myriad
 
The question, then, for any video, is what is the margin of error for this video? It isn't zero, nor is it infinity. The idea is to attempt to quantify it. This is done by the use of control cases. I have provided my data. Thusfar, the claims that the margin of error is too large are based on absolutely nothing.

This is the flaw in your reasoning so far. Let's take this one step at a time.

Firstly, you are trying to prove the viability of a hypothesis that conflicts fundamentally with a huge body of eyewitness testimony, all of which is consistent to a reasonable degree; with a large body of video evidence; with the recorded testimony of air traffic controllers tracking flight 175; and with the physical evidence of aircraft parts recovered at the scene. To even begin to cast doubt on this body of evidence, your claim of fakery needs to be absolutely airtight.

Your arguments for fakery boil down to two specific observations. Firstly, you have observed a small variation in sky colour around the plane. Secondly, you have observed a random variation in plane position relative to its expected position, assuming constant velocity relative to the tower.
In order to have anything to say here, you have to prove beyond reasonable doubt that these effects cannot result from any other cause than fakery.

Concerning the variation in sky colour, it has been explained many times that this may be caused by video compression. Since the video is known to be compressed, this point is therefore worthless to your thesis. As of now, you only have the position variations.

So let's return to the statement you've made, that I quote at the top of the page. You have to establish the expected margin of error for the specific video you have used. That means that, to construct a suitable control case, you need to reproduce the conditions under which that video was recorded as accurately as possible. Note that this includes the distance, magnification, stability of recording platform, effect of mechanical vibrations on the camera mechanism, specific coding algorithms used at each stage of re-recording or conversion of the video and de-interlacing algorithm used. It is not enough to argue that these cannot have caused the effects you have seen; specific proof is needed.

Quite simply, your control case does not reproduce the conditions under which the video under study was recorded, or the subsequent treatment of that video. Without knowing those variables, you do not have a valid control case.

Dave
 

ISF - Join now!

Every member here is approved by hand. No bots, no spam, just people who care about evidence and honest debate.

Membership is free!

Create your free account

Back
Top Bottom