i'd like this debunked

Gumboot - if you're reading.... Is it correct to refer to video in terms of "frames"? (Not sure it means anything - I'm just curious, and unable to find anything in a quick search that doesn't require me reading forty books.)
 
Gumboot - if you're reading.... Is it correct to refer to video in terms of "frames"? (Not sure it means anything - I'm just curious, and unable to find anything in a quick search that doesn't require me reading forty books.)


It can be. Interlaced video is actually fields, not frames. NTSC is actually 59.94 fields per second. PAL is 50 fields per second. An interlaced television or camera scans every second line, making one field, then goes back and scans the other lines, forming a second field.

However it is pretty common to refer to "frames" (treated as 2 fields), so although it can be technically incorrect, it is usually accepted. While the camera will be capturing the images as separate fields, the recording device is most likely recording both fields together.

-Gumboot
 
no the same sort of time changes do NOT occur throughout the video. yes there is a fluctuation in the appearance of the time stamp when run at normal speed. slow it down and you will see every second count off, one by one. it will require you to go frame by frame, however the average rate is as it should be 2 frames of analog video to every 30 frames of digital video at a rate of 30fps. go back and read what it is i am saying. everywhere in the video the rate of movement for every single moving object in this video is approx 1 step of movement every 15 frames, as one would expect them to be. the only exception to this is during the 12.5 seconds in question and in that segment the man remains in a movement stance for 121 frames, as the time stamp continues, for 4 seconds. the time stamp comes from the analog video. as does the video of the man. the ONLY way that the time stamp can continue to count off seconds and that man not move, though in a moving pose for 121 frames is if the video has been digitally altered or physically editing by cutting and splicing the film.

and the camera does not oscillate at the same rate during the segment im questioning. the oscilation is at a rate of 1 complete up/down cycle in 395 frames. everywhere else it completes one up/down cycle every 30 frames.

again i insist you go through the piece frame by frame, otherwise you're ignoring the evidence and making conclusions based on pure conjecture.

Well if you just play the tape and watch the time stamp you see it changing back and forth. If you have gone through this tape frame by frame how can you not notice it when it's evident just by playing the tape?

Again the tape freezes on many occasions and there's is nothing special on the moments after the impact. The time the running man is frozen is not unusually long. There are other times the tape freezes even longer (for example around timestamp 9:50:30) How could you mis that if you meticulously went through the tape frame by frame?
This tape is 899 seconds, that times 29,97 would make 26943,03 frames. Did you really go through all of them manually, almost 27000 frames. Mayby you payed closer attention to the moments after the impact and missed all the other times the time stamp changes and the movements of the people freeze.

I'm just asking questions.

rolleyes
 
Last edited:
the ONLY way that the time stamp can continue to count off seconds and that man not move, though in a moving pose for 121 frames is if the video has been digitally altered or physically editing by cutting and splicing the film.

The video of the man comes from the CAMERA and the timecode comes from the recording device.

If the images are not moving, but the timecode continues to count, that means the signal from the camera to the recorder has had a glitch.

It's an error in the CCD, nothing more.

And by the way, given this is video it cannot be "physically edited by cutting and splicing the film".

Maybe w_bender has read one too many conspiracy sites about the Zapruder film.
 

Back
Top Bottom