-
-
Notifications
You must be signed in to change notification settings - Fork 10
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
Feature request: timestamps #14
Comments
could do. what are the timestamps relative to? if they are relative to the map progress then you could plot the timestamp inbetween the song progress as that is read directly from the game (though now that i think of it that timer can be delayed sometimes) |
I mean absolute timestamps, milliseconds from jan 1st 1970. but i've checked that again ant it turned out that network delays are hardly noticeable. so it's not that necessary to add timestamps but anyway. I'm trying to make a script that saves every event to the database as you play. then you feed your raw video recording to another script and it cuts each play to a different file based on saved data. And while start/end events don't have to be precise, i can't make auto-pause-cutter © work properly as it is delayed significantly. I think the reason is that I can't align recording start time with real-world timestamp to calculate offsets precisely. I'm using file creation date but it's only precise to a whole second. |
oh yeah sure i can add epoch timestamps |
Please add timestamp field to update object
It will be useful to get the exact time when that update happened.
I am building a custom client for MapData and saving updates to a database. I'm using the timestamp of websocket message received because it is the most accurate one I could get.
But I noticed that there are some delays between game events and tracked timestamps. I think they are caused by network delays between sending the message and receiving it but I'm not sure.
Anyway, adding timestamp to update would be useful
The text was updated successfully, but these errors were encountered: