[FFmpeg-trac] #7480(avformat:open): HEVC codec info string

[FFmpeg]

#7480: HEVC codec info string
------------------------------------+------------------------------------
             Reporter:  tbucher     |                    Owner:
                 Type:  defect      |                   Status:  open
             Priority:  normal      |                Component:  avformat
              Version:  git-master  |               Resolution:
             Keywords:  hls         |               Blocked By:
             Blocking:              |  Reproduced by developer:  0
Analyzed by developer:  0           |
------------------------------------+------------------------------------
Changes (by Balling):

 * status:  new => open


Comment:

 "I was not sure what is the right format of that string. I saw some
 examples, like hvc1.2.4.L123.B0. But I didn't know what that meant"

 That part is implemented in a2b1dd0ce301450a47c972745a6b33c4c273aa5d.


 {{{
 snprintf(attr, sizeof(attr), "%s.%d.4.L%d.B01",
 av_fourcc2str(st->codecpar->codec_tag), profile, level);

 }}}
 and looks like it work with command in #8904. '''no-opengop=1, BTW, does
 not even exist in x265...
 '''

 That other issue with "for 2K and 4K resolution Apple clients don't
 playout properly even when properly constructed CODEC tag is
 there(hvc1.2.4.L153)" I do not think we should care. Apple 4K TV and not
 4K cannot even play 24.000 video correctly, playing it as 24/1.001 and
 losing frames there every 41 seconds, so who cares. See
 https://www.avsforum.com/threads/apple-tv-4k-lacks-support-
 for-24-000-video.2961262/ Though Macbooks play that correctly even on
 MacOS, so that part does not suck.

 Now the issue that is still not there is
 {{{
 #EXT-X-STREAM-INF:BANDWIDTH=3002024,RESOLUTION=1440x1080
 }}}
 and not


 {{{
 #EXT-X-STREAM-INF:BANDWIDTH=3002056,RESOLUTION=1440x1080,CODECS="hvc1"

 }}}

--
Ticket URL: <https://trac.ffmpeg.org/ticket/7480#comment:9>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker