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
This issue tracks the general idea of timestamping each event, or batch of events. In the case of USB HID packets, a single packet would require a timestamp, while with certain controllers, they provide a "device timestamp" (eg: jog wheels on the NI S4)
If you have input on how to best handle time-stamps, or "sub-time-stamps" like the device provided timestamp as above, please do post here - inspiration/suggestions appreciated!
The text was updated successfully, but these errors were encountered:
This issue tracks the general idea of timestamping each event, or batch of events. In the case of USB HID packets, a single packet would require a timestamp, while with certain controllers, they provide a "device timestamp" (eg: jog wheels on the NI S4)
If you have input on how to best handle time-stamps, or "sub-time-stamps" like the device provided timestamp as above, please do post here - inspiration/suggestions appreciated!
The text was updated successfully, but these errors were encountered: