Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: David Lang <david@lang.hm>
Cc: Colin_Higbie <CHigbie1@Higbie.name>,
	"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 20:52:29 +0100	[thread overview]
Message-ID: <CD143AFB-9452-413C-BF91-8C180D0BEFD0@gmx.de> (raw)
In-Reply-To: <8s587854-5233-porp-0qrs-6s7ro5093494@ynat.uz>

Hi David,



> On 18. Mar 2024, at 20:32, David Lang via Starlink <starlink@lists.bufferbloat.net> wrote:
> 
> 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.

	One of the issues is cost, Zour sensor pixels need to be large enough to capture a sufficient amount of photons in a short enough amount of time to be useful, and that puts a (soft) lower limit on how small you can make your pixels... Once your divided up your sensor are into the smalles reasonable pixel size all you can do iso is increase sensor size and hence cost... especially if I am correct in assuming that at one point you also need to increase the diameter of your optics to "feed" the sensor properly. At which point it is not only cost but also size...

Regards
	Sebastian

> 
> 8k video is in the ballpark of 30mp
> 
> David Lang
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink


  reply	other threads:[~2024-03-18 19:52 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
2024-03-18 19:52     ` Sebastian Moeller [this message]
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=CD143AFB-9452-413C-BF91-8C180D0BEFD0@gmx.de \
    --to=moeller0@gmx.de \
    --cc=CHigbie1@Higbie.name \
    --cc=david@lang.hm \
    --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