[FFmpeg-devel] [PATCH 1/3] avformat/flv: add support for h265 streams

[Zhao Zhili]

> On Jul 2, 2021, at 3:21 AM, Martin Storsjö <martin at martin.st> wrote:
> 
> On Thu, 1 Jul 2021, Jan Ekström wrote:
> 
>> On Thu, Jul 1, 2021 at 5:16 PM James Almer <jamrial at gmail.com> wrote:
>>> 
>>> From: Matthieu Patou <mpatou at fb.com>
>>> 
>>> Suggested-by: ffmpeg at fb.com
>>> Signed-off-by: James Almer <jamrial at gmail.com>
>>> ---
>> 
>> For the record, if Big Companies such as FB or Bilibili want to keep
>> on dragging FLV/RTMP around I recommend:
>> 
>> 1. Create something like
>> https://datatracker.ietf.org/doc/draft-ietf-cellar-codec/ for FLV.
>> 2. Have Adobe refer to that registry as the Point of Truth in their
>> spec/document.
>> 
>> That way we have a spec and Adobe does not have to update anything
>> beyond pointing towards the open codec register.
> 
> +1 on something like this. There has to be some sort of official spec for it, with at least a handwavy acknowledgement from Adobe.
> 
> And some more extensible way of signaling codecs might be good like JB suggests (although it makes the FLV stream much more cumbersome compared to other codecs), because the field only allows IDs 0-15, out of which already over half of them are defined, and if defining more of them, we're very soon out of numbers.

Here is my two cents.

Firstly, FLV should be deprecated, without adding new codec support.

Secondly, there are a lot of HEVC-in-FLV files exist. From the current patch, I can see a conflict definition of codecid. So now it's too late to file a specification. HEVC-in-FLV is the Titanic after crash into iceberg. So remux those non-standard files to something like mp4 is the only way to save life.

> 
> // Martin
> _______________________________________________
> ffmpeg-devel mailing list
> ffmpeg-devel at ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
> 
> To unsubscribe, visit link above, or email
> ffmpeg-devel-request at ffmpeg.org with subject "unsubscribe".
>