MRCC slaving to a master input device?

[Jesse Johannesen]

Awesome! For me (and others I’d imagine) that’d be a really nice feature.

I would like this one too. I know in most devices I've had a look at, the way they tackle this is taking the average ms of the last 4 (or so) clock tics and use that to derive the clock out, so if you stop the clock it still runs, but takes a few more tics to get it's head on straight if you start the clock again. Seems like there could be a time-out which could be set up so that after that after so long without a new tick, it starts with a fresh buffer on the next incoming tick.
Jesse