From: "Tomas Härdin" <tjoppen@acc.umu.se>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] avformat/mxfdec: do not log warning of multiple ANC packets if count is 0
Date: Fri, 09 Sep 2022 11:45:03 +0200
Message-ID: <b23bb2768d7b645d944ff627e5d1fce7eada6b2a.camel@acc.umu.se> (raw)
In-Reply-To: <573988b0-91a2-9f1c-af8b-e84bba820b97@yahoo.com>
ons 2022-09-07 klockan 15:28 +0100 skrev Gavin Smith:
>
> On 06/08/2022 21:44, Tomas Härdin wrote:
> > fre 2022-08-05 klockan 00:03 +0100 skrev Gavin Smith:
> > > Some NLVEs may insert a KLV packet for EIA-608 data even though
> > > the number of encapsulated ANC packets is zero.
> > > ---
> > > libavformat/mxfdec.c | 2 +-
> > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > Looks OK. Also I'm looking at maybe adding S436m support to mxfenc,
> > but
> > it's going to require a bit of plumbing in ffmpeg.c I think.
> >
> > /Tomas
>
> Can this be merged since there have been no objections?
Probably but I'm recovering from surgery, so some time next week for me
unless someone else feels like pushing. I see there are other MXF
patches too that I don't have the energy to deal with at the moment
/Tomas
_______________________________________________
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-09-09 9:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220804230338.13682-1-gcs584.ref@yahoo.com>
2022-08-04 23:03 ` Gavin Smith
2022-08-06 20:44 ` Tomas Härdin
2022-09-07 14:28 ` Gavin Smith
2022-09-09 9:45 ` Tomas Härdin [this message]
2022-09-09 15:33 ` Gavin Smith
2022-10-05 16:12 ` Gavin Smith
2022-10-06 8:26 ` Tomas Härdin
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=b23bb2768d7b645d944ff627e5d1fce7eada6b2a.camel@acc.umu.se \
--to=tjoppen@acc.umu.se \
--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