Opened 5 years ago

Closed 4 years ago

#2601 closed defect (fixed)

hls output always starts at 1 even so you tell otherwise

Reported by: vkroutik Owned by:
Priority: minor Component: documentation
Version: git-master Keywords: hls
Cc: Blocked By:
Blocking: Reproduced by developer: yes
Analyzed by developer: yes

Description

Summary of the bug:
One of the params is -start_number 1 for running HLS output like this:
C:\ffmpeg\ffmpeg.exe -re -i "rtmp://bar/foo.flv" -y -c:v copy -c:a copy -hls_time 6 -hls_list_size 5 -hls_wrap 30 -start_number 1 "C:\Tools\Foo\stream.m3u8"

But if your -start_number 100000

It will still start with 1

Change History (8)

comment:1 Changed 5 years ago by cehoyos

  • Component changed from undetermined to avformat
  • Keywords hls added
  • Priority changed from important to normal
  • Resolution set to worksforme
  • Status changed from new to closed

This works fine here, if you want to reopen this ticket, please provide the command line that allows to reproduce the problem together with the complete, uncut console output and attach the m3u8 file.

comment:2 Changed 5 years ago by cehoyos

Please also consider to read again the following sentence from the specification:
A media URI is not required to contain its sequence number.

comment:3 in reply to: ↑ description ; follow-up: Changed 5 years ago by saste

  • Resolution worksforme deleted
  • Status changed from closed to reopened

Replying to vkroutik:

Summary of the bug:
One of the params is -start_number 1 for running HLS output like this:
C:\ffmpeg\ffmpeg.exe -re -i "rtmp://bar/foo.flv" -y -c:v copy -c:a copy -hls_time 6 -hls_list_size 5 -hls_wrap 30 -start_number 1 "C:\Tools\Foo\stream.m3u8"

But if your -start_number 100000

It will still start with 1

Confirm the bug. There is some confusion between URI sequence number (which may be cyclic) and the EXT-X-MEDIA-SEQUENCE number specified in the M3U8, which are two distinct entities.

comment:4 in reply to: ↑ 3 Changed 5 years ago by cehoyos

Replying to saste:

Replying to vkroutik:

Summary of the bug:
One of the params is -start_number 1 for running HLS output like this:
C:\ffmpeg\ffmpeg.exe -re -i "rtmp://bar/foo.flv" -y -c:v copy -c:a copy -hls_time 6 -hls_list_size 5 -hls_wrap 30 -start_number 1 "C:\Tools\Foo\stream.m3u8"

But if your -start_number 100000

It will still start with 1

Confirm the bug.

Then please add information on how it can be reproduced.

comment:5 Changed 5 years ago by cehoyos

As said, -start_number works fine here for hls.

comment:6 Changed 5 years ago by cehoyos

  • Priority changed from normal to minor
  • Reproduced by developer set
  • Status changed from reopened to open
  • Version changed from unspecified to git-master

After discussion with Stefano, this is a documentation bug.

comment:7 Changed 5 years ago by cehoyos

  • Component changed from avformat to documentation

comment:8 Changed 4 years ago by saste

  • Analyzed by developer set
  • Resolution set to fixed
  • Status changed from open to closed

Documentation should be clarified since:

commit f6707f0689e025e39f17c1e452f4033743079801
Author: Stefano Sabatini <stefasab@gmail.com>
Date:   Thu Jan 2 00:30:37 2014 +0100

    doc/muxers/hls: extend documentation
    
    In particular, reference segment muxer and clarify difference between
    segment filename number and playlist sequence number.
    
    Should fix trac ticket #2601.
Note: See TracTickets for help on using tickets.