From: Thilo Borgmann via ffmpeg-devel <ffmpeg-devel@ffmpeg.org> To: ffmpeg-devel@ffmpeg.org Cc: Thilo Borgmann <thilo.borgmann@mail.de> Subject: Re: [FFmpeg-devel] [PATCH v3 1/2] avfilter: Add fsync filter Date: Mon, 18 Dec 2023 12:02:08 +0100 Message-ID: <8196823a-1331-4bf8-9736-df2745a48e52@mail.de> (raw) In-Reply-To: <20231217225130.GV6420@pb2> Am 17.12.23 um 23:51 schrieb Michael Niedermayer: > On Sat, Dec 16, 2023 at 09:13:21AM +0100, Thilo Borgmann via ffmpeg-devel wrote: > [...] > >> +// get number of bytes from cur to '\0' >> +static int buf_get_zero(FsyncContext *ctx) > > maybe doxygen syntax would make sense for comments descrining functions > its not public api but still maybe Better still. Done. >> +{ >> + return av_strnlen(ctx->cur, ctx->end - ctx->cur); >> +} >> + > [...] >> + if (s->last_frame) { >> + ret = av_sscanf(s->cur, "%"PRId64" %"PRId64" %d/%d", &s->ptsi, &s->pts, &s->tb_num, &s->tb_den); >> + if (ret != 4) { >> + av_log(ctx, AV_LOG_ERROR, "Unexpected format found (%i / 4).\n", ret); >> + ff_outlink_set_status(outlink, AVERROR_INVALIDDATA, AV_NOPTS_VALUE); >> + return AVERROR_INVALIDDATA; >> + } >> + >> + av_log(ctx, AV_LOG_DEBUG, "frame %lli ", s->last_frame->pts); > > warning: format ‘%lli’ expects argument of type ‘long long int’, but argument 4 has type ‘int64_t {aka long int}’ [-Wformat=] > > "%"PRIi64 / "%"PRId64 / "%"PRIu64 / "%"PRIx64 "%"PRId64 it shall be here and for the other DEBUG logs. All done locally, I'd appreciate if someone could test this on Windows, I'm curious about line endings in the map file... Thanks, Thilo _______________________________________________ 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:[~2023-12-18 11:02 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-16 8:13 [FFmpeg-devel] [PATCH v3 0/2] " Thilo Borgmann via ffmpeg-devel 2023-12-16 8:13 ` [FFmpeg-devel] [PATCH v3 1/2] " Thilo Borgmann via ffmpeg-devel 2023-12-17 22:51 ` Michael Niedermayer 2023-12-18 11:02 ` Thilo Borgmann via ffmpeg-devel [this message] 2023-12-31 12:31 ` Thilo Borgmann via ffmpeg-devel 2024-01-05 8:32 ` Thilo Borgmann via ffmpeg-devel 2023-12-18 1:04 ` Stefano Sabatini 2023-12-18 11:03 ` Thilo Borgmann via ffmpeg-devel 2024-01-06 17:39 ` James Almer 2024-01-07 13:02 ` Thilo Borgmann via ffmpeg-devel 2023-12-16 8:13 ` [FFmpeg-devel] [PATCH v3 2/2] fate: Add fsync filter tests Thilo Borgmann via ffmpeg-devel
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=8196823a-1331-4bf8-9736-df2745a48e52@mail.de \ --to=ffmpeg-devel@ffmpeg.org \ --cc=thilo.borgmann@mail.de \ /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