Symptoms
- Displayed time is incorrect despite a valid timecode signal being received
- Time is offset by a consistent amount (hours or minutes)
- Date or time does not match the expected reference
Causes
- Incorrect time display settings in WinDiscovery (UTC vs local), time zone, DST, or a configured offset
- Incorrect time-handling settings (time zone, DST, offsets, UTC vs local display)
- Signal integrity issue (cable type and length, connector seating, grounding/shielding, or signal level)
Suggested solutions or troubleshooting steps
- In WinDiscovery, verify time display settings (UTC vs local), time zone, DST, and any configured offsets.
- Check inputs, cabling, and network connectivity.
- Restart and re-test after each change to isolate the cause.
Fix
- Confirm time code signal is present and at a valid level at the device input.
- Confirm your source is actually encoding date/year (SMPTE Leitch-style user bits, IRIG-B IEEE 1344 control functions).
- Disable DST/time zone offsets at the source, or compensate using receiver offset settings where available.
- If using non-date-encoded time code with overwrite features, ensure overwrite settings match your intended behavior.
Related articles
Article ID: KB-TC-002
KB Version: