On Wed, Dec 28, 2022 at 5:30 PM Nicolas George <geo...@nsup.org> wrote:
> Mark Gaiser (12022-12-28): > > > Ok, that made me laugh :) > > I did not write that. And that feels rude. > > > Please correct me as I'm probably wrong. > > But where did anyone say that there was a working alternative solution > that > > did not require customizing how ffmpeg is used? > > Like disabling safe. > > Heuristics to not require safe in cases where it is quite safe would be > much more acceptable than a redundant ad-hoc format. > That works for me. But is that feasible? My thinking is that you'd need to parse the entire file (the concat thing) to know if it is safe or not. > > -- > Nicolas George > _______________________________________________ > 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". > _______________________________________________ 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".
