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
cmdseq-fix.txt
Propsed fix for the CmdSequencer timing alignment issue.
Here are the key changes:
Added microsecond-level compensation:
Convert timing to microseconds for precise adjustment
Subtract one second (1,000,000 microseconds) to compensate for the 1Hz execution offset
Only apply compensation when there's enough time margin (>= 1 second)
Enhanced execution precision:
Added a precision threshold (100 microseconds) for timing comparisons
Improved time comparison logic in isExecuteTime()
Separate handling for seconds and microseconds components
Maintained original functionality:
Preserved command serialization and execution logic
Kept activity logging and sequence state management
Retained time source and sequence validation checks
The fix adjusts the relative time calculation to account for the 1Hz execution rate while ensuring we don't introduce negative timing when dealing with very short delays. This should make the R00:00:0X notation behave as expected, delaying exactly X seconds rather than X+1.
Feature Description
Revisit time alignment on relative commands.
Rationale
A
R00:00:0X
typically delaysX+1
seconds if the sequencer is called at 1Hz, so theR
is not accurate.The text was updated successfully, but these errors were encountered: