I guess that is what I'm trying to describe. The latency only affects the Chord Select functionality, correct? Seems like it wouldn't matter what type of signal comes into the Chord Select (noise, velocity, stepped voltage, etc) or how many voices it is using - it still receives it's timing from a centrally located trigger input. So why not add the micro-offset to the trigger's input only when sensing input from the Chord Select? I could see that type of buffer management to be a bit of a pain, but it could be a potential solution. Inversely, when in input is received from the Midi In or V/Oct, the trigger timing can switch back to normal if desired. ...Unless there is a use case where someone would use V/Oct at the same time as Chord Select...to which point the logic should probably still add the micro-timing adjustment since Chord Select is in use. At any rate, it seems like there could be some programming logic to manage that super minor timing adjustment within the module. That's my only pain point with it, and I wouldn't have figured out how to compensate for that trigger inconsistency had I not come to the forum. It's a KILLER module. If that timing adjustment could happen within the module...for me it would save rack space and elevate it to what will probably be one of my most used modules! Truly unique in the marketplace!