On Tue, Oct 4, 2016 at 12:11 PM, Josh de Kock <j...@itanimul.li> wrote:
> Putting SCTE35 support in another library like Upipe was suggested as well. This is something that I don't understand. Should FFmpeg just ignore the existance of this very important standard in the professional video world? Drive users to something else, even though precisely these professional users often sponsor development? > My other question would be, if it does happen to get merged, how can I > disable SCTE35 entirely? Two questions 1) Does my patch break anything? If yes - it's just not ready to be merged. 2) SCTE-35, by its very definition, it's to cue video rebroadcasters to switch from one stream to another in real time, for example to add local commercials during a break. It's not a consumer format and you are just not going to see SCTE-35 in any stream "in the wild". By the time the stream reaches the consumer SCTE-35 has already done its job. However if you do deal with a stream that contains SCTE-35 data most likely you don't want to ignore it. Or maybe I'm just missing some real world scenarios? _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
