From: J Pan <Pan@uvic.ca>
To: Sauli Kiviranta <smksauli@gmail.com>
Cc: Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: [Starlink] Re: Testing 4K live video over Starlink with added +10% packet loss
Date: Tue, 9 Sep 2025 14:02:23 -0700 [thread overview]
Message-ID: <CAHn=e4hxFcB4=84BnwzPuntMDbpPptaSdLnCFNUG67QZg+sV6A@mail.gmail.com> (raw)
In-Reply-To: <CAJbqEYCxfLJr-sk7ZK54760RZTpO0HM+_9qJd+X0c6jeHS6wcQ@mail.gmail.com>
fast.com measures tcp performance and you used udp to get the best out
of a lossy link? spacex uses multiple starlink dishes on a launch
vehicle and pick whatever made through too
--
J Pan, UVic CSc, ECS566, 250-472-5796 (NO VM), Pan@UVic.CA, Web.UVic.CA/~pan
On Tue, Sep 9, 2025 at 1:50 PM Sauli Kiviranta via Starlink
<starlink@lists.bufferbloat.net> wrote:
>
> We start to get somewhere that is what I would say cool level. Our target
> is Ulrich Spiedel storm conditions measured over the Gabriella cyclone with
> Starlink.
>
> https://x.com/sksauli/status/1964349734304301268
>
> We have also now test running just accelerating all data, so we can get
> same effects for better utilization rate of the link.
>
> Anyone know what kind of bit error rates or packet loss levels are in the
> streams for SpaceX launches? Usually they look very very stable.
>
> Anyone want to test this? Send me email sauli.kiviranta@xrtc.io
>
> Best regards,
> Sauli
> _______________________________________________
> Starlink mailing list -- starlink@lists.bufferbloat.net
> To unsubscribe send an email to starlink-leave@lists.bufferbloat.net
next prev parent reply other threads:[~2025-09-09 21:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 20:49 [Starlink] " Sauli Kiviranta
2025-09-09 21:02 ` J Pan [this message]
2025-09-09 21:05 ` [Starlink] " Sauli Kiviranta
2025-09-09 21:13 ` J Pan
2025-09-09 21:26 ` Sauli Kiviranta
2025-09-10 8:11 ` Sauli Kiviranta
2025-09-10 15:53 ` J Pan
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='CAHn=e4hxFcB4=84BnwzPuntMDbpPptaSdLnCFNUG67QZg+sV6A@mail.gmail.com' \
--to=pan@uvic.ca \
--cc=smksauli@gmail.com \
--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