---
title: Using Timecode Synchronisation
description: Align your tracking data perfectly with external audio and facial mocap. Learn how to process timecode metadata in Genesis Post for seamless cross-system synchronization.
---

[Skip to content](https://docs.move.ai/knowledge/genesis-using-timecode-synchronisation-#main-content)

![Move New Logo 2021-May-19-2025-01-26-31-8785-PM](https://docs.move.ai/hs-fs/hubfs/Move%20New%20Logo%202021-May-19-2025-01-26-31-8785-PM.jpeg?width=45&height=45&name=Move%20New%20Logo%202021-May-19-2025-01-26-31-8785-PM.jpeg)

Open main navigation

Close main navigation

- [Move](https://www.move.ai/)

[Move](https://www.move.ai/)

 Welcome to the Move Knowledge Base

- There are no suggestions because the search field is empty.

1. [Move Docs](https://docs.move.ai/knowledge?hsLang=en)
2. [Genesis](https://docs.move.ai/knowledge/genesis?hsLang=en)
3. [Optimising your System](https://docs.move.ai/knowledge/genesis?hsLang=en#optimising-your-system)

# Using Timecode Synchronisation

**Genesis Post** supports processing videos containing timecode metadata. This allows your final tracking data to align perfectly with other capture systems (such as audio, facial mocap, or reference cameras) that shared the same master clock during production.

#### **1. Synchronizing the Clock**

Before you begin recording, you must ensure all hardware in your volume is on the same clock.

- **Master Camera**: All cameras and any external capture systems must be synced to the same master timecode clock at the point of capture. To align the Z Cams with the external clock, connect an LTC source into the master camera SDI timecode port.
- Camera Settings: Open the browser interface for the master camera, head to the Timecode tab, and verify the source is set to External. Ensure that the Project FPS for the cameras is set to the same value as the timecode FPS from your source.
- Tentact Sync Configuration: Set up the device via the mobile app, and either set the Tentacle Sync to the current phone time, or jam it to an existing LTC master clock in your studio.

 

#### **2. Verifying Timecode with FFprobe**

Once setting up your cameras, you should check that your videos contain the correct timecodemetadata. You can use **ffprobe** to check this. Run the following command in your terminal from the folder containing your video to inspect the metadata:

`ffprobe -v quiet -print_format json -show_streams video_name.mp4 | grep -i timecode`

#### Expected output

For Genesis Post to read the metadata correctly, the timecode must be in the following standard format: **`hh:mm:ss:frames`**

(e.g., `"timecode": "08:48:44:10"`)

 

#### **3. Workflow & Output**

1. **Import**: Bring your videos into Genesis Post. 
     1. For more information on this check out this document.
2. **Process**: Submit the takes for processing with the timecode sync method.
3. **Timecode in the output fil**es: Download your .fbx result files. 
     1. Import the resulting fbx file into your engine (Maya, MotionBuilder, Unreal Engine). Because the output files retain the original timecode, you can drop your exported data directly onto a 3D software or video editing timeline, where it will automatically snap to the correct position and sync with any other system's data captured at that same moment.

- [Genesis](https://docs.move.ai/knowledge/genesis?hsLang=en#main-content)

    - [Overview](https://docs.move.ai/knowledge/genesis?hsLang=en#overview)
    - [System Prep & Setup](https://docs.move.ai/knowledge/genesis?hsLang=en#system-prep-setup)
    - [Genesis Live](https://docs.move.ai/knowledge/genesis?hsLang=en#genesis-live)
    - [Genesis Post](https://docs.move.ai/knowledge/genesis?hsLang=en#genesis-post)
    - [Output Data](https://docs.move.ai/knowledge/genesis?hsLang=en#output-data)
    - [Optimising your System](https://docs.move.ai/knowledge/genesis?hsLang=en#optimising-your-system)
    - [System Management](https://docs.move.ai/knowledge/genesis?hsLang=en#system-management)
    - [Release Notes](https://docs.move.ai/knowledge/genesis?hsLang=en#release-notes)
- [Move One](https://docs.move.ai/knowledge/move-one?hsLang=en#main-content)

    - [Move One Pricing](https://docs.move.ai/knowledge/move-one?hsLang=en#move-one-pricing)
    - [Move Platform](https://docs.move.ai/knowledge/move-one?hsLang=en#move-platform)
    - [Move One iOS App](https://docs.move.ai/knowledge/move-one?hsLang=en#move-one-ios-app)
    - [Using your Animations](https://docs.move.ai/knowledge/move-one?hsLang=en#using-your-animations)
    - [Legacy Accounts - App Store Billing](https://docs.move.ai/knowledge/move-one?hsLang=en#legacy-accounts-app-store-billing)
- [Troubleshooting](https://docs.move.ai/knowledge/troubleshooting?hsLang=en#main-content)

    - [Z-Cams](https://docs.move.ai/knowledge/troubleshooting?hsLang=en#z-cams)
    - [Genesis](https://docs.move.ai/knowledge/troubleshooting?hsLang=en#genesis)

[![Chill listening crop-3](https://docs.move.ai/hs-fs/hubfs/1627650260615-1.jpg?width=24&height=24&name=1627650260615-1.jpg "Chill listening crop-3")](http://move.ai)

www.move.ai

<https://www.linkedin.com/company/move-ai/> <https://twitter.com/Moveai_> <https://www.instagram.com/move_ai_/> <https://www.youtube.com/@moveai/featured>

Copyright © 2026, Move AI