On Fri, Feb 7, 2025 at 2:31 PM Devlist Archive <devl...@rlb.org> wrote: > > > > > The cc_fifo mechanism is actually implemented within the various > > filters which change the framerate (deinterlacing, framerate > > conversion, interlacing), so no extra command line arguments are > > required. There are some edge cases though that don't properly handle > > it, and those mainly relate to cases such as the captions crossing > > back/forth between SEI and dedicated caption tracks (e.g. MP4 with a > > caption track, the subcc output, etc). > > > > Ok, based on this information I am going to make a bug report ticket for > the particular type of mp4 files I am using because while some caption data > is passed, it is garbled and the transcoding process is producing errors. > I was not aware that some work had been done to try to solve the frame rate > conversion issue already as the behaviour of ffmpeg implies that it doesn't > try to compensate for those changes for the file types I am working with. > There are also bugs in the subcc function that seem to be affecting display > time and other metadata. > > I assume that it would be more efficient and better to fix the existing 608 > only data path before trying to expand things to include 708? > > Zach
One thing worth noting is that the filenames in that Google drive don't match up with the example commands you've provided. I would recommend if you decide to open a ticket to either rename the files or change the commands so whoever tries to reproduce the issue knows they are working with the exact same files. Devin -- Devin Heitmueller, Senior Software Engineer LTN Global Communications o: +1 (301) 363-1001 w: https://ltnglobal.com e: devin.heitmuel...@ltnglobal.com _______________________________________________ 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".
