I’ve noticed that when I start the transport at any point other than at the start marker, stopping the transport after the end marker (when there is no audio being played) results in a… pop? bang? burst? A brief accumulation of sound. What is happening, and how do I stop it from happening?
The effect is small (but still noticeable) when I solo tracks, so this is all tracks contributing to a very big burst/pop.
This is not something I can overlook in a live playback setting, so I’m hoping I can track down what’s causing this.
8.12 on Linux (purchased ready-to-run version) with a desktop DAW that has 96G RAM and an AMD Ryzen 9 CPU. Ardour only uses 2-3% CPU using all available processors.
If all of the tracks have a small DC offset that can cause a pop when playback stops and the audio interface output transitions back to a 0V DC quiescent condition (e.g. if the audio input has a slight DC offset for some reason).
I’m not sure of the best way to determine if that is the case, but a quick way to check might be to instantiate a copy of ACE High/Low Pass Filter on the output of the master bus, and set the high pass to be very steep at a very low frequency to see if that eliminates the problem.
Ardour does fade at transport start/stop to prevent audible clicks.
This can be disabled in *Session > Properties > Fades
It should not, but is a clue…
Perhaps the issue is that what causes this is switching from disk monitoring to input monitoring at stop. Similar to what @cclaude suggested there is could be a DC offset on an input to Ardour, maybe an mic or some other source from the soundcard.
Does this happen in every session, or only a specific one?
Check on the Recorder Page, if all inputs are silent
Add an oscilloscope plugin to Ardour’s master-bus… that may also shed some light.