From: dan <dandenson@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: libreqos <libreqos@lists.bufferbloat.net>
Subject: Re: [LibreQoS] Fwd: [Starlink] Glass to glass latency test with video over QUIC
Date: Fri, 31 Mar 2023 17:24:03 -0500 [thread overview]
Message-ID: <CAA_JP8XSdfXx=TiUo3WNpXbzFwkZ+FyUinBoNbOk5JwbcwoMQQ@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw6Heoa8R0fW14GteKwTmD_XuGmd6ZNN8_m=E_doPNr6rw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2601 bytes --]
What’s the bitrate on the video though? It’s not that hard to push
uncompressed data out at low latency. I want to see a compressed <10Mbps
encode/decode.
On Mar 31, 2023 at 2:34:53 AM, Dave Taht via LibreQoS <
libreqos@lists.bufferbloat.net> wrote:
> ---------- Forwarded message ---------
> From: David Fernández via Starlink <starlink@lists.bufferbloat.net>
> Date: Fri, Mar 31, 2023 at 1:32 AM
> Subject: [Starlink] Glass to glass latency test with video over QUIC
> To: <starlink@lists.bufferbloat.net>
>
>
> I think some of you may be interested in this type of latency
> measurements. See below for setup details (SW used).
>
> Demo video (4m): https://youtu.be/adckQdZHECQ
>
> It seems this is State of the Art. I understand this test is done
> using FTTH at a minimum of 300 Mbit/s (symmetric), which is common and
> quite affordable in Barcelona area nowadays, but maybe he was even
> using Wi-Fi, not wired connection.
>
> Regards,
>
> David
>
> ---------- Mensaje reenviado ----------
> From: Jordi Cenzano Ferret <jcenzano@meta.com>
> To: Cullen Jennings <fluffy@iii.ca>, Jordi Cenzano Ferret
> <jcenzano=40meta.com@dmarc.ietf.org>
> Cc: MOQ Mailing List <moq@ietf.org>
> Bcc:
> Date: Fri, 31 Mar 2023 05:41:14 +0000
> Subject: Re: [Moq] Just FYI New media packager added 91+% efficient -
> NO action needed
> Thanks for your kind words Cullen, and thanks to the chairs for the agenda
> time.
>
> Please try the demo yourself, play with it and ping me for any
> clarifications you need or problems you find. Those are some pointers:
>
> Demo video (4m): https://youtu.be/adckQdZHECQ
>
>
> Encoder & Player code:
> https://github.com/facebookexperimental/webcodecs-capture-play
>
> Server/Relay code:
> https://github.com/facebookexperimental/go-media-webtransport-server
>
>
> Links to send/play data to a relay in Frankfurt (EU)
>
> Encoder link
>
> Player link
>
> Links to sened / play data to a relay in Oregon (USA)
>
> Encoder link
>
> Player link
>
>
> I hope all of you have a nice trip back!
> Jordi
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
>
>
> --
> AMA March 31: https://www.broadband.io/c/broadband-grant-events/dave-taht
> Dave Täht CEO, TekLibre, LLC
> _______________________________________________
> LibreQoS mailing list
> LibreQoS@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/libreqos
>
[-- Attachment #2: Type: text/html, Size: 4025 bytes --]
prev parent reply other threads:[~2023-03-31 22:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAC=tZ0pgX0NRS7eJaEhLVs3wwDHHj4KJc0ZXo+GT4Hzvr6Qutg@mail.gmail.com>
2023-03-31 8:34 ` Dave Taht
2023-03-31 22:24 ` dan [this message]
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/libreqos.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA_JP8XSdfXx=TiUo3WNpXbzFwkZ+FyUinBoNbOk5JwbcwoMQQ@mail.gmail.com' \
--to=dandenson@gmail.com \
--cc=dave.taht@gmail.com \
--cc=libreqos@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