General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Bruno George Moraes <brunogm0@gmail.com>
To: Bufferbloat lists bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat]  Integrating video codecs and congestion control
Date: Sat, 19 May 2018 14:39:32 -0300	[thread overview]
Message-ID: <CAJpr3FNXaoOMvFPCa4uxjx6KiEOguqtmRYrr+zkG0E2tCAa32g@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 241 bytes --]

On this subject,  [1] is a nice demonstration on strategies to reduce
buffer and play start time.

[1]  STSWE17: Will Law's presentation about low-latency streaming using
CMAF chunks
https://www.youtube.com/watch?v=hMtqWi_OoOU

Nice thread!

[-- Attachment #2: Type: text/html, Size: 393 bytes --]

             reply	other threads:[~2018-05-19 17:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-19 17:39 Bruno George Moraes [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-05-01  9:17 Toke Høiland-Jørgensen
2018-05-01  9:22 ` Jonathan Morton
2018-05-01 13:03 ` Marcelo Ricardo Leitner
2018-05-02  1:03 ` Dave Taht

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/bloat.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAJpr3FNXaoOMvFPCa4uxjx6KiEOguqtmRYrr+zkG0E2tCAa32g@mail.gmail.com \
    --to=brunogm0@gmail.com \
    --cc=bloat@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