From: Hal Murray <halmurray+bufferbloat@sonic.net>
To: "Network Neutrality is back! Let´s make the technical aspects
heard this time!" <nnagain@lists.bufferbloat.net>
Subject: Re: [NNagain] Fwd: separable processes for live in-person and live zoom-like faces
Date: Fri, 17 Nov 2023 11:14:01 -0800 [thread overview]
Message-ID: <20231117191401.A6BE128C20C@107-137-68-211.lightspeed.sntcca.sbcglobal.net> (raw)
In-Reply-To: Message from rjmcmahon via Nnagain <nnagain@lists.bufferbloat.net> of "Fri, 17 Nov 2023 09:27:56 -0800." <965f84c27d3d7c00ebcbaae5382234cd@rjmcmahon.com>
rjmcmahon said:
> The human brain is way too complicated to make simplified analysis like this
> is the latency required. It's a vast prediction machine and much, much more.
I agree that the brain is very complex, but it isn't a total mystery. We can
measure some things and work out some timing requirements.
Examples:
Movies/TV have a minimum frame rate to avoid flicker.
Phone systems have a max round trip latency.
(I think back in the days of satellites, they decided that one sat link was OK
but 2 was too long.)
You can measure the time to push a button after a light goes on.
That's tangled up with hand/eye coordination for catching a ball or using a
mouse.
I get (slightly) annoyed by the delay when news shows switch to a (very)
remote reporter.
I see no reason why a latency requirement couldn't be worked out for something
like a Zoom meeting.
--
These are my opinions. I hate spam.
prev parent reply other threads:[~2023-11-17 19:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-16 21:57 [NNagain] " Dave Taht
2023-11-17 14:16 ` Hirsch, Joy
[not found] ` <AD77204F-4839-4292-976D-E7BE11A12C9B@gmx.de>
2023-11-17 14:18 ` [NNagain] Fwd: " Dave Taht
2023-11-17 17:27 ` rjmcmahon
2023-11-17 18:57 ` [NNagain] " Sebastian Moeller
2023-11-17 19:14 ` Hal Murray [this message]
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
List information: https://lists.bufferbloat.net/postorius/lists/nnagain.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231117191401.A6BE128C20C@107-137-68-211.lightspeed.sntcca.sbcglobal.net \
--to=halmurray+bufferbloat@sonic.net \
--cc=nnagain@lists.bufferbloat.net \
/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