The currently failing test has to do with the current position of the Frame Sequencer, which is presently ignored on trigger. A hardware quirk causes extra length clocking in some cases, depending on how far along the FrameSequencer is at the time of trigger, probably to help improve the overall accuracy of the length counter.
The currently failing test has to do with the current position of the Frame Sequencer, which is presently ignored on trigger. A hardware quirk causes extra length clocking in some cases, depending on how far along the FrameSequencer is at the time of trigger, probably to help improve the overall accuracy of the length counter.