9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Nigel Roles" <nigel@9fs.org>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: RE: [9fans] A prick into the wasps' nest ;-)
Date: Thu, 10 Jun 2004 06:45:10 +0100	[thread overview]
Message-ID: <HOEHIDJJJINMLFPOLFJCMEJGDFAA.nigel@9fs.org> (raw)
In-Reply-To: <058e01c44e9a$93e22ce0$9b7f7d50@SOMA>

> factors involved.  if we assume that TV is 26 (iirc) frames/second
> there is phosphor persistance on the the screen (let's forget about
> LCD's) and (iirc) there's retinal persistance.  so, dropping a
> few frames  doesn't really matter.  oh yeah, it's interleaved as well.
> 
> they may not even be watching when the frames are dropped.
> 

Even if I softly drop a few words here and there, this is still
recognisably rubbish.

The frame rate is 25Hz for PAL, or 30Hz for NTSC (29.97 for pedants).
SECAM is also 25 Hz.

There is some persistance (sic), but the human eye/brain
is extremely sensitive to missing frames, or disturbed frame timing,
so it is arguable that persistence makes a timing error worse.
You only have to watch a someone walk across the shot on a decent
DVD player and then compare it will your typical soft decoder on
a Windows laptop to know that seeing all the fields at the right
time is a really important.

Interleaving only helps reduce apparent flicker. Each field represents
a different point in time, so missing a field, or replacing one
with a copy of the previous one is ruinous. Swap the fields and
everything looks furry. 100Hz TVs don't just
display each field twice; they have a DSP in there to
sort out the motion compensation and synthesise the missing fields.
My 100Hz TV still screws up on fast scrolling credits (horizontal
and vertical).

Stick to what you know, Boyd.
Except the guns; it's really, really tedious.



  reply	other threads:[~2004-06-10  5:45 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040609125113.UCQG24541.imf23aec.mail.bellsouth.net@Xaplos>
     [not found] ` <4fa4328626f76766f4799367fc0550c7@vitanuova.com>
2004-06-09 18:41   ` boyd, rounin
2004-06-10  8:16   ` vdharani
2004-06-10  3:25     ` boyd, rounin
2004-06-10  5:45       ` Nigel Roles [this message]
2004-06-10  9:20         ` Steve Simon
2004-06-10  9:20         ` Bruce Ellis
2004-06-10 14:55         ` boyd, rounin
2004-06-10  9:43 Andrew Simmons
2004-06-10 10:36 ` Nigel Roles
     [not found] <40C6C916.5080004@chunder.com>
2004-06-09 15:04 ` Mark F Rodriguez
2004-06-09 16:04   ` Bruce Ellis
2004-06-09 16:08     ` rog
2004-06-09 16:11       ` Bruce Ellis
2004-06-09 18:54   ` boyd, rounin
  -- strict thread matches above, loose matches on Subject: below --
2004-06-08  6:51 cej
2004-06-08  8:17 ` Vladimir Los
2004-06-09 23:10   ` kim kubik
2004-06-09 23:22     ` boyd, rounin
2004-06-09 23:40       ` George Michaelson
2004-06-09 23:41         ` boyd, rounin
2004-06-09 23:41       ` andrey mirtchovski
2004-06-09 23:44         ` boyd, rounin
2004-06-09 23:55           ` Geoff Collyer
2004-06-09 23:27     ` rog
2004-06-10  8:03     ` Vladimir Los
2004-06-07  7:09 cej
2004-06-07 15:53 ` Rob Pike
2004-06-08  7:32   ` Vladimir Los
2004-06-08 18:18     ` Sape Mullender
2004-06-08 18:55       ` Mark F Rodriguez
2004-06-08 18:58         ` William Josephson
2004-06-08 19:05         ` rog
2004-06-08 19:39           ` Mark F Rodriguez
2004-06-08 20:50             ` boyd, rounin
     [not found]     ` <40C6C6E8.1000302@chunder.com>
2004-06-20 22:35       ` vdharani

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=HOEHIDJJJINMLFPOLFJCMEJGDFAA.nigel@9fs.org \
    --to=nigel@9fs.org \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).