In the arpeggiator module, I find the keyboard trigger mode confusing and its behaviour not as I would expect. Hence, either my expectation is wrong or its behaviour is not optimal.
For example, for a simple arp pattern "0" with "Up" selected, pressing the keys C and E results in the sequence "C C E C E ..." being played, whereas I would expect "C E C E C E ...". Similarily, with a pattern like "012" and "Static" selected, for pressing the keys "C E G" most of the time I get "C E G C E G ..." as expected, but sometimes I trigger the pattern starting with "E G ...". It looks to me (but I might be wrong), that as I am pressing a chord and in doing so pressing one key ever so slightly earlier than the others, QMidiArp immediately starts arpeggiating the (at this time) incomplete chord. Ideally, it would wait a couple of milliseconds and start arpeggiating the whole chord I am pressing.
This is with QMidiArp 0.5.2 on Ubuntu 13.04. I am using the internal time source for this (i.e. not Jack Transport). My aim is to use QMidiArp together with SooperLooper, where I set the same tempo in both applications and then trigger recording in SooperLooper just by starting playing.