It's true that based on the bug report linked in the post, the application bundle is modified by a 3rd party installer running as root. I still think Chrome should correctly handle the permissions problem with a warning or asking for root privileges to fix it, but I've updated the post to point out Chrome itself is not the origin of the problem.
Hadn't thought of that! And considering that based on what I calculated in the post he goes off the edge at about 70mph, he probably needs way less that 258 feet right?
The 70mph is horizontal velocity, gravity is vertical acceleration from 0. Total velocity is sqrt(sum of squares). It's unclear how much horizontal velocity the train would lose due to air resistance and due to the unclean launch from the ravine. (Would it fly off the end of the track, or tip off the end and tumble down?)
You're probably right it's not all real time. I figured it wasn't completely unreasonable to treat it as such because when you watch it, most of it does feel RT and we pretty much see everything that happens in an uninterrupted way.
But for the sake of argument, even if the analysis is skewed a bit, it does suggests they were missing a lot of tracks. So if some of the sequence can be considered RT and some of it not, for them to reach the 88 mph in under 3 miles, probably a lot of it would need to be non-RT, which didn't feel right to me based on the way it's presented in the movie.
Totally agree it would be awesome to be able to figure out what overlaps. Thanks for the comment!
;)
A classic example that exaggerates the different passing of time of movie vs real time happens in Monty Python and the Holy Grail: https://youtu.be/DPXG4pdPj4w?t=20s
Went to school for video/film production and time compression was the subject of a couple of fun projects. In TV and movies, you rarely see things in "real time" unless it's specifically done for an effect (like the gimmick of "24" or to create some level of tension).
Normally, you compress time to a greater or lesser degree because you just don't need to see every single action that someone takes in the course of a given hour or event. Like you point out in the Python clip, you wouldn't normally shoot the entirety of a guy running across a long field. You'd show him start running, cut to a closer shot with him making progress, cut to the person/place he's running toward for reaction or to re-establish the destination, and then cut back to the guy as he's getting there.
When you drag these kinds of things out, it can be a good gag because it's almost like a bad storyteller who includes every irrelevant detail. It makes us uncomfortable and throws off timing. In a more tense scene, time is often screwy because maybe you want to drag things out and show all of the characters' reactions to create anxiety and the feeling that "they'll never make it".
Anyway, thanks for the reminder about the Python bit. Always makes me smile :)
This is also something used in fight scenes, where a person will say, throw a punch, then the camera angle shifts, and the person will be seen to throw the punch again - "The Asian Cut" [0]
Mac Mini is hooked up to speakers and TV and it plays the goal song. I set the volume of the media player so that it's just right with the game broadcast so everything sounds good together.
lol well it does go off erroneously sometimes... statistically speaking once every 4 games. BUT... I do have the big USB button ready to cancel the light show and goal song. Something I did not mention in the blog post is that it stops the goal song by playing the Fail Trombone sound (https://www.youtube.com/watch?v=iMpXAknykeg) when you use the USB button to cancel light show. Yes really disheartening, but the one time it happened it made the whole thing pretty funny actually :)
Not a bad idea. However it would probably be hard to make the difference between goals for and against your team without analyzing a lot of what's said prior to a goal.
The model is really specific to the station and commentator. I've trained it on games from a local Montreal station. I tried the other local station with the same model and the it detected no goals at all. So to make it work on any other station, we'd need to rebuild a dataset from scratch.
