From: David Lang <david@lang.hm>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: Colin_Higbie <CHigbie1@Higbie.name>,
"starlink@lists.bufferbloat.net"
<starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] 300ms Telecommunication Latency and FTL Communication
Date: Fri, 7 Jun 2024 07:55:54 -0700 (PDT) [thread overview]
Message-ID: <n08pn9sp-00q2-2s7p-2r26-nr76o8oqn9q3@ynat.uz> (raw)
In-Reply-To: <61FA5621-4E64-4CB3-81BA-04D568939E68@gmx.de>
Sebastian Moeller wrote:
>> video conferencing is more sensitive to latency than pure voice (in my personal opinion, no study I've read on this specifically), because we watch people's faces for reactions to what we say as we're speaking.
>
> [SM] I am happy to believe you on this, but ti turn this into something useful for my purpose I will need to find something published, preferably peer reviewed. But thanks to the pointer which should help in my search.
one factor to point out, almost all video conferencing is you to server to other
user, not direct you to other user. If you have two people in the same house on
a call together, they suffer double the latency.
>> If there is a noticeable lag there, it disrupts the conversation. On the other hand, the same lag in a pure voice discussion, which is inherently less synchronous, would not be noticeable.
>
> [SM] Not sure I fully agree here, assuming video and audio arrive both with
> the same delay I would guess both suffer similarly from the delay... my gut
> feeling is as long as natural speech sequence stays intact, that is no
> unintended collisions due to both speaking at the same time, audio-only and
> audio-video should both be sort of OK...
the longer the latency, the more likely people are to talk over each other,
because they don't see/hear the other person talking when they start. If the
latency is low, they can stop quickly, but as the latency increases, they are
talking longer before they hear the other person.
1. this means it's harder to figure out who started first and should continue
2. this means that there is a longer time period of multiple people talking
I agree that this is the same video vs audio. That's why I was thinking back to
the early AT&T research I've heard from Internet lore (back when AT&T had a huge
R&D section). It may be useful to look not only for long distance info
(including microwave relays vs direct cables vs satellite relays) but also if
they have any research on early conference calling.
David Lang
next prev parent reply other threads:[~2024-06-07 14:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.3171.1717601612.1074.starlink@lists.bufferbloat.net>
2024-06-05 17:58 ` Colin_Higbie
2024-06-06 7:22 ` Sebastian Moeller
2024-06-06 13:43 ` Colin_Higbie
2024-06-07 14:07 ` Sebastian Moeller
2024-06-07 14:55 ` David Lang [this message]
2024-06-07 15:32 ` Sebastian Moeller
2024-06-07 16:46 ` Colin_Higbie
2024-06-07 16:56 ` David Lang
2024-06-07 17:00 ` Colin_Higbie
2024-06-07 17:34 ` Michael Richardson
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/starlink.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=n08pn9sp-00q2-2s7p-2r26-nr76o8oqn9q3@ynat.uz \
--to=david@lang.hm \
--cc=CHigbie1@Higbie.name \
--cc=moeller0@gmx.de \
--cc=starlink@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