https://www.youtube.com/watch?v=z6i1VVikRu0
This video claims that TBS is currently increasing the speed of Seinfeld episodes a whopping 9%, reducing a 25 minute episode to some 22.5 minutes.
Technology can work in your favor too!
Speed up: ] key Speed down: [ key Normal speed: = key
Also, some youtubers speak way too fast. Slowing them down helps comprehension a lot, I find.
http://www.cinemablend.com/new/Message-From-Stanley-Kubrick-...
Though, I can now instantly tell if I'm watching a PAL or NTSC version of Star Trek TNG based on the the first few bars of the opening song.
Which is weird, because I don't even have pitch perfect hearing and I'm not even that musically inclined.
I was actually thinking about a similar but less subtle example: I use a transit system that involves tagging on and off with an RFID card (Clipper on Caltrain). When you tag your card, it makes one of three different noises depending on what happen—and I couldn't possibly tell you which one corresponds to what. But if I'm actually using it and I make a mistake, I notice immediately because I'm so acclimated to the pattern it normally makes!
If I hadn't realized this, the UI for the system would have looked absolutely terrible. The different beeps are the auditory equivalent of "mystery meat navigation" but even worse because they don't carry any semantic meaning at all. But because I always use the system in the same way and the noises were consistent, it actually works really well even if I never consciously learned what noise corresponds to what.
(The fact that there are wrong ways to use the system is bad design, but it's a function of how the whole train system is set up, not the fault of Clipper's designers.)
I'd be really interested to read anything more concrete about audio affordances though, if anyone knows of links to further research, etc!
A fantastic book on how these are all related is "metaphors we live by". I'd expand on this but I'm typing on mobile and on a hurry. But seriously: read the book. It takes a long afternoon. It's great, short, illuminating, and not excessively dense or padded.
* One beep - successfully paid fare
* Two beeps (different) - successfully paid fare, and you're about to run out of money on your card
* Two beeps (equal) - tagged off (e.g. on Caltrain or San Francisco Bay Ferry)
* Three beeps - read error or insufficient value
There might be others. Indeed, they've introduced a quieter "here is a Clipper reader" beep to help visually impaired people locate them: https://vimeo.com/183916243
[1] e.g. http://www.sciencedirect.com/science/article/pii/S0010027715...
And in cinema they were better (I seem to remember Geoffrey Rush 'playing' Rachmaninov 3rd Piano Concerto in that film, at excellent pitch in the cinema), so I knew they were sometimes right. But i think the tape, TV and DVD formats I'll have rewound most often in perplexity.
Another confounding: living in California a lot and not having incorrect pitch on local copies. And nowadays, when sources are digital, bit may have originated from analogue recordings, it's now very unclear what to expect.
No. For NTSC they just drop (throw away) 1 frame from every 1000 frames, so there's no speed-up or speed-down in audio track.
https://www.lynda.com/Pro-Tools-tutorials/Understanding-vide...
Let's say you have 100 seconds of film material with corresponding audio duration. That would be exactly 2400 frames, because film is 24 fps. When you do 2:3 pulldown (that's one of the methods used to do telecine, i.e. film conversion to television format) you'll get back exactly 3000 video frames. But in NTSC format, (if you'll leave audio untouched, i.e. it's duration didn't change, it's still is 100 seconds) for 100 seconds of video duration you must display 2997 video frames, not 3000. So you just throw away 1 frame from every 1000 frames to get the exact 29.97 fps.
Doing this, at worst case you'll get audio/video desynchronization of 33 ms, which I don't think is noticeable (I tend to visually notice desynchronization when it's at about 100 ms or more). But if you'll drop that 1 excessive frame in the middle (not at the end) of the sequence of 1000 frames, you'll get audio/video desynchronization which only varies from -16 ms to +16 ms. Which is not worth the trouble of fixing this by going the other way around it: leaving video untouched and slowing down the audio by 0.1%.
A friend of mine bought the DVD of 'Rent' when it first came out in our region. A month or two after it came out, the DVD got re-issued because it's a musical, and people had been complaining that the conversion had been messed up. I think she got the re-release for free.
Yup. Another example: in most of the world (where the television system is PAL or SECAM) movies are played on TV or released on DVD at 25 frame per second. But to achieve this frame rate, they take the theatrical film release at 24 fps and speed the video and audio up by 25/24th (4.17%). Of course almost nobody knows this because nobody notices it. https://en.wikipedia.org/wiki/576i#PAL_speed-up
For NTSC, the film release is sped down by a much smaller amount (0.1%) during the 3:2 pulldown to adjust from 30 to the exact 29.97 fps that NTSC needs.