(4) Insert a Signal Generator plugin on the THIRD insert (Insert C) of the Signal Pulse track.

Make sure the click is enabled in the session settings. The default settings are fine, and most likely will be Click 1 at a quarter note with the 'Classic Click Acc' sound and Click 2 also at a quarter note with the 'Classic Click' sound, with 'Follow Meter' enabled. (3) Insert the Click II plugin on the CLICK track. Name the first one 'CLICK' and the second one 'Signal Pulse.' VERY QUICK SERIES OF STEPS TO DEMONSTRATE THE PROBLEM: Third-party plugins like xfer's LFOTool and SoundToys' Tremolator similarly depend on knowing where the downbeat occurs. 'on the grid' and also the Pumper plugin, which mimics the effect of a typical EDM sidechain operation whereby the kick ducks the other instruments - which also, when operating properly, provides a rhythmic effect whose relationship to 'the grid' is predictable. When operating properly, it can provide rhythmic effects that stay in time with the music - i.e. Within that collection are the Filter Gate plugin, which 'slices' or gates the audio (while also offering the option to filter it) on a rhythmic basis, with a variety of parameters for controlling that behavior. The original post will follow below this new edit.Īudio plugins that provide tempo-synced processing, and also require synchronization to measure boundaries, exhibit timing problems when a delay-compensated plugin is present before them in the signal path. I'm editing this first post in this thread, to more concisely describe the issue. You can also mention that the case you're opening is related to existing Cases 0412423804. Please mention, in your case details, that this is in reference to Bug PT-263943. (The direct link is - but you'll need to be signed in.) To open a Support Case, you need to be signed into your account on, and then click on the 'Access the Support Center (Portal)' link. In today's world, the type of timing problems caused by the bug (again, see the simple but detailed description and steps below) cause major delays and inconsistencies when working on certain genres of music, and undermine the user's confidence in the accuracy of what's being programmed and played back.

This issue has already been logged as a bug, but it will only be prioritized for a fix if Avid becomes aware that it affects people's daily Pro Tools experience.

If you're new to this thread, please consider attempting to recreate the steps below - and if you do recreate the problem, please consider opening a Support Case.ĪND - if what we've been describing here is something that you've already seen in your own Pro Tools usage, and especially if it impacts your workflow, PLEASE also consider opening a Support Case.

Lfo tool fl studio