Re: [FFmpeg-devel] [FFmpeg-cvslog] avfilter/buffersrc: add color_space/range parameters

Re: [FFmpeg-devel] [FFmpeg-cvslog] avfilter/buffersrc: add color_space/range parameters

[Michael Niedermayer]

[-- 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".

Re: [FFmpeg-devel] [FFmpeg-cvslog] avfilter/buffersrc: add color_space/range parameters

[Niklas Haas]

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".

Re: [FFmpeg-devel] [FFmpeg-cvslog] avfilter/buffersrc: add color_space/range parameters

[Michael Niedermayer]

[-- Attachment #1.1: Type: text/plain, Size: 1769 bytes --]

On Wed, Jan 10, 2024 at 10:07:52AM +0100, Niklas Haas wrote:
> 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?

I need to recheck, i just saw some segfaults in swscale related tests
and i think i reported it already a while ago ...

thx

[...]

thx
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Breaking DRM is a little like attempting to break through a door even
though the window is wide open and the only thing in the house is a bunch
of things you dont want and which you would get tomorrow for free anyway

[-- 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".