Hi Tomas, I hope you are doing well
> On Apr 14, 2019, at 8:58 AM, Tomas Härdin <tjop...@acc.umu.se> wrote:
>
> […]
>
>> @@ -2553,6 +2563,12 @@ static int mxf_parse_structural_metadata(MXFContext
>> *mxf)
>> }
>> }
>>
>> + for (int i = 0; i < mxf->fc->nb_streams; i++) {
>> + MXFTrack *track = mxf->fc->streams[i]->priv_data;
>> + if (track && track->body_sid && track->wrapping == UnknownWrapped)
>> + track->wrapping = mxf_get_wrapping_by_body_sid(mxf->fc,
>> track->body_sid);
>> + }
>
> Or maybe put a warning here instead. Vendors should fix their dang MXF
> muxers..Yeah… Since MXF is a container exclusively used in a professional environment, I believe we could be way more strict than other formats. I also feel we don’t have to support older files that were often broken. — Baptiste
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
