From: Kenneth Porter <shiva@sewingwitch.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Bufferbloat glossary
Date: Sun, 29 Mar 2020 14:08:38 -0700 [thread overview]
Message-ID: <8236FA89207AF4F3FB62291A@[172.27.17.193]> (raw)
In-Reply-To: <705E8BC2-13ED-47CC-AAF6-1BB9F7E37107@gmail.com>
--On Sunday, March 29, 2020 10:23 PM +0300 Jonathan Morton
<chromatix99@gmail.com> wrote:
> I think the main distinction between online gaming and teleconferencing
> is the volume of data involved. Games demand low latency, but also
> usually aren't throwing megabytes of data across the network at a time,
> just little bundles of game state updates telling the server what actions
> the player is taking, and telling the player's computer what enemies and
> other effects the player needs to be able to see. Teleconferencing, by
> contrast, tends to involve multiple audio and video streams going
> everywhere.
But most gamers DO use voice chat systems to coordinate their play with
teammates. This might be built into the game or it might be a second
program such as Mumble, Ventrilo, or TeamSpeak. Two-way headsets were
popular with gamers long before one saw them used for office conferencing.
And gamers care much more about latency than some office flunky who hears
something a second or two later than transmitted. So their codecs tend to
be a lot more network-friendly, trading off quality for low latency.
(Given the high bandwidth needs of video, I wonder if anyone's working on
avatar-based meeting systems wherein one creates an avatar from one's photo
(like Bitmoji) and uses pre-downloaded content (like video games) to
construct low-bandwidth video streams?)
prev parent reply other threads:[~2020-03-29 21:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-29 18:10 Kenneth Porter
2020-03-29 18:23 ` Jonathan Morton
2020-03-29 21:08 ` Kenneth Porter [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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='8236FA89207AF4F3FB62291A@[172.27.17.193]' \
--to=shiva@sewingwitch.com \
--cc=bloat@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