From: Niklas Haas <ffmpeg@haasn.xyz>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [FFmpeg-cvslog] avfilter/buffersrc: add color_space/range parameters
Date: Wed, 10 Jan 2024 10:07:52 +0100
Message-ID: <20240110100752.GC67866@haasn.xyz> (raw)
In-Reply-To: <20240107095001.GI1833374@pb2>
On Sun, 07 Jan 2024 10:50:01 +0100 Michael Niedermayer <michael@niedermayer.cc> wrote:
> On Sun, Dec 31, 2023 at 09:49:43PM +0000, Niklas Haas wrote:
> > ffmpeg | branch: master | Niklas Haas <git@haasn.dev> | Fri Oct 20 16:55:43 2023 +0200| [2d555dc82d4ccd3c54c76e2fb3c861a8652de1c6] | committer: Niklas Haas
> >
> > avfilter/buffersrc: add color_space/range parameters
> >
> > To allow adding proper negotiation, in particular, to fftools.
> >
> > These values will simply be negotiated downstream for YUV formats, and
> > ignored otherwise.
> >
> > > http://git.videolan.org/gitweb.cgi/ffmpeg.git/?a=commit;h=2d555dc82d4ccd3c54c76e2fb3c861a8652de1c6
> > ---
> >
> > doc/filters.texi | 10 +++++++
> > libavfilter/buffersrc.c | 75 +++++++++++++++++++++++++++++++++++++++++++------
> > libavfilter/buffersrc.h | 6 ++++
> > 3 files changed, 83 insertions(+), 8 deletions(-)
>
> After this the command line tools print tons of warnings
Sent a fix to the ML, thanks.
> also iam still seeing a segfault i reported earlier, should i recheck which
> commit was causing that?
Are you referring to the hwframes issue, the vaf issue, or something
else entirely?
_______________________________________________
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:[~2024-01-10 9:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231231214944.B0C8541005F@natalya.videolan.org>
2024-01-07 9:50 ` Michael Niedermayer
2024-01-10 9:07 ` Niklas Haas [this message]
2024-01-10 16:24 ` Michael Niedermayer
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=20240110100752.GC67866@haasn.xyz \
--to=ffmpeg@haasn.xyz \
--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