On Wed, Jun 19, 2024 at 7:12 PM Mark Filipak <markfilipak.i...@gmail.com> wrote:
> On 19/06/2024 13.07, Mark Filipak wrote: > > Correction of first file name, sorry, copy goof. > > > > On 19/06/2024 12.45, Paul B Mahol wrote: > >> ffmpeg -i Ticket_11055.m2ts -an -c copy -f framecrc broken.video.txt > > > > Thank you, Paul. I have two _different_ outputs. One from this: > > ffmpeg -i g:\Ticket_11055.m2ts -an -c copy -f framecrc > c:\broken.video.txt > > and one from this: > > ffmpeg -copyts -i g:\Ticket_11055.m2ts -an -c copy -f framecrc > c:\broken.video.copyts.txt > > The reason they differ is '-copyts'. > The 2nd one (with the actual timestamps) matches the actual packets as > viewed in a packet browser. > The 1st one (with the bogus timestamps) has been messed with by FFmpeg. > > > It could be ffmpeg libavformat m2ts demuxer bug. Get the m2ts stream inspector tool to confirm. > _______________________________________________ > ffmpeg-user mailing list > ffmpeg-user@ffmpeg.org > https://ffmpeg.org/mailman/listinfo/ffmpeg-user > > To unsubscribe, visit link above, or email > ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe". > _______________________________________________ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
