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

"[Bug]" clockskew #5

Closed
jaegeral opened this issue Aug 28, 2019 · 1 comment
Closed

"[Bug]" clockskew #5

jaegeral opened this issue Aug 28, 2019 · 1 comment
Labels
bug Something isn't working

Comments

@jaegeral
Copy link
Contributor

Within mans files. there is a value in the manifest.json called skew.
In metadata.json the value is called: "clockSkew" Not sure where the difference is.

This is meant to be the offset of the system clock.

That value can be pretty high and if not respected, the resulting timeline if off by that value.

Some example values:
`
-pt64s --> ofset: -01:04 min

+PT16710S --> offset +4 h38:30
`
So the number is seconds and the + or - is a prefix to tell how to interpret the offset.

imho mans_to_es should respect or at least tell if there is such an offset to calculate the normalized timeline afterwards.

Thx

@jaegeral jaegeral added the bug Something isn't working label Aug 28, 2019
@garanews
Copy link
Member

garanews commented Oct 3, 2019

added support in release 1.4 38329e2

@garanews garanews closed this as completed Oct 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants