almostEric
commented
5 years ago Hi,
That is not a good assumption. Since QAR does a lot of internal clock manipulation, there needs to be a reference and this is done by measuring the time between the last 2 clock pulses
Sent from my iPhone
On Jun 21, 2019, at 8:16 PM, midiguru notifications@github.com wrote:
My assumption would be that when a pulse (gate or trigger) is received at the Start input jack for a row, the row would jump to its first step and continue from there. In the Windows build of 1.1.0, that isn't happening. When I send a pulse to the Start input jack, nothing happens -- the row just continues stepping along.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.
My assumption would be that when a pulse (gate or trigger) is received at the Start input jack for a row, the row would jump to its first step and continue from there. In the Windows build of 1.1.0, that isn't happening. When I send a pulse to the Start input jack, nothing happens -- the row just continues stepping along.