This is an automated archive made by the Lemmit Bot.
The original was posted on /r/ufos by /u/Aeylwar on 2024-12-19 23:38:00+00:00.
Edit: Broken links fixed, added fourth sighting to case 12 Edited my closing statement
*I will not start this post with a statement, I will end it with one. All links to previous work, posts, and references will be at the bottom, neatly organized chronologically.
IMGUR LINKS CONTAIN MULTIPLE PICTURES, PLEASE SCROLL DOWN.
ALL VIDEOS AND PICTURES PROVIDED HAVE TIMESTAMPS INCLUDED AT THE BOTTOM NEAR THE SCROLL WHEEL.
TIMESTAMP LEGEND IS AS FOLLOWS: mm.SS.CF this represents: minutes:Seconds.CurrentFrame
The videos are frame by frame. Feel free to pause the video where you need to, the bottom of the video will have what frame you’re on, listed along with the minute and second of the video you’re on.
Case [14] is towards the bottom of the post. I absolutely suggest you read this whole post before you get there.
Context is very important.
As always, thank you for your time.
. . .
Many of you have read along with my previous breakdowns of videos—thank you. I appreciate your time.
I encourage you to take some time out of your day, assess my findings, come to your own conclusions with my work— And let me know why I’m wrong in the end.
Everybody is suddenly an Airplane, Helicopter, Jet, and Star engineer/expert. I’m making my own claim here, and I’m backing it up.
Your beliefs don’t matter here, your opinion does. Read through my post and form one, share it at the end of your reading
. . .
I’m going to start by bringing attention to Case [12] [ ] as it was considered my weakest link, and I will provide context for it.
The person that provided this video was actively recording the sky in 240FPS HD video during a “hysteria” craze last year.
Why was he recording the sky?— you might ask yourself.
Him and his best friend found an Instagram account that they were intrigued by— a guy that explained how to capture these things that were in the sky. He said that you couldn’t get film with 30-60 fps *consistently*.
User testimony:
This is the podcast link:
They have many more recordings but have not gone public for stigma issues. In this next recording they thought they found one thing.
THIS WAS NOT THE CASE.
The following is 240FPS Not zoomed in, HD Slow motion footage.
Original file I received from the person that recorded it:
This is what OP thought he caught and sent me to review:
And so instead of just looking at what he sent me and thought that he caught— I downloaded the video and looked through every single frame and looked for inconsistencies and differences in pixels.
Here are my findings. I’ll name them with numbers representing which frames are included in the video. I will first post the full video in slow motion at full video scale, and then afterwards I will post a zoomed in clip highlighting my finding. At the end of the zoomed out clip, the video zooms into where the next clip will be.
I hope you take it as a challenge to spot the orb in slow mo before you continue to the second zoomed in clip.
The next videos are shown in the following format: First half of the video is forwards in time, and when the orb is lost from sight at the middle of the video— *At which point I rewind the video, frame by frame, until it reaches the point the orb was introduced to us.
This will be chronological to original video.
First instance in video. **00:02.88–00:02.151:
Zoomed in:
Second instance in video. **00:04.20–00:05.30
Zoomed in:
Third instance in video. **00:09.21–00:09.197
Zoomed in:
Fourth instance in video. **00:12.03–00:12.22
Zoomed in:
I will use Case [12] to further strengthen my previous findings. The following is my observation and claim.
In trying to film what they believe to be drones, many people are filming actual airplanes, drones, and helicopters— This creates video recordings of the sky. The video settings usually provide 30FPS, at night— Blurry images and videos. A lot of it is unusable.
But if you comb through the posts to find ones that are interesting, and then take the time to look deeper than 10 seconds, you’re gonna find some crazy shit.
It is a fact that Case [12] is recorded in 240FPS.
The next video I will show you, from this point forward will be known as Case [14]. This video is low-res zoomed in in some points of the video. It is 6 minutes long. It contains a lot of image noise, but it’s very easy to tell when it happens because of zoom.
Case [14] contains 10,800 total frames.
Case [12] contains 86,400 total frames.
The orbs visible in Case [12] at 240FPS are only visible for .25 seconds at best
Meaning then— The orbs fully crossed the whole screen, in a quarter of a second, 4 times in the video for a total screen time of 1 second. You just watched 8 total minutes of video in Case [12] which represent 1 total second of screen time for the orbs.
I do not have the original video, I’ve contacted the OP but they do not respond, I’m sure they’re flooded with comments.
It is a fact that in Case [14] we are missing 210 frames per second of recording as compared to Case [12]. This is important to keep in mind for what you’re about to see next:
Case [14]
This is the original poster [6 minute video]:
This is the post that got my attention [6 minute video]:
Keeping everything in mind that I’ve explained about frames missing from the video, take a look at my findings.
The next series of videos are frame by frame play throughs. The frame you’re watching is labeled at the bottom of the video near the scroll bar. The time legend is as follows: mm:SS:CF which means minute:Second.CurrentFrame. Take your time, pause the video where you need to and take your time observing what I observe.
The next link is two images, one frame apart. Take a look and scroll down:
This is the same thing zoomed in, again, the same two pictures:
With the above two images above, I want you to watch the next clip. It is imperative that you watch the next clip while understanding everything we’ve talked about at this point in my post. Framerate difference of the videos, how Case [12] provider filmed specifically during the day and with conditions that would provide contrast of a Dark Object against a white background, and specifically the speed of these orbs. They cross the screen in one quarter of a second. 00:00:25. 0.25.
Again, the next video is shot at 30FPS. Every frame in the next video, again, is .05 seconds of time allotted. In Case [12] if recorded at 30 Frames Per Second, we would see only 8 frames of the orb. The effect this causes is— instead of an orb smoothly gliding over the screen, we will see what its movements are while missing out on 8 frames in between for every perceived frame, giving the impression of it skipping, or instantly appearing on screen, or instantly leaving the screen, jumping in between orbs, interacting so fast that all we see are the colors change, or as a blur of movement.
02:08.21–02:13.10
After watching the previous one, the next one has some context.
01:21.05–01:30.08
Watch these all the way through, pause if you have to, replay it if you didn’t see anything.
02:44.03–02:45.12
02.47.30–02:51.02
02:39.20–02:45.20
highlight from previous video:
Im now going to file dump important interactions I found, chronologically relative to the original 6 minute video.
. . .
Understand for these videos, This is recorded in 30fps. Whatever orbs you see that are dashing, we are missing 14 frames between each movement.
01:21.05–1:30.08
2:07.25–02:09.24
03:22.12–03:25.28
03:28.03–03:32.20
03:36.11–03:42.28
03:45.10–03:49.10
03:50.08–3:53.21...
Content cut off. Read original on https://old.reddit.com/r/UFOs/comments/1hi6f4c/we_have_to_talk_about_this_as_a_community_i_dont/