Skip to content
This repository has been archived by the owner on Mar 26, 2023. It is now read-only.

Wrong Timestamps (04:39:37) and Unplayable video #355

Open
omarojo opened this issue Nov 4, 2016 · 0 comments
Open

Wrong Timestamps (04:39:37) and Unplayable video #355

omarojo opened this issue Nov 4, 2016 · 0 comments

Comments

@omarojo
Copy link

omarojo commented Nov 4, 2016

@jgh- Im doing live stream to Facebook Live endpoints where their specifics suggest the following:
From Facebook Live Documentation.

  • We accept video in maximum 720p (720 x 1280) resolution, at 30 frames per second. (or 1 key frame every 2 seconds)
  • You must send an I-frame (keyframe) at least once every two seconds throughout the stream.
  • Recommended max bit rate is 4 mbps. Going above this maximum is possible but will make live streams highly unstable.
  • The Live API accepts H264 encoded video and AAC encoded audio only

> In VideoCore I have set adaptiveBitrate activated, 30fps, and 4096000 bitrate

Currently the videos stream very good, but once the VOD is compiled, I get issues like the video lasting 04:39:37 hours and only playing the first frame with the audio playing in the background. Sometimes it plays well though. I asked Facebook support and they said it was a timestamp issue from my broadcasting client.

This is what they said: "It was discovered that the cause of busted encoding is the incorrectly large timestamp values in the middle of the stream, causing busted core encodings whose duration is much larger than actual duration."

Further Description of the issue
When playing video as VOD it freezes after the first couple frames and stays frozen with only audio playing. In addition to that, the video seems to be 4 hours and 39 minutes long, even though it was just a few minutes of live stream. This issue is experienced using Google Chrome 53.0.2785.143 (64-bit) and Official Facebook Mobile App iOS 10.0.2 (used for viewing only).

This doesnt happen in Safari Version 9.1.3, although the Freezing and 4 hour long issues appear in Safari only when trying to activate HD mode.
The behaviour is similar in Firefox too. In addition to that... HD mode is not available in Chrome even though the encoder was sending 1280x720.

The issue is very consistent, and happens highly regularly.
Sample 1: https://www.facebook.com/omarojo/videos/vb.715740753/10154012652625754/
Sample 2: https://www.facebook.com/omarojo/videos/vb.715740753/10154007465770754/

img_8611
img_8612
screen shot 2016-10-25 at 5 28 46 pm 2
screen shot 2016-10-25 at 5 29 01 pm 2
screen shot 2016-10-25 at 5 36 45 pm

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant