From: David Lang <david@lang.hm>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: David Lang <david@lang.hm>, 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 13:00:57 -0700 (PDT) [thread overview]
Message-ID: <sr85r7n8-r735-0s73-52r6-87r436sor95o@ynat.uz> (raw)
In-Reply-To: <CD143AFB-9452-413C-BF91-8C180D0BEFD0@gmx.de>
On Mon, 18 Mar 2024, Sebastian Moeller wrote:
>> 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...
I'm talking about full frame high-end professional cameras (the ones where the
body with no lens costs $8k or so). This has been consistant for over a decade.
So I don't think it's a cost/manufacturing limit in place here.
There are a lot of cameras made with smaller sensors in similar resolution, but
very little at much higher resolutions.
at the low end, you will see some small, higher resolution sensors, but those
are for fixed lens cameras (like phones) where you use digital zoom
David Lang
next prev parent reply other threads:[~2024-03-18 20:00 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
2024-03-18 20:00 ` David Lang [this message]
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=sr85r7n8-r735-0s73-52r6-87r436sor95o@ynat.uz \
--to=david@lang.hm \
--cc=CHigbie1@Higbie.name \
--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