Skip to content
This repository has been archived by the owner on Aug 9, 2022. It is now read-only.

Player Does't Use Latest Stream #8

Closed
ericxtang opened this issue Dec 4, 2017 · 2 comments
Closed

Player Does't Use Latest Stream #8

ericxtang opened this issue Dec 4, 2017 · 2 comments
Labels
type: bug something's not working correctly

Comments

@ericxtang
Copy link
Member

ericxtang commented Dec 4, 2017

(Correct me if I'm wrong) I think the current player implementation takes the first available video for an Eth address and makes that the stream for the channel.

Because of the way our p2p network works, there is a problem with that - a new video stream will not be on the gateway node (exit node hooked up to the CDN), and therefore initially appear like it's not available. So if someone stops an old stream and immediately starts a new one, the old stream will appear to be still available in the CDN, and the new stream will appear to be unavailable.

One possible work-around is to always try and show the video with the highest JobID.

p.s - The stream usually becomes available after 5-15 seconds.

@ericxtang ericxtang added the type: bug something's not working correctly label Dec 4, 2017
@jozanza
Copy link
Contributor

jozanza commented Dec 4, 2017

It should show the video with the highest jobId if it's on the CDN. The current player doesn't know anything about the p2p network and has no way of loading videos if they aren't on the CDN.

@dob
Copy link
Member

dob commented Jan 3, 2018

I believe this is fixed as per the latest player updates which autoplay the latest video after verifying that it is still receiving new content and hence "live"

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type: bug something's not working correctly
Projects
None yet
Development

No branches or pull requests

3 participants