[FFmpeg-trac] #2230(avformat:open): Specified MPEG-TS metadata is not written to HLS(-ssegment) segments

[FFmpeg]

#2230: Specified MPEG-TS metadata is not written to HLS(-ssegment) segments
-------------------------------------+-------------------------------------
             Reporter:  nealzebub    |                    Owner:
                 Type:  defect       |                   Status:  open
             Priority:  normal       |                Component:  avformat
              Version:  unspecified  |               Resolution:
             Keywords:  hls          |               Blocked By:
  metadata segment                   |  Reproduced by developer:  1
             Blocking:               |
Analyzed by developer:  1            |
-------------------------------------+-------------------------------------
Changes (by saste):

 * analyzed:  0 => 1
 * keywords:  hls metadata => hls metadata segment
 * status:  new => open
 * component:  undetermined => avformat
 * reproduced:  0 => 1


Comment:

 Replying to [ticket:2230 nealzebub]:
 [...]
 > I am attempting to encode from file(mainly MP4) to HTTP Live
 Streaming(HLS) compatible streams.  I'd like to encode segments with
 metadata, just like I can with single-file mpegts files.
 >
 >
 > I obtained a source file, so I could enter this report, from:
 >  http://www.wowzamedia.com/_h264/bigbuckbunny_1500.mp4
 >
 >
 > The problem I encountered is when I specify metadata for the HLS
 segments, the metadata is confirmed in the console, but when I check the
 segments with FFprobe, it shows the default metadata.  When I specify to
 output "mpegts" instead of "ssegment", the output file contains the
 metadata I specified.
 >
 > '''What I want:'''
 >
 > {{{
 >       service_name    : Some Channel Name
 >       service_provider: Some Provider
 > }}}
 >
 > '''What I get:'''
 >
 > {{{
 >       service_name    : Service01
 >       service_provider: FFmpeg
 > }}}

 Hi,

 this is a known issue. The problem is that you here specify the metadata
 for the segment muxer, which does not propagate them to the chained muxer
 (TS in this case). I'll see if there is some way to fix it.

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