[FFmpeg-trac] #10992(avformat:new): Option for forcing the inclusion of the hour field in WebVTT timestamps

[FFmpeg]

#10992: Option for forcing the inclusion of the hour field in WebVTT timestamps
-------------------------------------+------------------------------------
             Reporter:  ejm          |                    Owner:  (none)
                 Type:  enhancement  |                   Status:  new
             Priority:  normal       |                Component:  avformat
              Version:               |               Resolution:
             Keywords:  webvtt       |               Blocked By:
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
-------------------------------------+------------------------------------
Description changed by ejm:

Old description:

> While the [https://www.w3.org/TR/webvtt1/#webvtt-timestamp WebVTT spec]
> denotes that the hour field is optional on timestamps whose duration is
> less than one hour, it would be helpful to be able to forcibly include
> the field, even if the value is `00` with an option.
>
> Currently, this field is set in
> [https://git.ffmpeg.org/gitweb/ffmpeg.git/blob/HEAD:/libavformat/webvttenc.c#l41
> webvtt_write_time] by checking if `hour > 0`.
>
> The usecase here is with a third-party tool that expects the hour field
> regardless of its content, despite the spec, so I understand if that is
> too niche to justify inclusion.
>
> Thank you!

New description:

 While the [https://www.w3.org/TR/webvtt1/#webvtt-timestamp WebVTT spec]
 denotes that the hour field is optional on timestamps whose duration is
 less than one hour, it would be helpful to be able to forcibly include the
 field, even if the value is `00`, with an option.

 Currently, this field is set in
 [https://git.ffmpeg.org/gitweb/ffmpeg.git/blob/HEAD:/libavformat/webvttenc.c#l41
 webvtt_write_time] by checking if `hour > 0`.

 The usecase here is with a third-party tool that expects the hour field
 regardless of its content, despite the spec, so I understand if that is
 too niche to justify inclusion.

 Thank you!

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