Chopper 5 Velocity Study Proves Video Composite, Reveals Sloppy Photoshopping


Now, imagine you’re holding the camera for the screenshot on the left. How far left do you suppose you’d have to walk to be able to see the “plane” on the opposite side of the other tower, as shown on the right? Do you think 45 degrees would do the trick? Maybe 30? How about 20? Well, according to my calculations, the difference between these two camera angles is only about 6 degrees.

That's a classic example of non-evidence. The writer makes some wild guesses at a number, doesn't even try to do any calculations to justify it, doesn't even say what the number is, then states that it differs from a different number that he doesn't give his calculations for. It's the usual truther argument - "We know A is different to B, even though we don't know what A is." If there's a case there, I'd like to see the working (and, of course, the error bars).

Dave
 

The basic claim in that is that the difference in angle is only 6 degrees. The blogger claims to have calculated that, but does not mention how.

However, three things influence the apparant position of the plane in the videos.

1) The angle between the camaras.

2) The distance between the camaras and the target.

3) The Zoom factor (because zooming distorts angles).

The only way to verify if the image of the plane is in different places in the two videos is to plot the camara position on a map (presumably informaton on their position can be retrieved, if not otherwise then by contacting the people making the shots). Then it wil be possible to plot the trajectory of the plane images and see if they correlate.

My assumption is that they do. You are welcome to explore the matter, but be SURE to provide ALL data.

Hans
 
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.

The "large body of video evidence" is self-contradictory. We have planes flying through different paths in 3D space, different plane colors, impossible physics, missing audio tracks, strange edits, etc. etc. etc.

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.

No, Dave. Compression wants to make similar colors the same. It doesn't want to make the same colors different. Compression will tend to add a halo around objects of high contrast with the background. Funny that this halo exists around certain parts of the plane, but not down where the pink sky is. Seems that the perps needed to keep the sky behind the engines from the original, so that the wake vortex effects would appear. Their absence would have been a giveaway.

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

Fair on some points, not fair on others. Of course a control should attempt to match every single thing, but theoretically that could include the exact model airplane, the exact camera, lens, everything. Such is not needed to show proof of concept. Most relevant are the apparent size of the plane in the picture, and the video processing used. Matching mechanical vibration is not needed, eliminating mechanical motion is the purpose of stabilization.

I am in contact with the "curator" of the video, and I've sent him a full sized copy of my controls. Though I believe I've shown control cases which would have a greater margin of error than Chopper 5, I'll work to create more control cases that address these issues even more thoroughly than the current ones.

Thank you again for your input.
 
The "large body of video evidence" is self-contradictory. We have planes flying through different paths in 3D space,

I assume you mean http://911logic.blogspot.com/2007/01/911-tv-fakery-45-degree-ua175-flight.html. This is a piece of analysis that relies critically on calculating camera angles from the apparent width in pixels of the two visible faces of the towers. The problem with this analysis is, as usual, that it assumes no measurement error. Looking at the pictures used to deduce the 11.5 degree and 23.5 angles on the camera shots, it's not at all clear where in fact the corner of the tower is, but there's a light coloured feature that appears to be treated as part of the side face when it may well be part of the front face. A discrepancy of about 4 pixels in the measurement of an 8 pixel apparent width would be enough to account for the supposed differences in viewing angles, and this is in measuring a feature which fades to grey.

different plane colors,

Did you miss the bit where it was shown that this was the effect of the plane flying into the shadow cast by the smoke cloud from WTC1? You know, the thick black oxygen-starved-fire smoke?

impossible physics,

Pure fantasy. The impacts have been modelled using the existing laws of physics, and nothing impossible was observed.

missing audio tracks, strange edits, etc. etc. etc.

This is just blowing smoke.

No, Dave. Compression wants to make similar colors the same. It doesn't want to make the same colors different. Compression will tend to add a halo around objects of high contrast with the background.

Thise two sentences don't exactly agree with each other.

Funny that this halo exists around certain parts of the plane, but not down where the pink sky is. Seems that the perps needed to keep the sky behind the engines from the original, so that the wake vortex effects would appear. Their absence would have been a giveaway.

Hang on a minute - I thought you were saying the videos were faked because you couldn't see wake vortex effects. Now you're saying that the haloes were included so as not to exclude wake vortices. I think you're getting a bit confused here. Are they visible or not, and is it their presence or absence that proves fakery?

Fair on some points, not fair on others. Of course a control should attempt to match every single thing, but theoretically that could include the exact model airplane, the exact camera, lens, everything. Such is not needed to show proof of concept. Most relevant are the apparent size of the plane in the picture, and the video processing used. Matching mechanical vibration is not needed, eliminating mechanical motion is the purpose of stabilization.

I would argue, in fact, that matching mechanical motion and stabilisation is crucial - do you know what stabilisation techniques were used on the original shot, and what artefacts they might produce? If not, you don't have a valid control. As for proof of concept, you're not trying to prove that the video could have been faked, which is what proof of concept entails; you're trying to prove that the video must have been faked, which means you have to eliminate every other possibility.

Dave
 
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.



Another factor missing from his control cases is the speed of the airplane. From what I've seen, his control cases appear to be planes that are landing or taking off, which we know would be moving significantly slower than the plane that hit the tower. Such high-speed movement also creates artifacts when recorded using electronic/digital cameras. He needs to either allow for this factor in his analysis, or find a control case of a plane flying much faster.
 
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.

[qimg]http://www.acebaker.com/9-11/PinocchioStudy/PastedPlane-Contrast.jpg[/qimg]

Here is an image I took of that video you linked below, cropped it and changed brightness contrast a bit. Notice the Halo on the right edge of the Left Tower? Guess there was no tower on 9/11 and they pasted some pre-recorded footage in there. Also notice the weird color clouds within the Towers. Strange, isn't it?

wtc.jpg




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

Fair enough. But you do agree that you cropped it massively and fiddled around with the contrast, to start with? 640 x 480 is not really a high res to start with and you blow it up by what? 400% if not more.

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

You're kidding me right?

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.

Oh, I am certain. "Dudes, the weather doesn't match our pre-recorded clip. Call back the other planes. I know, it sucks. Defuse the charges. See ya all tomorrow for another try"

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

Where does it appear so?

You mean the one on the sidewalk underneath the tarp? Please.

Yes. As I remember there was an entire turbine there. Why 'please'? Was it photoshopped into the NYT-pics too? Prerecorded?

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.

I talked to people at 9:30 am who saw the second plane hit. Or heard it. A co-worker of mine, Bethany Kobe, lived in Battery Park City. She said the thing practically flew through her bedroom. You are a truly living in a parallel universe.

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.

You are entitled to your opinion. We are talking about facts here, though.

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

Then why don't you and your ilk finally bring on some "provable" evidence?
 
Last edited:
Ace said:
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.

Still waiting to see that police state arise...
 
No, actually i did account for the motion of the helicopter. I stabilized the video.
No, you have to know where the helo is and how it moves for every frame you use. You have zero knowledge of where and how the helo is moving, and the algorithm of the gyro stabilized video from the helo. You are totally out of your ability to analyze this, and you will never prove something that was witnessed by real eyes. Sorry, you need to seek help from professionals and stop being silly with this effort to prove the impossible.
 
Bad news, Ace.Your original video is compressed.

Sorenson three is a variant of H.264. http://www.nuntius.com/technology3.html H.264 uses motion compensation and motion prediction in its compression, as well as using DCT. Your samples were uncompressed video, Ace.

Comparison invalid. Try again, and see if you can do it right.
 
Then why didn't they use a fixed camera?? :rolleyes:

I think Ace said that the camera shake was added to the plane video to compensate for the expected camera shake from the live video from the helicopter. When I pointed out that anyone with a first year college education knows that random errors accumulate, he stopped saying it, and said that he didn't have to explain why they used a shaky video.

Dave
 
I think Ace said that the camera shake was added to the plane video to compensate for the expected camera shake from the live video from the helicopter. When I pointed out that anyone with a first year college education knows that random errors accumulate, he stopped saying it, and said that he didn't have to explain why they used a shaky video.

Dave

Not quite. The perps knew that if they inserted a perfectly stable shot into a shaky shot, that would be a dead giveaway. So that's out. Best bet is to lay a shaky shot into another shaky shot, try to keep the shake down to a minimum, and blame the resulting errors on measurement imprecision, as Dave is now doing.

On a frame by frame basis, the random errors in the live shot can either add to or subtract from the random errors already present in the overlay.

In general, we can say that the Chopper 5 shot was more smooth and stable than the overlay shot. Around frames 8,16,18,22, and 41, the Chopper 5 motion was such that it added to the error. Around frames 9,21, and 39 the motion was such that it subtracted from the error.

The cumulative error predicted by Dave is indeed evident.
 
Last edited:
Not quite. The perps knew that if they inserted a perfectly stable shot into a shaky shot, that would be a dead giveaway. So that's out. Best bet is to lay a shaky shot into another shaky shot, try to keep the shake down to a minimum, and blame the resulting errors on measurement imprecision, as Dave is now doing.

The point I made, which I think needs re-stating because you've clearly completely failed to appreciate it, is that nobody with a freshman college level education or better would think that what you've suggested could do anything but increase the shakiness of the shot. You're assuming that the people who you imagine did this had exactly the same appreciation of the accumulation of random errors as you do - in other words, very little. Overlaying a shaky shot on to another shaky shot can only result in a doubly shaky shot, and anybody with enough of a scientific education to be able to devise a real-time system for producing this sort of overlay - which, I'll remind you, you have not claimed to be able to do - would be certain to know that.

Given that measurement errors are not ruled out - in particular in the light of MortFurd's discovery that the original video was compressed using motion compensation and motion prediction, which can produce exactly this sort of artefact - then we have a simple theory (compression artefacts) or an internally contradictory and technologically infeasible theory (a system that can carry out real-time overlays of videos on to a live feed, operated by a team which does not include anyone with at least a first-year university science education) to explain the behaviour you've seen. Since the infeasible and contradictory theory also contradicts eyewitness testimony, radar tracking and physical evidence, it doesn't seem like a terribly useful one.

Dave
 
Not quite. The perps knew that if they inserted a perfectly stable shot into a shaky shot, that would be a dead giveaway.

And how did you find out that they knew this ?

This is still Hollywood-style (or Hollywoo-style) deduction, where one can make up explanations on the fly and the audience just nods. Reality isn't like that.

Best bet is to lay a shaky shot into another shaky shot

And thereby exarcerbating the problem.

try to keep the shake down to a minimum, and blame the resulting errors on measurement imprecision, as Dave is now doing.

Yeah, sure. In a pig's eye.

In general, we can say that the Chopper 5 shot was more smooth and stable than the overlay shot.

What overlay shot ? Ah, yes, the one you still hasn't proven exists.
 
1. Distance to the building in the control footage.

2. Lack of comparable compression in the control footage.

3. Measurements dependent on subjective assessments (of "best fit" frame positions of airplane and building edges) performed by un-blinded assessor.

These are three substantial problems with your control case, and hence with your study's conclusions. Note that they would be considered problems regardless of what those conclusions were.

You asked for responses to your study taken at face value, without regard to external issues such as what live witnesses saw or whether the live-composite conjecture is a priori plausible. So, there it is. Do you have a response?

Ideally, I'd like to see you continue your study and correct these problems with your control. You've been honest about presenting your methods so far, which is what makes this criticism possible at all, so perhaps you might be willing to carry it through to a conclusive result, regardless of what that result might be.

You cannot correct every possible source of error -- for instance, the speed of the planes will inevitably be different, and there's little recourse.* That's one reason why no single scientific study is ever completely conclusive. But you can and should at least address those factors for which plausible explanations of how they could contribute to error in the findings have already been presented, such as I did in my previous post.

Each of the three issues listed above is potentially fixable, at least in large part. For #1, you're clearly not going to find a flight path that coincides with a building at exactly the same distance (that is, that crashes into the building), but many airports have commercial strips of hotels and convention centers that are within a mile or two of a runway, where you should be able to find a viewpoint where the building is at least 2/3 the distance to the plane instead of prominently in the near foreground. Even better if you can use a service building, enclosed tower, etc. that's on the airfield itself.* For #2, just compress the control video using the same algorithm as the 9/11 footage you're using, or get someone else to do it for you. For #3, get some volunteers and have them perform the procedure of locating the plane's outline in the frame, on individual randomized frames in which the identifying features of the 9/11 versus the control footage have been cropped off or blanked out. The logistical details of this might be tricky, but it can be done. As a bonus, you'll have data that shows the variation in assessments by different people. You can even give the same frame to each assessor more than once, so you'll have data on how consistent those assessments are.

*With jetliner/airport footage you'll never be able to get the pixel size and pixel speed to both be comparable to the 9/11 shot, because jetliners are not flown that speed near the ground normally. But here's a suggestion for how to model those same pixel sizes and speeds using a different scale: consider using footage of planes taking off or landing on aircraft carriers. If you can find footage from the right distance, you should be able to get the pixel size of the plane in the image and the pixel speed of the plane across the frame to both be comparable with the 9/11 footage, even though the plane's actual size and speed will be smaller and lower. Then you can use the carrier's island superstructure, which is necessarily very close to the flight path, as your "building" position.

Respectfully,
Myriad
 
Personally, I like the turn the truth movement has taken into the dead end of "video fakery".

While a lot easier to fool the uninformed of the possibility that WTC-7 was intentionally demolished, and even to some extent that no plane hit the Pentagon, I am confident that the average person on the street is not going to buy that no planes hit the twin towers.

So keep on truckin Ace.
 
T
. . .a technologically infeasible theory (a system that can carry out real-time overlays of videos on to a live feed . . .

Dave


False. Sophisticated real time video overlay was operational since 1998 at least. You know it. I know it. When you resort to such falsehoods, it only emboldens us, and weakens your credibility.
 
False. Sophisticated real time video overlay was operational since 1998 at least. You know it. I know it. When you resort to such falsehoods, it only emboldens us, and weakens your credibility.

Yet you are unable to provide evidence for your claim that the level of sophistication was great enough that it can be responsible for your stupid theory.

So, "when you resort to such falsehoods, it only emboldens us, and weakens your [nonexistent] credibility"...
 

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