You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
OBSInfoWriter currently exports only hours, minutes, and seconds. It would be good to export also milliseconds, because if the even happens at 10s 900ms, then automation tools will work on the incorrect point in the video stream.
It looks like it requires a change in InfoWriter.cpp:67 to get the time in milliseconds and InfoWriter.cpp:32 to output the time.
The standard format for reporting would be:
HH:MM:SS.000 (with 000 for the milliseconds)
The text was updated successfully, but these errors were encountered:
I do however have my doubts that this will fix anything, and even add a false sense of accuracy to the plugin. The time that the plugin provides is merely an approximation in seconds (based on the current time) and is not based on the time of the recording or stream itself. And even if it were that, there would always be a difference and you still would need to fix it manually anyway.
So, for now, I don't think it's worth making changes to implement this.
Has there been any progress with this issue? I understand your concerns. Even if the approximation to the time of the recording is bad maybe overall accuracy would be good; imagine synchronizing the whole log file to the recording, not each one separately. I need this plugin more accurate or a similar approach, please let me know if you know any other solution.
Thanks for investing your time into this project.
OBSInfoWriter currently exports only hours, minutes, and seconds. It would be good to export also milliseconds, because if the even happens at 10s 900ms, then automation tools will work on the incorrect point in the video stream.
It looks like it requires a change in InfoWriter.cpp:67 to get the time in milliseconds and InfoWriter.cpp:32 to output the time.
The standard format for reporting would be:
HH:MM:SS.000 (with 000 for the milliseconds)
The text was updated successfully, but these errors were encountered: