From: Zane van Iperen <zane@zanevaniperen.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH v4 2/3] avformat/imf: fix packet pts, dts and muxing
Date: Fri, 18 Feb 2022 13:38:46 +1000
Message-ID: <bd633043-ec13-139e-1b6b-5200fff10f54@zanevaniperen.com> (raw)
In-Reply-To: <20220216165410.17063-2-pal@sandflow.com>
On 17/2/22 02:54, pal@sandflow.com wrote:
> av_log(s,
> AV_LOG_DEBUG,
> "Switch resource on track %d: re-open context\n",
> track->index);
> - if (open_track_resource_context(s, &(track->resources[i])) != 0)
> - return NULL;
> +
> + ret = open_track_resource_context(s, &(track->resources[i]));
Nit: "track->resources + i" is easier to read imo
> + if (ret != 0)
> + return ret;
> if (track->current_resource_index > 0)
> avformat_close_input(&track->resources[track->current_resource_index].ctx);
> track->current_resource_index = i;
> }
>
> - return &(track->resources[track->current_resource_index]);
> + *resource = &(track->resources[track->current_resource_index]);
Nit: track->resources + track->current_resource_index
The rest lgtm.
Will apply (with nits fixed) in a few days of no objections.
_______________________________________________
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-02-18 3:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-16 16:54 [FFmpeg-devel] [PATCH v4 1/3] avformat/imf: open resources only when first needed pal
2022-02-16 16:54 ` [FFmpeg-devel] [PATCH v4 2/3] avformat/imf: fix packet pts, dts and muxing pal
2022-02-18 3:38 ` Zane van Iperen [this message]
2022-02-16 16:54 ` [FFmpeg-devel] [PATCH v4 3/3] avformat/imf: document IMFVirtualTrackResourcePlaybackCtx pal
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=bd633043-ec13-139e-1b6b-5200fff10f54@zanevaniperen.com \
--to=zane@zanevaniperen.com \
--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