as said if you're using a 64 or 128 frames/buffer setting, it might not be an outrageously noticeable effect.
well, it may even get a bit of, say, humanized :)
technically speaking, and depending on the sample rate as well, this all means a 2ms tops for an induced quantization effect--all events aligning to the start time of jack period/process cycles--put in another way, this is maximum jitter in most circumstances.
anyway, i've made some improvement on it today and now it become quite independent of buffer-sizes, sample rates and all but midi resolution (ppqn). also worth mentioning is that the change is only effective when transport is rolling (play is on).
as said if you're using a 64 or 128 frames/buffer setting, it might not be an outrageously noticeable effect.
well, it may even get a bit of, say, humanized :)
technically speaking, and depending on the sample rate as well, this all means a 2ms tops for an induced quantization effect--all events aligning to the start time of jack period/process cycles--put in another way, this is maximum jitter in most circumstances.
anyway, i've made some improvement on it today and now it become quite independent of buffer-sizes, sample rates and all but midi resolution (ppqn). also worth mentioning is that the change is only effective when transport is rolling (play is on).
re. svn trunk r1972+ (aka. qtractor 0.4.8.66+)
cheers