Search results

Using the slightly better quality version here, I converted it to real-time 30fps (29.97) The question that the promoters like Marik are holding out on is if the panning continues during the "fly-off". It's a little hard to see with all the noise, so I added a blur sufficient that the pixel...

Well, this is annoying. I've only just noticed that the version I was working on is actually a cropped and degraded version. The YouTube video starts out with 1m24s of the object first flying (apparent) left (west), and then right (east). It's rock solid, which should have been suspocious for...

It happens in other places, that one's just the greatest.

To expand on that: You get dark regions when recording from a CRT (an older Cathode Ray Tube TV), because the picture is built up from top to bottom. So if your exposure is not a multiple of the frame time of the TV (like 1/60, 1/30) then you get something like 1.5 frames at full brightness...

Same reason the word "ACFT" shrinks, it's a localized change in gain that happened AFTER the actual recording. So basically, in the camera of the person recording it off the screen. For unknown reasons, but maybe from recording off a CRT. Which might mean the "cold glare" image expansion...

Both boxes are essentially the same size, in that they describe 5m horizontally on the ground. At ULTN (Ultra narrow, the maximum optical zoom), we see a smaller object relative to the box. If we take the 4x version and shrink it down 4x, we see the box encloses the same area, and the object...

Another key point is that what we see seems to be a kind of glare. Kind of unusual from a cold object, but did the object really change size? Both boxes are 5m wide.

I think it really can just be boiled down to the fact that the "fly-off", which looks like a camera motion, coincides exactly with a change in camera modes. This is unlikely to be a coincidence, given the alternative is breaking the laws of physics. Occam goes with camera motion. Arguments...

Or essentially infinite acceleration. Which would certainly break the laws of physics, as we know them. Of course, what they really mean is a very rapid acceleration, something that reaches significantly velocity in a fraction of a second, less than a single frame of a video, so it seems...

I now use a 3D illuminated model of the Moon to accurately display the phase. I also added a "Celestial Lock" to the Camera -> Camera Heading, to let you lock the camera to point at a particular celestial body.

Here I've added two straight line, constant speed traversals https://www.metabunk.org/sitrec/?custom=https://sitrec.s3.us-west-2.amazonaws.com/1/Syria Source: https://www.youtube.com/watch?v=2y91EufUNTc The Magenta one is descending, the cyan one is ascending, they both stay reasonably...

It might be something as simple as the balloon hitting an updraft

In that situation, we were able to very precisely align the LOS through the object with a very detailed background. Just using the pure numbers on screen gave pretty much a random walk. It was a very fiddly manual process, and slight deviations made the solution explode. But the end result had...

When they switch out of 4x to 2x they immediately pan right about 1.2 screens wide. It would be lost in the initial motion blur, and then off screen, even in ULTN

No. These are not particularly accurate numbers. I would not expect a perfect path to pop out. If the object was going screen-up before, why would it not continue after the lock was lost? I think it's very difficult to determine what is going on with the local contrast adjustments that seem to...

This older starlink tutorial will probably be updated eventually Source: https://www.youtube.com/watch?v=WkzRJQ3rWa0 There's a help docuement built-in to Sitrec (Help/Documentation) https://www.metabunk.org/sitrec/docs/Starlink.html

Some of these are a bit older, but still useful Source: https://www.youtube.com/watch?v=F6IiVwVLoYc Source: https://www.youtube.com/watch?v=jbybIhk5Pig

Source: https://www.youtube.com/watch?v=slA7aV2Mags I've started a series of tutorial videos to get people more quickly up to speed with using Sitrec. The above one on the user Interface should be the starting point (even if you've used Sitrec before, there's several useful features) Source...

The entire video has likely been through several stages of re-recording, maybe on different systems. But the timecode does seem particularly bad. It goes from 18:21:06 to 18:22:21 (1m 15 sec) over the course of the video, about the right length. But it skips over seconds, displaying 18:21:06...

To duplicate the above, drag in the video first, and then the drone and ground tracks. Then set the camera track to the drone and "follow target" I've updated the MQ9 UI to display more of what we see...