Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Dennis Mungai <dmngaie@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v2 0/6] WebRTC sub-second live streaming support
Date: Sun, 23 Mar 2025 15:06:01 +0300
Message-ID: <CAKKYfmHEn7BtME68KBmjr=a9KCr7YrGkvOytzBVF4Dzy0a8pUw@mail.gmail.com> (raw)
In-Reply-To: <ZWRl2K4AZtvqukpM@phare.normalesup.org>

On Mon, 27 Nov 2023 at 12:48, Nicolas George <george@nsup.org> wrote:

> Michael Riedl (12023-11-27):
> > Regardless, this will only test the implementation against itself. If
> that makes
> > sense and sounds reasonable, I will add the server support to this patch
> series.
>
> Thanks. It will not be enough in a perfect world, but it still is a very
> good start and much better than no testing at all.
>
> Regards,
>
> --
>   Nicolas George


An update:

The libdatachannel project has already implemented support for AV1 and HEVC
codecs in the RTP (de)packetizers, as of version v0.22.6.
Updating the patchset to match these capabilities for WHIP & WHEP would be
timely.
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

      reply	other threads:[~2025-03-23 12:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-07 14:12 Michael Riedl
2023-11-14 10:05 ` Tomas Härdin
2023-11-14 12:59   ` Michael Riedl
2023-11-14 15:46     ` Tomas Härdin
2023-11-15 21:45     ` Michael Niedermayer
2023-11-27  9:46       ` Michael Riedl
2023-11-27  9:48         ` Nicolas George
2025-03-23 12:06           ` Dennis Mungai [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

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

  git send-email \
    --in-reply-to='CAKKYfmHEn7BtME68KBmjr=a9KCr7YrGkvOytzBVF4Dzy0a8pUw@mail.gmail.com' \
    --to=dmngaie@gmail.com \
    --cc=ffmpeg-devel@ffmpeg.org \
    /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

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git