Framerate

Overview

Pixelrush represents framerate as a rational fraction (for example, 30000/1001 or 25/1) and uses it to interpret timecode, decide how cuts round to frame boundaries, and stamp every cut in the export.

How framerate is read

Framerate can come from the signal itself or be set manually:

• Signals with framerate metadata. Pixelrush reads the framerate automatically. Examples include MTC streams and other timecode signals whose framing includes framerate.
• Signals without framerate metadata. You set the framerate manually in Pixelrush. LTC is the canonical example: the protocol has no framerate field, so Pixelrush cannot infer it from the signal.

The framerate Pixelrush uses must match the framerate of the actual signal it's reading. A mismatch produces frame-shifted timecodes in every export that uses that source.

Related features

• Recording sessions — the session inherits a framerate from its chosen timecode source.
• Timeline exports — the export carries the framerate so your editor interprets timecode correctly.

Supported hardware

• Blackmagic ATEM — framerate read automatically from the device.
• Atomos UltraSync ONE — framerate set manually.
• Tentacle Sync — framerate read automatically over MTC; set manually over LTC.
• Other LTC-compliant devices — framerate set manually.
• MTC-compliant devices — framerate read automatically.