This happened to me yesterday, and from time to time.
I have not updated to the latest version of FloTools yet, but what
fixed it for me yesterday was simply just opening up the KM
application, instead of relying on the setting that allows the KM
engine to run at start-up.
I would assume that this equated to the fact that maybe not all of the
macros were active or something, until I opened the application.
This may be way off-base, but it seemed to work for me.
Other times, a shutdown of Protools or a system bounce do the trick.
Just my two cents. Hope it helps.
>
https://groups.google.com/d/msgid/ptaccess/DF9E32D0-6A40-4390-BDDF-E02B9947B49B%40gmail.com.
>