Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

getLocalTime return a future instant #272

Open
LVBK opened this issue Feb 23, 2017 · 3 comments
Open

getLocalTime return a future instant #272

LVBK opened this issue Feb 23, 2017 · 3 comments

Comments

@LVBK
Copy link

LVBK commented Feb 23, 2017

When i make a conference between Chrome 56 and Firefox 51.0.1
getLocalTime return a new instant come from future
difference with the System.currentTimeMillis() up to a few hours.
More specific diff2S inside getLocalTime is too big.
When i try compose all client videos and audios into one source base on metadata.json. It become a hours conversation.
but in real life only take place in a few minutes.
Thanks!

@gpolitis
Copy link
Member

Could it be that the client clocks are completely de-synchronized and our sync implementation doesn't take that use case into account?

@LVBK
Copy link
Author

LVBK commented Feb 24, 2017

@gpolitis
I skipped it. But fears that it could potentially lead to deficiencies.
In that case, may or may not be based on RECORDING_ENDED instant of metadata and the duration of the source file to calculate the instant of RECORDING_STARTED.
I'll try it right after this

@LVBK
Copy link
Author

LVBK commented Feb 27, 2017

@gpolitis I have tried many ways but still no solution to solve the problem. Sad

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

No branches or pull requests

2 participants