1)Run the AjaLog.exe command line tool to enable the traces of level 1 or 2:
e.g.: AjaLog 2
2)This creates a file c:\AJALog.txt that contains the traces. If the file
already exists it is emptied.
3)This file is updated a chunk at a time and can be opened with notepad at
anytime. However you will have to close it and re-open it to see the updates
made after it was opened.
4)Run the AjaLog.exe command line tool again to disable the traces: AjaLog
0. This will flush the remaining traces to the file and close the file. The
file can then be used a desired.

When the traces are disabled, there is very little overhead. When the traces
are enabled the overhead is also minimal, as it is only writing to memory
when the trace is first logged. Only later is the trace committed to the
file during a lazy commit cycle...

For now, only the render pin is using the log facility.

The current traces are:
1)Level 1: All render pin drift correction events, all drop/duplication
events and following six frames stats.
2)Level 2: All render pin drift correction events, all frame stats
regardless of whether or not a special case happened.

The timestamp of when we receive a frame is the time when we process that
frame, not the time when it is displayed. This is why it is sometimes way
ahead of the frame timestamp. What really matters is that the frame will be
displayed on time. These timestamps of when we receive a frame are sometimes
negative at the beginning. These are illegal timestamps we receive from the
clock, but it doesn't matter as this is all signed arithmetic.