On Thu, Oct 25, 2018 at 1:39 PM Louis Letourneau <[email protected]> wrote: > > > However, I have now submitted a new patch which correctly fixes the issue I > > was solving. > > > > I took the time to reproduce your issue outlined in your original post. I > > managed to reproduce it and then resolve it with this new patch. > > > > The patch I submit has changes to his.c (relevant to your issue) and to > > mov.c (not relevant to your issue). > > > > http://ffmpeg.org/pipermail/ffmpeg-devel/2018-October/235524.html > > <http://ffmpeg.org/pipermail/ffmpeg-devel/2018-October/235524.html> > > > > https://patchwork.ffmpeg.org/patch/10767/ > > <https://patchwork.ffmpeg.org/patch/10767/> > > > > Regards, > > Nick > > > Your patch works like a charm. This issue has been a thorn on my side > for 1.5 years now. Thank you so much.
I also added a link to your patch in my ticket: https://trac.ffmpeg.org/ticket/7485 Louis _______________________________________________ ffmpeg-user mailing list [email protected] http://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email [email protected] with subject "unsubscribe".
