@cjclip, this is a known bug that should be fixed soon:
I’m guessing you are sending clock in from an external source?