Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: David Lang <david@lang.hm>
To: Colin_Higbie <CHigbie1@Higbie.name>
Cc: "starlink@lists.bufferbloat.net" <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] Sidebar to It’s the Latency, FCC: Measure it?
Date: Mon, 18 Mar 2024 12:32:38 -0700 (PDT)	[thread overview]
Message-ID: <8s587854-5233-porp-0qrs-6s7ro5093494@ynat.uz> (raw)
In-Reply-To: <MN2PR16MB3391C8A37D3869359B7DEA94F12D2@MN2PR16MB3391.namprd16.prod.outlook.com>

On Mon, 18 Mar 2024, Colin_Higbie via Starlink wrote:

> Will that 25Mbps requirement change in the future? Probably. It will probably 
> go up even though 4K HDR streaming will probably be achievable with less 
> bandwidth in the future due to further improvements in compression algorithms. 
> This is because, yeah, eventually maybe 8K or higher resolutions will be a 
> standard, or maybe there will be a higher bit depth HDR (that seems slightly 
> more likely to me). It's not at all clear though that's the case. At some 
> point, you reach a state where there is no benefit to higher resolutions. 
> Phones hit that point a few years ago and have stopped moving to higher 
> resolution displays. There is currently 0% of content from any major provider 
> that's in 8K (just some experimental YouTube videos), and a person viewing 8K 
> would be unlikely to report any visual advantage over 4K (SD -> HD is huge, HD 
> -> 4K is noticeable, 4K -> 8K is imperceptible for camera-recording scenes on 
> any standard size viewing experience).

I'll point out that professional still cameras (DSLRs and the new mirrorless 
ones) also seem to have stalled with the top-of-the-line Canon and Nikon topping 
out at around 20-24 mp (after selling some models that went to 30p or so), Sony 
has some models at 45 mp.

8k video is in the ballpark of 30mp

David Lang

  parent reply	other threads:[~2024-03-18 19:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.2503.1710703654.1074.starlink@lists.bufferbloat.net>
2024-03-18 16:41 ` Colin_Higbie
2024-03-18 16:49   ` Dave Taht
2024-03-18 19:32   ` David Lang [this message]
2024-03-18 19:52     ` Sebastian Moeller
2024-03-18 20:00       ` David Lang
2024-03-19 16:06         ` David Lang
     [not found] <mailman.11.1710518402.17089.starlink@lists.bufferbloat.net>
2024-03-15 18:32 ` [Starlink] It’s the Latency, FCC Colin  Higbie
2024-03-15 18:41   ` Colin_Higbie
2024-03-15 19:53     ` Spencer Sevilla
2024-03-15 23:07       ` David Lang
2024-03-16 18:45         ` [Starlink] Itʼs " Colin_Higbie
2024-03-16 23:05           ` David Lang
2024-03-17 15:47             ` [Starlink] It’s " Colin_Higbie
2024-03-17 16:17               ` [Starlink] Sidebar to It’s the Latency, FCC: Measure it? Dave Collier-Brown

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=8s587854-5233-porp-0qrs-6s7ro5093494@ynat.uz \
    --to=david@lang.hm \
    --cc=CHigbie1@Higbie.name \
    --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