(no title)
ddcarnage | 10 years ago
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!
ant6n|10 years ago
soylentcola|10 years ago
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 :)
FrankenPC|10 years ago