[FFmpeg-trac] #3356(undetermined:open): feature request: Segment HLS streams on SCTE 35 markers

[FFmpeg]

#3356: feature request: Segment HLS streams on SCTE 35 markers
-------------------------------------+-------------------------------------
             Reporter:  adamscybot   |                    Owner:
                 Type:  enhancement  |                   Status:  open
             Priority:  wish         |                Component:
              Version:  git-master   |  undetermined
             Keywords:  hls bounty   |               Resolution:
             Blocking:               |               Blocked By:
Analyzed by developer:  0            |  Reproduced by developer:  0
-------------------------------------+-------------------------------------

Comment (by adamscybot):

 Replying to [comment:19 er.anshul.maheshwari@…]:
 > @adamscybot
 > I dont have any tool to cross verify the output.
 > In the video you have shared, there is only one splice command, which is
 insert.
 > I do need more video with more commands in it.
 >
 > I was also looking for some ready made(may be enterprise) tool output to
 verify my output.
 > If you can help me, please.
 > (please contact me at er.anshul.maheshwari at gmail dot com)

 I should be able to help. My initial impression is that the data outputted
 there is correct. At the moment, I don't have access to the streams with
 SCTE markers in, as we are in the process of a rebuild. However, I'm
 hoping said access will be restored going into january.

 With this, I will be able to capture some real broadcast streams with
 SCTE35 markers in for you (both CUE IN and CUE OUT).

 Have you seen TSReader (http://www.tsreader.com/tsreader/)? With the lite
 (free) version, you should be able to open the original TS provided on the
 samples FTP. I *think* you are able to see the decoded scte35 markers with
 this tool.

 Keep in touch. I may send over my skype details if that is useful to you,
 to discuss provision of samples further?

 Good work!

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