Indeed. I only got to feel this woof thing on bigger buffer sizes (eg buffer size = 4096) where it gets really noticeable (and annoying, yeah:) Will investigate it further, over the holidays perhaps ;)
Re. the MIDI looping drop notes, I must tell there was a serious mistake on the drift correction code on one of these recent SVN revisions, maybe that's what have been troubling you. Maybe not. I'll ask you to update from svn trunk again, giving today's qtractor 0.4.3.1461+. If it ain't much for you, build with ./configure --enable-debug and, among other things, watch for these messages coming out from the console (stderr):
point here is that iTimeDrift value must not, er, drift away too much and most importantly, the bracketed number and percentage should be near or rounding zero from either side (-/+), at all times. These numbers (inside brackets) get higher valued as higher the audio (jackd) buffer size is, so you'll have lower drifting/jitter as well as lower latencies. If these values get somewhat crazy, stop and try with another MIDI timer resolution (see View/Options.../MIDI/Playback/Queue timer (resolution)). Or a smaller buffer size. As said before, you should be comfortable with a 128 frames buffer size (-p128) as a reasonable target and a double- or triple-period per buffer (-n2 or -n3, these are all jackd parameters, of course).
Indeed. I only got to feel this woof thing on bigger buffer sizes (eg buffer size = 4096) where it gets really noticeable (and annoying, yeah:) Will investigate it further, over the holidays perhaps ;)
Re. the MIDI looping drop notes, I must tell there was a serious mistake on the drift correction code on one of these recent SVN revisions, maybe that's what have been troubling you. Maybe not. I'll ask you to update from svn trunk again, giving today's qtractor 0.4.3.1461+. If it ain't much for you, build with
./configure --enable-debugand, among other things, watch for these messages coming out from the console (stderr):qtractorMidiEngine:drift(): iAudioTime=99999 iMidiTime=99998 (1) iTimeDrift=1 (0.0015%)point here is that iTimeDrift value must not, er, drift away too much and most importantly, the bracketed number and percentage should be near or rounding zero from either side (-/+), at all times. These numbers (inside brackets) get higher valued as higher the audio (jackd) buffer size is, so you'll have lower drifting/jitter as well as lower latencies. If these values get somewhat crazy, stop and try with another MIDI timer resolution (see View/Options.../MIDI/Playback/Queue timer (resolution)). Or a smaller buffer size. As said before, you should be comfortable with a 128 frames buffer size (-p128) as a reasonable target and a double- or triple-period per buffer (-n2 or -n3, these are all jackd parameters, of course).
BBL