[FFmpeg-trac] #6915(avformat:open): DASH audio segments duration doesn't match exactly with video segments duration.

[FFmpeg]

#6915: DASH audio segments duration doesn't match exactly with video segments
duration.
------------------------------------+-------------------------------------
             Reporter:  beloko      |                    Owner:  stevenliu
                 Type:  defect      |                   Status:  open
             Priority:  normal      |                Component:  avformat
              Version:  git-master  |               Resolution:
             Keywords:              |               Blocked By:
             Blocking:              |  Reproduced by developer:  0
Analyzed by developer:  0           |
------------------------------------+-------------------------------------

Comment (by j_karthic):

 Replying to [comment:34 stevenliu]:
 > Replying to [comment:33 j_karthic]:
 > > Replying to [comment:31 stevenliu]:
 > > > HLS Team have answered the question and about the 4.3.3.1.
 EXT-X-TARGETDURATION
 > > >
 > > > I respect Roger Pantos's and HLS Team's specification.
 > > >
 > > > Thanks for Apple and HLS Team's clearity explication
 > >
 > > Yes. That is clear. I am not contesting that. "You can have
 TARGETDURATION much higher than the EXTINF duration". The spec only says
 "round(EXTINF_duration) <= target_duration", which means for a EXTINF
 duration of 2.08 seconds, TARGETDURATION could be 2 second, 3 second, 5
 second or 100 seconds. Any target durations greater than or equal to the
 rounded segment duration is valid.
 >
 > I didn't say''' "You can have TARGETDURATION much higher than the EXTINF
 duration"''',  just round up to looks like plus one.
 No, you didn't say it. Sorry for the misunderstanding. I meant, Roger
 Pantos has said that. In his own words "It is perfectly legal to have
 EXTINF duration that are less than EXT-X-TARGETDURATION. '''Much less, in
 fact'''." I just wrote it the other way.

 Also he says "To be clear, the EXT-X-TARGETDURATION is the max
 ('''roughly''') of EXTINF durations. Thats all." Again note the use of the
 word "roughly", which one can interpret as 1.08 is roughly 1.

 >

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