From: Tristan Matthews via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Tristan Matthews <httamt@protonmail.com>
Subject: Re: [FFmpeg-devel] [PATCH v4] avformat: add AV1 RTP depacketizer and packetizer
Date: Wed, 26 Feb 2025 17:23:35 +0000
Message-ID: <4UA1JEyoyZNWMM2cTkvZlYzoe0UNwUcDXUbiuIJPX-oJlgvjKBtbiwJd0oHBNaquLvCdAEdiRQVQa5BOtkMLjUT8CpZO34x4aULPz5ty19s=@protonmail.com> (raw)
In-Reply-To: <3dc2802b-f50f-4aac-a64c-9336a1a9630e@axis.com>
On Friday, February 21st, 2025 at 5:15 AM, Chris Hodges <Chris.Hodges@axis.com> wrote:
> Hi Tristan,
>
> On 12/13/24 14:44, Tristan Matthews via ffmpeg-devel wrote:
>
> > Nice, looking forward to testing the next iteration.
>
>
> Sorry for the long delay, I got sidetracked with other work.
>
> > On a related note, one feature that only the VP8 depacketizer supports now is signalling via RTCP that it needs a keyframe (in the event of loss or the start of a stream), to do this you just have to implement the .need_keyframe callback (see https://git.ffmpeg.org/gitweb/ffmpeg.git/blob/eb79c316c7b205f45e7003e91f77c253818e6685:/libavformat/rtpdec_vp8.c#l274)
>
>
> Added code to support this and enabled the extra scan for the sequence
> header OBU.
>
This is great work, thanks for the additions and LGTM after some testing.
Best,
-t
_______________________________________________
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".
next prev parent reply other threads:[~2025-02-26 17:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0b3c803d-06cf-48b7-a6cc-5c89718d33e9@axis.com>
[not found] ` <173251117350.10731.1542254717493021660@lain.khirnov.net>
[not found] ` <b1e3009d-7cbc-4a38-9783-4175d5fa7914@axis.com>
[not found] ` <4eNqpkTNGNskG64scqGKGS_OKDOuEyzth3W8Cd3AYD6G_4CePb6C_R6qxR4QcE7yhYat_DXD49mBOhUn-4_Kz8d4qnFiCzwdvHb3qTDaebQ=@protonmail.com>
[not found] ` <d5435ad6-b03b-44c5-80df-737398aba571@axis.com>
[not found] ` <H3rZ_QqjzlLpRuUYM1OLP7dEy_1FXfC5BF95olbmuxUSaK-_a_XaREO4KYwI0ReRUiEvy5EMAKtp11kJ7lo8drd02AI0eUE6ZX024Xz99ZM=@protonmail.com>
[not found] ` <24f0b678-f066-4a73-a8c0-b8f9f80a512d@axis.com>
[not found] ` <9nYMkrGRIMVsBkNStNzAMocJCDDzdQWx2peYAQhlHuiezIWrTtP2zosRbB1_N0MgT7HeTt-uSij04-crFdWxxrVAZwIt-JVi17KSr07dypU=@protonmail.com>
2025-02-21 10:15 ` Chris Hodges
2025-02-26 17:23 ` Tristan Matthews via ffmpeg-devel [this message]
2025-02-26 18:26 ` Ronald S. Bultje
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='4UA1JEyoyZNWMM2cTkvZlYzoe0UNwUcDXUbiuIJPX-oJlgvjKBtbiwJd0oHBNaquLvCdAEdiRQVQa5BOtkMLjUT8CpZO34x4aULPz5ty19s=@protonmail.com' \
--to=ffmpeg-devel@ffmpeg.org \
--cc=httamt@protonmail.com \
/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