> 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/recommended-workflow.md).

# Recommended Workflow

Follow the recommended end-to-end Timeline recording workflow from project preparation and Timecode setup through recording, Take management, replay, editing, and final export.

This page summarizes the recommended end-to-end workflow for Timeline recordings in Grid Studio.

Use it as a practical checklist from initial project preparation through recording, review, Take management, and export.

***

## 1. Prepare the Timeline

Create the Timeline and add a **Parameter Layer** for the recording.

Before continuing:

* set an appropriate **Start Time** and **End Time**
* configure the required **Project FPS**
* select the Parameter Layer that should receive new recordings using the red **R**

The Timeline range should cover the expected recording period, even when a Global Recording Timecode Provider is used.

See **Prepare the Timeline** for details.

***

## 2. Choose the Recording Timebase

Decide whether the recording should use:

* Grid Studio internal timing
* external Timecode

For recordings that require an external time reference, use the **Global Recording Timecode Provider**.

Use an additional Timeline-specific Timecode Provider only when the Timeline Playhead itself should visibly follow external Timecode.

See **Choose the Recording Timebase**.

***

## 3. Verify Timecode and Synchronization

For time-critical recordings, verify the timing setup before recording.

Check:

* the **Timecode Quality Graph**
* the **Interpolated** Timecode signal
* the selected interpolation mode
* the **Time Inspector**
* external synchronization / Genlock where required

The goal is stable Timecode interpolation and a consistent timing relationship between the incoming Timecode and the Grid Studio Process Tick.

See **Verify Timecode and Synchronization**.

***

## 4. Choose the Correct Recording Source

Decide which object actually contains the values that should be preserved.

Be aware of:

* Parent / Child transformations
* relative versus global values
* Filters
* Modifier logic
* Maps
* other processing applied before the final result

If the final processed result is required, create a dedicated **Recording Object** and feed the resolved data into it.

See **Choose What to Record**.

***

## 5. Prepare Camera Tracking if Required

For Camera Tracking, use a dedicated Recording Camera / Object that receives the final global Camera result.

Do not record directly from an intermediate Camera state if Lens Profiles, Tracking Alignment, Parent transforms, Filters, or other processing still affect the final result.

Link any additional Camera or Lens Parameters required for replay or export.

See **Camera Tracking Recording**.

***

## 6. Arm the Objects

Enable Recording on every object that should be included in the Take.

Verify that:

* all required objects appear in the recording target Parameter Layer
* no unintended objects are armed
* the correct Parameter Layer has the red **R**

See **Arm Objects for Recording**.

***

## 7. Run the Final Check

Before pressing Record:

* verify Timeline range
* verify Project FPS
* verify Timecode
* verify synchronization
* verify Recording Objects
* verify armed objects
* disable Auto Save for important time-critical recordings

Once recording starts, keep Grid Studio as undisturbed as possible.

See **Before You Press Record**.

***

## 8. Record the Take

Start recording manually or through a Workflow.

The Recording Block:

* starts when **Start Recording** is triggered
* records changes according to the Project FPS
* ends at the last recorded Parameter change
* is finalized by **Stop Recording**

The Timeline can continue running after recording has stopped.

See **Recording a Take**.

***

## 9. Preserve Alternate Takes

If a new recording overlaps an existing Recording Block, prefer:

**Create New Layer**

when the previous Take should be preserved.

Use **Replace Current Block** only when the previous recording is no longer required.

Rename Takes manually and choose an organization that fits the production:

* multiple Take Layers in one Timeline
* one Timeline per Take
* a combination of both

See **Managing Takes**.

***

## 10. Review the Recording

Perform a quick visual check after every important Take.

Verify that:

* a Recording Block was created
* the Block length looks plausible
* the expected objects contain recorded data

Then replay the Take.

When multiple Take Layers control the same Parameters, enable only the desired Take and disable the competing Layers.

See **Reviewing & Replaying**.

***

## 11. Edit Only if Required

Recording Blocks can be:

* moved
* trimmed
* copied
* duplicated
* rearranged

The edited Timeline arrangement is used during replay and export.

Keep recordings in their optimized format whenever possible.

Only use **Convert all recordings to keys** when individual recorded Keyframes need to be inspected or manually edited.

See **Editing Recorded Data**.

***

## 12. Export the Final Take

Choose the export format according to the destination.

### CSV

Use CSV when raw Parameter values and timestamps are required.

CSV preserves sparse recording data and gaps.

### FBX

Use FBX for supported frame-based animation data.

FBX writes continuous frame data and interpolates across gaps between Recording Blocks.

Not every recorded Parameter type can be represented in FBX, including Lens Distortion data.

### Shield Recording

Use Shield Recording when transferring the complete supported recording data to Unreal Engine through the Stage Precision **Shield** plugin.

Shield preserves gaps and supports both full-Layer and current-Block exports.

See **Exporting Recordings**.

***

## Optional: Automate Recording

If the required recording window is known in advance, recording can be automated through Workflows.

Use **Timecode Events** to trigger:

* **Start Record**
* **Stop Record**

at predefined Timecodes.

See **Automating Recording with Workflows**.

***

## Quick Workflow

For most recordings, the complete process can be summarized as:

**Prepare Timeline → Configure Timing → Verify Sync → Prepare Recording Source → Arm Objects → Final Check → Record → Review → Organize Take → Edit if Required → Export**