[FFmpeg-trac] #2224(undetermined:new): HLS output using b-frames has crazy initial timestamps
FFmpeg
trac at avcodec.org
Tue Mar 26 04:07:57 CET 2013
#2224: HLS output using b-frames has crazy initial timestamps
-------------------------------------+-------------------------------------
Reporter: nealzebub | Owner:
Type: defect | Status: new
Priority: normal | Component:
Version: unspecified | undetermined
Keywords: libx264 | Resolution:
mpegts hls | Blocked By:
Blocking: | Reproduced by developer: 0
Analyzed by developer: 0 |
-------------------------------------+-------------------------------------
Comment (by nealzebub):
Yeah, according to Wowza folk, that WARNING is due to the first timestamp
being zero.
"We now add a 10 second offset to the transport stream chunk timecodes
(pts and dts values) per Apple's recommendation. Without this the Apple
stream validator would throw warning messages. This is also how the Apple
segementer works."
I think I smell an request to automatically shift timestamps 10 seconds to
comply with the rec.
http://www.wowza.com/forums/showthread.php?16978-Apple-iOS-Acceptance-
Team-rejecting-Wowza-server-media-streams
http://www.wowza.com/forums/showthread.php?21181-Wowza-Media-Server-3-5-0
-duration-start-Bug-on-HLS/page2
--
Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/2224#comment:6>
FFmpeg <http://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list