Las Vegas Shooting Timeline Eye Witness Videos & Police Scanner sync скачать в хорошем качестве

Las Vegas Shooting Timeline Eye Witness Videos & Police Scanner sync

This video demonstrates the sequence of events regarding the Oct. 1 Las Vegas Shooting by painstakingly syncing video footage of bullet fire taken from eyewitness cell phone footage, surveillance footage, and police body cams that night. Thus illustrating, with certainty, when the first shots were fired, and exactly when the zebra 20 team breached RM 32-135 inside Mandalay Bay. The first shot was fired at 22:05:29 PDT *ALL CREDIT GOES TO THE ORIGINAL ANON WHO POSTED THIS RESEARCH* He states: "The time format for the Video Time Code (the clock on the bottom left, not the PDT on the bottom right) is hh:mm:ss:[frame #0-30] (so then, 01:02:03:04 would be the 4th frame of the 3rd second of the 2nd minute of the 1st hour). There are 30 frames of every video for every second on every clock. It's beautiful ffs. Note: only the security camera footage (among the clocked) lacks this complete fps precision throughout - that is: in a very few sections (maybe 6) of the new b&w video (which runs the length of, and beyond, this video), a single second of video may have only 29 frames - or even 28 - right at the cusp of the next second. This isn't used AT ALL for timestamping, but shows sufficient continuity (imo) for inclusion here, for comparison against all the other syncs. It always matches at sync points perfectly, of course, and any of the aformentioned surplus frames are allowed for at the next edit/sync point. Sounds way more complicated than it is - but it is difficult. And I see now I missed at least one dropped frame - so probably as many as 6. The Bleacher Vid - contributing to neither timing nor video interest - was replaced with a far better one at 00:03:48:28 ("Catwalk Stage Left" my term), source as pic related I have included a "Bright Lights" vid (again, my naming), to reflect the salient radio traffic. Seen and heard together, they may open a new angle for consideration of the light visible a third of the way up the north tower. 00:09:00:27 source pic related I used all the police videos. Their clocks were all the same amount of incorrect, so they shared an offset, and then sync'd up perfectly. So well, in fact, that at 00:09:37:15, you can hear the shots and voices captured on the Axxon camera, and from the dispatch radio recording, and coming thru the individual police radios - all at the same as the officers themselves are hearing it. Cool sync. It's one of the radios illustrated at the sync points ...... The clocks on the cops don't verify the time in any way, incidentally - they only corraborate the overall syncrony of the event continuity, ifyouseewhatImean. It would have been very, very difficult to fake this sync point, as captured and shown. All of these Axxon vids are sourced as a single file, as they were released. The webm compression took 36 hours, and my machine is made from magic. The final 2pass 4:4:4 12bit at 1456 (targetting 1GB) is, however, beautiful, codec wise. You can easily read every little digit on every little clock. The audio is normalized (but loud), and the only mixing was to avoid clipping. The audio on the final "flipper" vid (as indicated and labelled, in vid) has been turned down. This is due to a roughly 500ms consistent shift in this audio over the length of the section that was disturbing. Therefore, it is only easily audible during the actual breach. Finally: the time. The Taxi Driver meter clock (changing during the 6 seconds you've seen before) is the one that fits with the breach time of 23:19:55 PDT. I started at the official 23:20, but this is the one that fits. It also fits the other time syncs, such as the truck dashboard clock & the tweet time (23:25:09 pm). It could be scooted by only a few seconds (3?), either way. And every other single frame would also have to shift and still fit. I believe this to be the accurate time, as shown in the video. I have the 1st shot at 22:05:29 PDT, and all the other clocks are correct. Apologies for length."