From: Marton Balint <cus@passwd.hu>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 2/2] ffprobe: add -o option
Date: Thu, 9 Jun 2022 21:09:02 +0200 (CEST)
Message-ID: <2166a0-e72d-71e5-8265-fa3cadbadc42@passwd.hu> (raw)
In-Reply-To: <20220403140643.GB264464@mariano>
On Sun, 3 Apr 2022, Stefano Sabatini wrote:
> On date Wednesday 2021-04-21 23:57:04 +0200, Stefano Sabatini wrote:
>> On date Monday 2021-04-19 11:26:49 +0200, Michael Niedermayer wrote:
>>> On Sun, Apr 18, 2021 at 11:30:58PM +0200, Stefano Sabatini wrote:
>>>> This enables printing to a resource specified with -o OUTPUT.
>>>>
>>>> Address issue: http://trac.ffmpeg.org/ticket/8024
>>>> ---
>>>> doc/ffprobe.texi | 7 ++
>>>> fftools/ffprobe.c | 174 ++++++++++++++++++++++++++++++----------------
>>>> 2 files changed, 120 insertions(+), 61 deletions(-)
>>>
>>> This seems breaking some fate tests like fate-gaplessenc-itunes-to-ipod-aac
>>>
>>> I see 0 bytes in the output:
>>> 73 3D 4B 44 00 73 69 64 65 5F 64 61 74 61 7C 0A 0A
>>>
>>> thx
>>
>> That's right, I'm still forgetting to run make fate :-)
>> (avio_put_str() was adding the 0), should be fixed now.
>>
>> Thanks.
>
> Updated again, now it's locally passing fate with FATE samples (don't
> remember if other issues were spotted the past time).
This looks good to me in general, so I intend to apply. One thing that we
might do is to keep writing to the standard output if no output file is
specified instead of using the special "pipe:" URL. This way ffprobe
keeps working even if the pipe protocol is not compiled into
ffmpeg/libavformat.
Regards,
Marton
_______________________________________________
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:[~2022-06-09 19:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210418213058.24475-1-stefasab@gmail.com>
[not found] ` <20210421215335.GC12140@mariano>
2022-04-03 14:03 ` [FFmpeg-devel] [PATCH 1/2] lavf/avio: add avio_vprintf() Stefano Sabatini
2022-06-09 19:03 ` Marton Balint
2022-06-12 15:32 ` Stefano Sabatini
2022-06-12 17:00 ` Nicolas George
2022-06-16 16:23 ` Soft Works
[not found] ` <20210418213058.24475-2-stefasab@gmail.com>
[not found] ` <20210419092649.GJ4777@pb2>
[not found] ` <20210421215704.GD12140@mariano>
2022-04-03 14:06 ` [FFmpeg-devel] [PATCH 2/2] ffprobe: add -o option Stefano Sabatini
2022-06-09 19:09 ` Marton Balint [this message]
2022-06-12 15:33 ` Stefano Sabatini
2022-06-13 20:47 ` Marton Balint
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=2166a0-e72d-71e5-8265-fa3cadbadc42@passwd.hu \
--to=cus@passwd.hu \
--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