From: Nicolas George via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: ayosec <code@ffmpeg.org>, Nicolas George <george@nsup.org>
Subject: [FFmpeg-devel] Re: [PATCH] Add drawvg video filter. (PR #20458)
Date: Sun, 19 Oct 2025 21:05:48 +0200
Message-ID: <aPU2jNELuzPG-zdG@phare.normalesup.org> (raw)
In-Reply-To: <175728541704.25.13938384286569916058@463a07221176>
ayosec via ffmpeg-devel (HE12025-09-07):
> PR #20458 opened by ayosec
> URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20458
> Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20458.patch
>
> This pull-request adds _drawvg_, a new filter to draw vector graphics on top of a video.
>
> This description is an updated version of the [proposal from a few weeks ago](https://ffmpeg.org/pipermail/ffmpeg-devel/2025-August/347825.html) in the ffmpeg-devel mailing list.
>
>
> ## What is drawvg
>
> drawvg is a filter to render vector graphics on top of video frames.
That makes a lot of code to review.
Michael, you gave this an approval of principle. Now that we have a
complete patch, do you believe we should start reviewing in order to
apply. Another option would be to suggest ayosec maintains it for some
time as a source plugin, while review happens in its time and while
requesting user comments and accepting incompatible changes in the
syntax.
Regards,
--
Nicolas George
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
prev parent reply other threads:[~2025-10-19 19:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-07 22:50 [FFmpeg-devel] " ayosec via ffmpeg-devel
2025-10-19 19:05 ` Nicolas George via ffmpeg-devel [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=aPU2jNELuzPG-zdG@phare.normalesup.org \
--to=ffmpeg-devel@ffmpeg.org \
--cc=code@ffmpeg.org \
--cc=george@nsup.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