From: "Tomas Härdin" <tjoppen@acc.umu.se> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH 2/2] avformat/mxfenc: do not write index tables with the same InstanceUID Date: Wed, 16 Mar 2022 20:20:48 +0100 Message-ID: <448adba57d6da7376f139d9053c5740c29e045b7.camel@acc.umu.se> (raw) In-Reply-To: <6a996093-83fe-53c9-c0c0-6cbf9c5ad1e@passwd.hu> mån 2022-03-14 klockan 21:44 +0100 skrev Marton Balint: > > > On Mon, 14 Mar 2022, Tomas Härdin wrote: > > > mån 2022-03-14 klockan 20:54 +0100 skrev Marton Balint: > > > > > > > > > On Mon, 14 Mar 2022, Tomas Härdin wrote: > > > > > > > mån 2022-03-14 klockan 19:49 +0100 skrev Marton Balint: > > > > > Only index tables repeating previous index tables should use > > > > > the > > > > > same > > > > > InstaceUID. Use the index start position when generating the > > > > > InstanceUID to fix > > > > > this. > > > > > > > > > > Signed-off-by: Marton Balint <cus@passwd.hu> > > > > > --- > > > > > libavformat/mxfenc.c | 2 +- > > > > > 1 file changed, 1 insertion(+), 1 deletion(-) > > > > > > > > > > diff --git a/libavformat/mxfenc.c b/libavformat/mxfenc.c > > > > > index ba8e7babfb..5b972eadaa 100644 > > > > > --- a/libavformat/mxfenc.c > > > > > +++ b/libavformat/mxfenc.c > > > > > @@ -1757,7 +1757,7 @@ static void > > > > > mxf_write_index_table_segment(AVFormatContext *s) > > > > > > > > > > // instance id > > > > > mxf_write_local_tag(s, 16, 0x3C0A); > > > > > - mxf_write_uuid(pb, IndexTableSegment, 0); > > > > > + mxf_write_uuid(pb, IndexTableSegment, mxf- > > > > > > last_indexed_edit_unit); > > > > > > > > Two things: yes, it is good that this fixes the same > > > > InstanceUID > > > > being > > > > reused. But more importantly, we should not be writing files > > > > with > > > > over > > > > 65536 partitions! > > > > > > last_indexed_edit_unit is frame based not partition based, so it > > > can > > > overflow 65536 realtively easily, that is why I submitted patch > > > 1. > > > > Right. But we could use the partition number instead. > > Well, we could use mxf->body_partitions_count but it is not trivial > to see > that it will work for all cases. I don't see why not. But upping to 32-bit is easy anyways. > For simple indexes, we rewrite the index > table in the footer when writing the mxf header, opatom may follow > another > layout, so it just felt less error-prone to use actually the start > offset > of the index. We only need to do this for frame wrapping. And yeah that can be a separate patch. /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-03-16 19:21 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-14 18:49 [FFmpeg-devel] [PATCH 1/2] avformat/mxfenc: allow more bits for variable part in uuid generation Marton Balint 2022-03-14 18:49 ` [FFmpeg-devel] [PATCH 2/2] avformat/mxfenc: do not write index tables with the same InstanceUID Marton Balint 2022-03-14 19:40 ` Tomas Härdin 2022-03-14 19:54 ` Marton Balint 2022-03-14 20:24 ` Tomas Härdin 2022-03-14 20:44 ` Marton Balint 2022-03-16 19:20 ` Tomas Härdin [this message] 2022-03-16 19:38 ` Marton Balint 2022-03-16 20:06 ` Tomas Härdin 2022-03-16 21:17 ` Marton Balint 2022-03-14 19:35 ` [FFmpeg-devel] [PATCH 1/2] avformat/mxfenc: allow more bits for variable part in uuid generation Tomas Härdin 2022-03-14 19:57 ` Marton Balint 2022-03-14 20:21 ` 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=448adba57d6da7376f139d9053c5740c29e045b7.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