Open sh0sh1n opened 5 years ago
Debugged this and the onset time reported is correct...it just happened to be a negative value which did not get converted to an appropriate timestamp; e.g., -3840ms is set as -1:59:56:160. It seems to subtract the negative time from 2 hours.
Describe the bug Using the Ruby API function to save Controller tracks information sets a negative start time for the first track. Should be 0.
To Reproduce Steps to reproduce the behavior:
Expected behavior Start time of first track should be non-negative.
Desktop (please complete the following information):