From: David Lang <david@lang.hm>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: Alexandre Petrescu <alexandre.petrescu@gmail.com>,
Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] It’s the Latency, FCC
Date: Sat, 16 Mar 2024 15:51:19 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.02.2403161549460.6193@nftneq.ynat.uz> (raw)
In-Reply-To: <C236E49C-D073-423C-8AD2-0CEA363B2925@gmx.de>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 2613 bytes --]
On Sat, 16 Mar 2024, Sebastian Moeller via Starlink wrote:
> Hi Alex...
>
>> On 16. Mar 2024, at 18:18, Alexandre Petrescu via Starlink <starlink@lists.bufferbloat.net> wrote:
>>
>>
>> Le 15/03/2024 à 21:31, Colin_Higbie via Starlink a écrit :
>>> Spencer, great point. We certainly see that with RAM, CPU, and graphics power that the software just grows to fill up the space. I do think that there are still enough users with bandwidth constraints (millions of users limited to DSL and 7Mbps DL speeds) that it provides some pressure against streaming and other services requiring huge swaths of data for basic functions, but, to your point, if there were a mandate that everyone would have 100Mbps connection, I agree that would then quickly become saturated so everyone would need more.
>>>
>>> Fortunately, the video compression codecs have improved dramatically over the past couple of decades from MPEG-1 to MPEG-2 to H.264 to VP9 and H.265. There's still room for further improvements, but I think we're probably getting to a point of diminishing returns on further compression improvements. Even with further improvements, I don't think we'll see bandwidth needs drop so much as improved quality at the same bandwidth, but this does offset the natural bloat-to-fill-available-capacity movement we see.
>>
>> I think the 4K-latency discussion is a bit difficult, regardless of how great the codecs are.
>>
>> For one, 4K can be considered outdated for those who look forward to 8K and why not 16K; so we should forget 4K.
>
> [SM] Mmmh, numerically that might make sense, however increasing the resolution of video material brings diminishing returns in perceived quality (the human optical system has limits...).... I remember well how the steps from QVGA, to VGA/SD to HD (720) to FullHD (1080) each resulted in an easily noticeable improvement in quality. However now I have a hard time seeing an improvement (heck even just noticing) if I see fullHD of 4K material on our 43" screen from a normal distance (I need to do immediate A?B comparisons from short distance)....
> I am certainly not super sensitive/picky, but I guess others will reach the same point maybe after 4K or after 8K. My point is the potential for growth in resolution is limited by psychophysics (ultimately driven by the visual arc covered by individual photoreceptors in the fovea). And I am not sure whether for normal screen sizes and distances we do not already have past that point at 4K....
true, but go to a 70" screen, or use it for a computer display instead of a TV
and you notice it much easier.
David Lang
next prev parent reply other threads:[~2024-03-16 22:51 UTC|newest]
Thread overview: 86+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.11.1710518402.17089.starlink@lists.bufferbloat.net>
2024-03-15 18:32 ` Colin Higbie
2024-03-15 18:41 ` Colin_Higbie
2024-03-15 19:53 ` Spencer Sevilla
2024-03-15 20:31 ` Colin_Higbie
2024-03-16 17:18 ` Alexandre Petrescu
2024-03-16 17:21 ` Alexandre Petrescu
2024-03-16 17:36 ` Sebastian Moeller
2024-03-16 22:51 ` David Lang [this message]
2024-03-15 23:07 ` David Lang
2024-03-16 18:45 ` [Starlink] Itʼs " Colin_Higbie
2024-03-16 19:09 ` Sebastian Moeller
2024-03-16 19:26 ` Colin_Higbie
2024-03-16 19:45 ` Sebastian Moeller
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
2024-03-16 18:51 ` [Starlink] It?s the Latency, FCC Gert Doering
2024-03-16 23:08 ` David Lang
2024-04-30 0:39 ` [Starlink] It’s " David Lang
2024-04-30 1:30 ` [Starlink] Itʼs " Colin_Higbie
2024-04-30 2:16 ` David Lang
2024-05-06 15:42 [Starlink] It’s " David Fernández
-- strict thread matches above, loose matches on Subject: below --
2024-05-06 13:21 David Fernández
2024-05-03 9:09 [Starlink] It's " David Fernández
[not found] <mailman.2877.1714641707.1074.starlink@lists.bufferbloat.net>
2024-05-02 14:47 ` [Starlink] It’s " Colin_Higbie
2024-05-02 19:50 ` Frantisek Borsik
2024-05-06 11:19 ` Alexandre Petrescu
2024-05-06 13:43 ` Nathan Owens
2024-05-06 15:22 ` Colin_Higbie
2024-05-14 19:23 ` Colin_Higbie
2024-05-15 6:52 ` Sebastian Moeller
2024-05-15 14:55 ` Colin_Higbie
2024-05-03 1:48 ` Ulrich Speidel
2024-05-03 7:22 ` Jeremy Austin
2024-05-03 9:02 ` Alexandre Petrescu
2024-05-03 8:29 ` Alexandre Petrescu
2024-05-03 8:34 ` Alexandre Petrescu
2024-05-01 16:35 [Starlink] It's " David Fernández
2024-05-01 8:41 David Fernández
[not found] <mailman.2785.1714507537.1074.starlink@lists.bufferbloat.net>
2024-04-30 20:48 ` [Starlink] It’s " Colin Higbie
2024-04-30 20:49 ` Colin_Higbie
2024-05-01 0:51 ` David Lang
[not found] <mailman.2779.1714503924.1074.starlink@lists.bufferbloat.net>
2024-04-30 19:31 ` Colin_Higbie
2024-04-30 19:51 ` Eugene Y Chang
2024-04-30 21:07 ` Dave Taht
2024-04-30 21:22 ` Frantisek Borsik
2024-04-30 22:02 ` Dave Taht
2024-04-30 22:03 ` Dave Taht
2024-04-30 22:05 ` [Starlink] Fwd: " Rich Brown
2024-04-30 22:10 ` Dave Taht
2024-04-30 22:42 ` [Starlink] " Rich Brown
2024-04-30 23:06 ` Dave Taht
2024-04-30 22:31 ` Eugene Y Chang
2024-04-30 21:22 ` Eugene Y Chang
2024-04-30 21:35 ` Frantisek Borsik
2024-04-30 21:53 ` Eugene Y Chang
2024-05-01 0:54 ` David Lang
2024-05-01 7:27 ` Frantisek Borsik
2024-05-01 19:26 ` Eugene Y Chang
2024-05-14 16:05 ` Dave Taht
[not found] <mailman.2775.1714488970.1074.starlink@lists.bufferbloat.net>
2024-04-30 19:12 ` Colin_Higbie
2024-04-30 19:31 ` Eugene Y Chang
2024-05-01 0:33 ` David Lang
2024-05-01 0:31 ` David Lang
2024-05-01 0:40 ` [Starlink] It?s " David Lang
[not found] <mailman.2773.1714488060.1074.starlink@lists.bufferbloat.net>
2024-04-30 18:05 ` [Starlink] It’s " Colin_Higbie
2024-04-30 19:04 ` Eugene Y Chang
2024-05-01 0:36 ` David Lang
2024-05-02 9:09 ` Alexandre Petrescu
2024-05-02 9:28 ` Ulrich Speidel
2024-04-30 20:05 ` Sebastian Moeller
2024-05-02 9:21 ` Alexandre Petrescu
[not found] <mailman.2769.1714483871.1074.starlink@lists.bufferbloat.net>
2024-04-30 14:00 ` Colin_Higbie
2024-04-30 14:25 ` Alexandre Petrescu
2024-04-30 14:32 ` Sebastian Moeller
2024-04-30 14:40 ` Alexandre Petrescu
2024-04-30 14:45 ` Sebastian Moeller
2024-04-30 14:56 ` Alexandre Petrescu
2024-04-30 15:04 ` David Lang
2024-04-30 15:01 ` David Lang
2024-04-30 9:54 David Fernández
[not found] <mailman.2495.1710610618.1074.starlink@lists.bufferbloat.net>
2024-03-16 19:10 ` Colin_Higbie
2024-03-16 19:32 ` Sebastian Moeller
2024-03-17 17:00 ` Alexandre Petrescu
2024-03-17 19:26 ` Frantisek Borsik
2024-03-15 3:53 Larry Press
2024-03-15 5:33 ` Dave Taht
2024-03-15 21:14 ` 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=alpine.DEB.2.02.2403161549460.6193@nftneq.ynat.uz \
--to=david@lang.hm \
--cc=alexandre.petrescu@gmail.com \
--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