Hello,

We chase LTC using RME TCO cards with our several dual-Madi MacPro workstations.  We recently discovered that all of them have an almost 2-frame offset in the MTC that is generated by the TCO card.  There is no offset capability in the RME driver that I can find to compensate for this.  If I had to take a guess as to where this is happening, I'm betting the driver is not adding the required two-frame offset to the completed MTC word, because the MTC sync point is accurate at the first nibble of the frame number, but it's not complete until 8 quarter-frame messages later, which requires adding 2 frames to the number minus anticipated processing time.

Two things -

First - RME, please fix this immediately.  We've tested it on all our systems and it's the same issue.  It wasn't always incorrect but must have been broken in an update.  Two frames off for a synchronizer is not functional.

Second - anyone have a workaround temporarily?  We don't have a way to offset the incoming MTC in the workstation software without some abuse.

Thanks
Hugh