Hi - I recently discovered some sessions that I had recorded in the last few months have glitches (clicks/pops) in one or more tracks near in time to the enabling or disabling of another track.
For example, I might be recording several tracks overall, but a couple of them are used only sporadically, so I enable/disable them on the fly, to avoid wasting disc space. I’ve found that, apparently, switching a track’s record button on or off can induce a glitch in one or more of the other (enabled) tracks. Neither Ardour nor qjackctl show any xruns. I’ve gone back to look at several sessions, and so far I’m only seeing this in those that were recorded using a Focusrite Saffire Pro 40 through FFADO. I haven’t found it (yet) in sessions that were recorded from a Soundcraft Si Performer over USB, but I’ve only checked a couple of those. It appears that, in order for the glitch to be audible, either or both of the track being switched on/off, and the track(s) being affected, need to be recording some sound (ie, not just silence), and of course the sound they’re recording needs to be “friendly” to audible detection of clicks. Even so, which track(s) are affected by a given transition seems to be somewhat random. Sometimes it’s very obvious in the mix, but other times I only discover it by PFL’ing each potentially affected track in turn.
The sessions I’ve looked at so far were recorded with either 4.0.0 or 4.4.0 64-bit (not sure which version was used in some cases) from ardour.org, JACK 1.9.9.5, FFADO 2.2.1 (compiled from source), on Fedora 19 with CCRMA extensions, kernel 3.10.25-200.rt23.1.fc19.ccrma.x86_64.rt.
I can open a bug report on this, but at the moment I’m not sure how reproducible it is. I wanted to ask here first to see if anyone else has seen this, and in case the devs might be aware of any changes since 4.0.0 (or in JACK or FFADO) that could relate to this. (ie, if it’s a known issue that’s already been fixed, I won’t bother.)