From: Zhao Zhili <quinkblack@foxmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Niklas Haas <git@haasn.dev>
Subject: Re: [FFmpeg-devel] [PATCH 1/2] fftools/ffplay: add missing YUV metadata to buffersrc
Date: Fri, 26 Jan 2024 18:17:30 +0800
Message-ID: <tencent_9A4B8AE62D1090A6CBA7EA2ABA532B5C5606@qq.com> (raw)
In-Reply-To: <170626179485.8914.11156439406477457395@lain.khirnov.net>
> On Jan 26, 2024, at 17:36, Anton Khirnov <anton@khirnov.net> wrote:
>
> Quoting Niklas Haas (2024-01-10 10:05:46)
>> From: Niklas Haas <git@haasn.dev>
>>
>> Fixes error spam from the `ffplay` tool since commit 2d555dc82d, caused
>> by an oversight on my part - I didn't notice during development that
>> `ffplay` goes through its own filtering code path separate from
>> fftools/ffmpeg_filter.c
>
> Wouldn't the same issue affect any other caller?
Firstly, can avfilter support color range/space change from unspecified to a specified value
on the first frame? I think it should silent the log most of the cases.
Secondly, log once for non-serious case.
>
> --
> Anton Khirnov
> _______________________________________________
> 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".
_______________________________________________
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-26 10:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-10 9:05 Niklas Haas
2024-01-10 9:05 ` [FFmpeg-devel] [PATCH 2/2] fftools/ffmpeg_filter: simplify buffersrc arg printing Niklas Haas
2024-01-26 9:36 ` [FFmpeg-devel] [PATCH 1/2] fftools/ffplay: add missing YUV metadata to buffersrc Anton Khirnov
2024-01-26 10:17 ` Zhao Zhili [this message]
2024-02-01 13:10 ` Niklas Haas
2024-02-01 12:52 ` Niklas Haas
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=tencent_9A4B8AE62D1090A6CBA7EA2ABA532B5C5606@qq.com \
--to=quinkblack@foxmail.com \
--cc=ffmpeg-devel@ffmpeg.org \
--cc=git@haasn.dev \
/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