On Tue, Jul 27, 2021 at 5:50 AM Gyan Doshi <ffm...@gyani.pro> wrote: > > > > On 2021-07-26 22:51, Hendrik Leppkes wrote: > > On Mon, Jul 26, 2021 at 5:16 PM Gyan Doshi <ffm...@gyani.pro> wrote: > >> > >> > >> On 2021-07-26 19:49, Steven Liu wrote: > >>> 在 2021年7月26日星期一,Gyan Doshi <ffm...@gyani.pro> 写道: > >>> > >>>> On 2021-07-26 16:39, Steven Liu wrote: > >>>> > >>>>> 2021年7月26日 下午6:57,Gyan Doshi <ffm...@gyani.pro> 写道: > >>>>>> Are you referring to the choice of FLV_CODECID values? > >>>>>> > >>>>> Not only, you can find whole history on: > >>>>> > >>>>> https://lists.ffmpeg.org/pipermail/ffmpeg-devel/ > >>>>> https://trac.ffmpeg.org/ticket/6389 > >>>>> https://trac.ffmpeg.org/ticket/3581 > >>>>> > >>>> try play this sample in ticket > >>>> The objections mainly center on compliance with Adobe's spec which is a > >>>> concern when muxing. > >>>> > >>>> no not only muxing, it’s format spec, and no documentation said which > >>> codec id is hevc. 10?11?12?13?14?15? How do you make sure which one is > >>> hevc > >>> from users flv? This is very unreasonable. > >> By making it a user option: ffmpeg -f flv -hevc_id 12 -i rtmp://... > >> > >> > > Which just screams ugly hack even more then anything else. > > Of course. The format is alive but the publisher has abandoned it, so > hacks are all that is left. >
That doesn't mean we have to endorse those hacks. HEVC in FLV, and a few other codecs, have been brought up numerous times. You can find all the arguments in the ML archives. Just posting yet-another-patch is not going to change those arguments or the reasons to not apply such a patch. - Hendrik _______________________________________________ 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".