The output can be clocked with timecode data from various sources. This allows for frame-synchronization of the output which keeps network traffic to a minimum and can reduce tracking drift.
RF currently only supports one Decklink card per system, and will automatically choose the first card it sees. The input format (framerate/resolution) is automatically detected. The Input chooses which physical video input you want to use.
The "ref" or genlock input on Decklink cards only clocks the video output, and has no bearing on Reality Field. RF only pulls timecode from the video.
Decklink card inputs can only be used by one program at a time. You will not be able to use the video in Unreal/Aximmetry etc if you are using it for frame sync in RF.
LTC timecode is carried through a standard PC audio jack, and can be provided from a normal timecode box with the correct cable. RF uses WASAPI for this. This is a very cheap and convenient way to get timecode, but it is the highest latency option available.
When connected to an Optitrack NatNet source, timecode and genlock can be provided through an eSync hub. This is automatically pulled from the data stream and can be used for sync.
Raw LONET2 data can be logged to a file on the PC. This must be manually started/stopped. LONET 2 is a simple JSON protocol that can be easily parsed with scripts by a VFX house.
If your video source carries timecode, it will be shown at the top. This timecode is also made available to other devices via an automatic OSC output. This output it sent to localhost on port 8000, using the following format:
/genlock [timecode string]
Systems like Retracker use this to clock their own output.