Changes between Initial Version and Version 1 of Ticket #5419, comment 7


Ignore:
Timestamp:
May 21, 2016, 8:54:24 PM (4 years ago)
Author:
an_ffmpeg_user
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #5419, comment 7

    initial v1  
    3232}}}
    3333
    34 I would expect this to play test000 > test001 > test002 > test003
     34I would expect this to play test000 > test001 > test002 > test003.
    3535
    3636{{{
     
    4949}}}
    5050
    51 A player which does not support EXT-X-DISCONTINUITY will behave unexpectedly.  We have seen players that either power-on-through, stall or skip.  This stream would not pass the Apple HLS Validator and playback support across software or devices could not be guaranteed.
     51I can't say how a player should behave in this case.  It will be unpredictable.  We have seen players that either power-on-through, stall or skip.  This stream would not pass the Apple HLS Validator and playback support across software or devices could not be guaranteed.
    5252
    53 I would expect FFmpeg to scream, moan and complain at the console.
    54 
    55 This appears to be the behavior that @xyq204101 describes.
    56 
     53I would expect FFmpeg's demuxer to scream, moan and complain at the console.
    5754
    5855{{{
     
    7370}}}
    7471
    75 I would expect a HLSv3 or above player/encoder with EXT-X-DISCONTINUITY support to play or generate a seamless test000 > test002 > test001 > test003 output without console errors or warnings.
     72I would expect a HLSv2 or above player/encoder with EXT-X-DISCONTINUITY support to play or generate a seamless test000 > test002 > test001 > test003 output without console errors or warnings.
    7673
    77 It may choose to verbose log that a discontinuity flag was detected, but it should not justify a console warning or error if the EXT-X-DISCONTINUITY flag is correctly placed.  But TBH, the console output is irrelevant - it is the stream that is important.
     74The demuxer may choose to verbose log that a discontinuity flag was detected, but it should not justify a console warning or error if the EXT-X-DISCONTINUITY flag is correctly placed.  But TBH, the console output is irrelevant - it is the stream that is important.
    7875
    7976@xyq204101 - how does FFplay behave when it tries to play your out.m3u8?  It will help take the output modules and VLC out of the equation, helping the developers tag with the correct component.
    8077
    81 Also, it may be better to take the FLV container out of the loop and encapsulate in a single MPEG-TS.
     78Also, it may be better to take the bitstream filter and FLV container out of the loop and encapsulate in a single MPEG-TS.
    8279
    83 {{{ffmpeg -i out.m3u8  -acodec copy -vcodec copy -bsf:a aac_adtstoasc -f mpegts test.ts}}}
     80{{{ffmpeg -i out.m3u8  -acodec copy -vcodec copy -f mpegts test.ts}}}
    8481
    8582