From: Michael Niedermayer <michael@niedermayer.cc>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [FFmpeg-cvslog] avfilter/buffersrc: add color_space/range parameters
Date: Sun, 7 Jan 2024 10:50:01 +0100
Message-ID: <20240107095001.GI1833374@pb2> (raw)
In-Reply-To: <20231231214944.B0C8541005F@natalya.videolan.org>
[-- Attachment #1.1: Type: text/plain, Size: 5567 bytes --]
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
./ffplay file-j2k.mxf
[ffplay_buffer @ 0x7f8b90001940] filter context - w: 320 h: 240 fmt: 2 csp: unknown range: unknown, incoming frame - w: 320 h: 240 fmt: 2 csp: gbr range: pc pts_time: 0
[ffplay_buffer @ 0x7f8b90001940] Changing video frame properties on the fly is not supported by all filters.
[ffplay_buffer @ 0x7f8b90001940] filter context - w: 320 h: 240 fmt: 2 csp: unknown range: unknown, incoming frame - w: 320 h: 240 fmt: 2 csp: gbr range: pc pts_time: 0.04
[ffplay_buffer @ 0x7f8b90001940] Changing video frame properties on the fly is not supported by all filters.
[ffplay_buffer @ 0x7f8b90001940] filter context - w: 320 h: 240 fmt: 2 csp: unknown range: unknown, incoming frame - w: 320 h: 240 fmt: 2 csp: gbr range: pc pts_time: 0.08
[ffplay_buffer @ 0x7f8b90001940] Changing video frame properties on the fly is not supported by all filters.
[ffplay_buffer @ 0x7f8b90001940] filter context - w: 320 h: 240 fmt: 2 csp: unknown range: unknown, incoming frame - w: 320 h: 240 fmt: 2 csp: gbr range: pc pts_time: 0.12
[ffplay_buffer @ 0x7f8b90001940] Changing video frame properties on the fly is not supported by all filters.
[ffplay_buffer @ 0x7f8b90001940] filter context - w: 320 h: 240 fmt: 2 csp: unknown range: unknown, incoming frame - w: 320 h: 240 fmt: 2 csp: gbr range: pc pts_time: 0.16
[ffplay_buffer @ 0x7f8b90001940] Changing video frame properties on the fly is not supported by all filters.
heres it with a random file from fate
./ffplay fate-suite/mxf/track_01_v02.mxf
[ffplay_buffer @ 0x7fd610001940] filter context - w: 1280 h: 720 fmt: 4 csp: unknown range: unknown, incoming frame - w: 1280 h: 720 fmt: 4 csp: bt709 range: tv pts_time: 0
[ffplay_buffer @ 0x7fd610001940] Changing video frame properties on the fly is not supported by all filters.
[ffplay_buffer @ 0x7fd610001940] filter context - w: 1280 h: 720 fmt: 4 csp: unknown range: unknown, incoming frame - w: 1280 h: 720 fmt: 4 csp: bt709 range: tv pts_time: 0.0417083
[ffplay_buffer @ 0x7fd610001940] Changing video frame properties on the fly is not supported by all filters.
[ffplay_buffer @ 0x7fd610001940] filter context - w: 1280 h: 720 fmt: 4 csp: unknown range: unknown, incoming frame - w: 1280 h: 720 fmt: 4 csp: bt709 range: tv pts_time: 0.0834167
[ffplay_buffer @ 0x7fd610001940] Changing video frame properties on the fly is not supported by all filters.
[ffplay_buffer @ 0x7fd610001940] filter context - w: 1280 h: 720 fmt: 4 csp: unknown range: unknown, incoming frame - w: 1280 h: 720 fmt: 4 csp: bt709 range: tv pts_time: 0.125125
[ffplay_buffer @ 0x7fd610001940] Changing video frame properties on the fly is not supported by all filters.
[ffplay_buffer @ 0x7fd610001940] filter context - w: 1280 h: 720 fmt: 4 csp: unknown range: unknown, incoming frame - w: 1280 h: 720 fmt: 4 csp: bt709 range: tv pts_time: 0.166833
[ffplay_buffer @ 0x7fd610001940] Changing video frame properties on the fly is not supported by all filters.
[ffplay_buffer @ 0x7fd610001940] filter context - w: 1280 h: 720 fmt: 4 csp: unknown range: unknown, incoming frame - w: 1280 h: 720 fmt: 4 csp: bt709 range: tv pts_time: 0.208542
[ffplay_buffer @ 0x7fd610001940] Changing video frame properties on the fly is not supported by all filters.
[ffplay_buffer @ 0x7fd610001940] filter context - w: 1280 h: 720 fmt: 4 csp: unknown range: unknown, incoming frame - w: 1280 h: 720 fmt: 4 csp: bt709 range: tv pts_time: 0.25025
[ffplay_buffer @ 0x7fd610001940] Changing video frame properties on the fly is not supported by all filters.
[ffplay_buffer @ 0x7fd610001940] filter context - w: 1280 h: 720 fmt: 4 csp: unknown range: unknown, incoming frame - w: 1280 h: 720 fmt: 4 csp: bt709 range: tv pts_time: 0.291958
[ffplay_buffer @ 0x7fd610001940] Changing video frame properties on the fly is not supported by all filters.
[ffplay_buffer @ 0x7fd610001940] filter context - w: 1280 h: 720 fmt: 4 csp: unknown range: unknown, incoming frame - w: 1280 h: 720 fmt: 4 csp: bt709 range: tv pts_time: 0.333667
[ffplay_buffer @ 0x7fd610001940] Changing video frame properties on the fly is not supported by all filters.
[ffplay_buffer @ 0x7fd610001940] filter context - w: 1280 h: 720 fmt: 4 csp: unknown range: unknown, incoming frame - w: 1280 h: 720 fmt: 4 csp: bt709 range: tv pts_time: 0.375375
[ffplay_buffer @ 0x7fd610001940] Changing video frame properties on the fly is not supported by all filters.
[...]
also iam still seeing a segfault i reported earlier, should i recheck which
commit was causing that?
thx
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Nations do behave wisely once they have exhausted all other alternatives.
-- Abba Eban
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 251 bytes --]
_______________________________________________
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 parent reply other threads:[~2024-01-07 9:50 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 [this message]
2024-01-10 9:07 ` Niklas Haas
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=20240107095001.GI1833374@pb2 \
--to=michael@niedermayer.cc \
--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