posted on Nov, 1 2013 @ 07:44 AM
reply to post by onehuman
Before I read your post I picked that too.
I don't go with the bug theory either.
As I mentioned before, the reason the object appears in two frames simultaneously could be the result of "video interlacing".
Video interlacing is a video compression method in which information is borrowed from one frame to the next. The idea for this being that if pixels
don't change from one frame to the next (say, for example, because of a non-changing background) not all of the pixel information for every
needs to be kept uniquely in the file memory. Instead, if the video software in the device that created or saved the video file senses that
certain background pixels have not changed from one frame to the next, there fore it does not need to remember each pixel in every frame uniquely; it
just says "for that pixel, use this information I already have in memory"
, thus saving file space, and making the file smaller. It also makes
the video run more smoothly, because each frame can load much faster, letting the video buffer ahead faster -- i.e., faster than the playback
So that's what video interlacing is (in a nutshell)...
...but how could that potentially result in frames where the object can be seen twice in the same frame? Well, video interlacing is not always
perfect. Sometimes the device doing the file creation/file saving makes mistakes. Sometimes information/pixels that are unique to two different
frames is read as being the same/unchanging in those two different frames (sometime because of fast motion). Therefore, the information from one
frame (say the pixels of the object) can be interlaced on top of the information of the next frame, thus creating frames where the object appears
To me, this actually makes me think the object was really there (possibly a bug close to the camera, possibly something else). If it was CGI, then I
think there would be less of a chance of the image appearing twice on the same frame. There is less of a chance for the video interlacing algorithm
to read a CGI-added object as pixel information that could be interlaced.
edit on 11/1/2013 by Soylent Green Is People because: (no reason