> For the complete documentation index, see [llms.txt](https://stage-precision.gitbook.io/grid/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://stage-precision.gitbook.io/grid/timeline/timeline-recording-and-export-guide/choose-the-recording-timebase.md).

# Choose the Recording Timebase

Choose between internal timing, Timeline Timecode, and the Global Recording Timecode Provider, and understand which source controls the Playhead and which source defines recording timestamps.

Before recording, decide which time source should be used for the Recording timestamps.

Grid Studio can record using its internal Timeline timing or use an external Timecode source.

For recordings that need to match other systems, the **Global Recording Timecode Provider** is the recommended external time reference.

***

## Free Run

If no external Timecode is required, the Timeline can simply run using Grid Studio's internal timing.

Start the Timeline at the desired Playhead position and press **Record**.

<figure><img src="https://1761958297-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDcGqBEYUYkl2mQzGbOue%2Fuploads%2Fyepeoo0Kq3HhijtFrjG4%2Fimage.png?alt=media&amp;token=521aa100-e1bc-4540-8853-b60a01b1e318" alt=""><figcaption></figcaption></figure>

The Playhead starts from its current position and continues using the internal Timeline timing.

This is suitable when the recording does not need to align with an external system or shared Timecode.

***

## Global Recording Timecode Provider

For recordings that require external Timecode, use the **Global Recording Timecode Provider** in the **TimeManager**.

The Recording Provider defines the timestamps written into recorded data independently from the Timecode configuration of the individual Timeline.

Once configured, the same Recording Timecode Provider can be used for recordings across different Timelines.

### Configure the Global Recording Timecode Provider

1. Click the small **TC** indicator in the top bar, next to the FPS display.
2. In the Inspector, enable the **Recording** option.
3. Select the desired **Timecode Provider**.

The selected provider is then used as the global timestamp source for Timeline recordings.

<div align="left"><figure><img src="https://1761958297-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDcGqBEYUYkl2mQzGbOue%2Fuploads%2FlMcsjHOrZ0KeivDiXqw9%2F4bwN1UGzqp.gif?alt=media&amp;token=3d764532-0b68-498b-8cec-e73a3cf5f505" alt="" width="379"><figcaption></figcaption></figure></div>

### Why use the Global Recording Provider?

The Global Recording Timecode Provider is specifically used as the time reference for recording.

It provides several advantages:

* recording timestamps are independent from the individual Timeline configuration
* the same provider can be used across multiple Timelines
* recording is not limited by the visible Timeline Timecode range
* the Timeline itself does not need to be driven by the same Timecode source

{% hint style="info" %}
For recordings that need an external time reference, using the **Global Recording Timecode Provider** is the recommended setup.
{% endhint %}

### Timeline Display

The Global Recording Timecode Provider does **not** drive the Timeline itself.

This means that the Timeline Playhead and Current Time display do not automatically follow the Recording Timecode.

The provider is used as the timestamp source for the recorded data only.

***

## Timeline Timecode Provider

A Timeline can also be driven directly by an external **Timecode Provider**.

In this configuration, the incoming Timecode controls the Timeline itself.

<div align="left"><figure><img src="https://1761958297-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDcGqBEYUYkl2mQzGbOue%2Fuploads%2FcmNO3hQBAgQSgNbkqsm4%2Fimage.png?alt=media&amp;token=51209c92-f889-46ee-9454-378221b3c8d7" alt="" width="360"><figcaption></figcaption></figure></div>

This means that:

* the Playhead visibly follows the external Timecode
* the Timeline Current Time follows the external source
* recording takes place at the Timeline's current time position

This can be useful when the operator needs to see the Timeline running in direct synchronization with the external Timecode.

### Timeline Range

When using a Timeline Timecode Provider, make sure that the configured **Start Time** and **End Time** include the complete expected Timecode range.

<div align="left"><figure><img src="https://1761958297-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDcGqBEYUYkl2mQzGbOue%2Fuploads%2FJz1OMtq1oqUo0mtHYoep%2Fimage.png?alt=media&amp;token=43943121-2926-4a67-8c78-c6676dc681de" alt="" width="360"><figcaption></figcaption></figure></div>

For example, if the incoming Timecode is around:

`01:00:00`

but the Timeline only covers the first five minutes, the external Timecode is outside the valid Timeline range.

{% hint style="warning" %}
When recording from a Timeline-driven Timecode source, always make sure the Timeline range covers the complete expected recording period.
{% endhint %}

***

## Using Both Timecode Providers

The Global Recording Timecode Provider and a Timeline Timecode Provider can be used at the same time.

In this setup, the two providers have different responsibilities.

### Timeline Timecode

The Timeline Timecode Provider controls the visible Timeline and Playhead.

### Recording Timecode

The Global Recording Timecode Provider defines the timestamps written into the recorded data.

The two Timecodes do not have to be identical.

For example, the Timeline can visibly follow one Timecode source while the recording itself is timestamped using a different Global Recording Provider.

When both are configured, the **Global Recording Timecode Provider has priority for recording timestamps**.

***

## Recommended Setup

For an externally synchronized recording:

1. Configure the **Global Recording Timecode Provider** as the recording time reference.
2. Configure a Timeline Timecode Provider additionally only if the Timeline and Playhead should visibly follow external Timecode.
3. Make sure the Timeline Start and End range cover the expected working range.
4. Verify the quality and synchronization of the Timecode before starting the recording.

The next section, **Verify Timecode and Synchronization**, explains how to check the incoming Timecode before recording.