QLab 3 LTC Output

[Jason Crystal]

(I emailed this to support@, so apologies for the duplication, Figure 53 team!)

I have one QLab 3 rig feeding LTC SMPTE to another QLab 3 rig.

On the sending device:

- Created a Timecode Cue.

- Set framerate to 24fps.

- Selected LTC and a valid audio output.

On the receiving device:

- Created a new cue list and enabled "Trigger Cues from incoming"

- Selected LTC and a valid input.

- Select framerate at 24fps.

- Once I start striping from the source computer, I see the counter move on the destination.

Problem: There is a discrepancy between the "start time" and the time being read on the receiving device.  I trust the time reading to be accurate, and am skeptical about the start time on the Timecode cue.  The reason for this is that multiple devices (not just the QLab receiver) read the incorrect timecode together.

The farther away the start time is from 0:00:00:00, the greater the discrepancy.  Starting a Timecode cue at 11:00:00:00 yields an offset of about 40s, while starting at 5:30:00:00 is about half of that.  So there seems to be some (directly proportional) drift based on the start time of the cue.

I can recreate this discrepancy locally on my own machine with QLab 3, SoundFlower, and SMPTE Reader.

Any advice?

Thank you!

-Jason

[Jason Crystal]

For anyone following along at home, this was fixed in v3.0.6b3.  Thanks, team!

-Jason