General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Michael Richardson <mcr@sandelman.ca>
To: Sebastian Moeller <moeller0@gmx.de>,
	Dave Taht via Bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] 80Mbit streaming
Date: Fri, 06 Oct 2023 13:49:46 -0400	[thread overview]
Message-ID: <2673596.1696614586@dyas> (raw)
In-Reply-To: <8F072AF6-D0B0-4ACC-9333-7CEB31CC9104@gmx.de>

[-- Attachment #1: Type: text/plain, Size: 1280 bytes --]


Sebastian Moeller <moeller0@gmx.de> wrote:
    > On 5 October 2023 21:53:55 CEST, Michael Richardson <mcr@sandelman.ca>
    > wrote:
    >> Sebastian Moeller via Bloat <bloat@lists.bufferbloat.net> wrote: > Now
    >> finally, a use case that needs at least a ~100Mbps link... question >
    >> is, how much better than the competitors streaming this is going to >
    >> look?
    >>
    >> What's the point?  My eyesight isn't actually that good :-)

    > Mine neither... from my low-fi perspective, anything up to ~full hd
    > (1920x1080) was a noticeable improvement, but e.g. going to 4K on a 43"
    > screen does not feel any better...  My comment was driven mostly by the

One can stream monster resolutions across very high latency/bloated links.

Meanwhile, my new-this-year Roku enabled TV crashes if I change the volume
while Netflix or Prime or Disney is in the process of starting the stream.

I'm at a loss to understand why TVs don't come with cameras, or at least
support some wide variety of USB webcams.  It seems obvious to me that they
should be videophones.... but that requires low-latency networks and
low-latency wifi.  (My TV supports one USB-Ethernet device, but not one I
happened to have around)

So why doesn't Sony do this with their PS4/PS5?



[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 658 bytes --]

      parent reply	other threads:[~2023-10-06 17:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-05 17:04 Dave Taht
2023-10-05 18:31 ` Sebastian Moeller
2023-10-05 19:02   ` jf
2023-10-05 19:53   ` Michael Richardson
2023-10-06  5:07     ` Sebastian Moeller
2023-10-06  5:26       ` David Lang
2023-10-06 17:49       ` Michael Richardson [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=2673596.1696614586@dyas \
    --to=mcr@sandelman.ca \
    --cc=bloat@lists.bufferbloat.net \
    --cc=moeller0@gmx.de \
    /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