> Which kind of recurrence pattern are you talking about? I am talking about really sparse pattern. e.g. nothing for a long time, then ads inserted or program changes, and embedded bit stream starts. It's not that often but it happens with SCTE-20, or sloppy DVD edits for example.
> Even if it was just 98% reliable, those 2% could not serve as justification > for why probing of the 98% takes twice or thrice the time. I do agree. Having the "fast but catches most" solution as an option would be useful. I had tried to put up 3 proposals and -analyze_frames was the only one that seemed to stick since it did not break API or make things awkward with dispositions. For now, -analyze_frames helps to at least make the feature workable and has a utilitarian purpose for flexible CC probing needs. _______________________________________________ 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".
