Getting Started: Flair to Unreal Engine — Plugin Options and First Steps¶
Summary¶
There are two primary methods for sending live camera tracking data from Flair to Unreal Engine for virtual production (LED volumes, XR stages, previz):
- OSC output from Flair — sends camera XYZ position and rotation over UDP. Simple, built-in to Flair, but OSC in UE4.26+ has known issues (broken in 4.26 beta; see related issue).
- Rite Media LiveLink plugin (community-developed, GitHub: KevinRiTE/RiTE_MRMC_LiveLink) — a dedicated Unreal LiveLink plugin that connects to Flair's FreeD or 50Hz XYZ data stream. The more robust option for production use. Port 55535 by default.
For new setups in 2023 and beyond, the Rite Media plugin on UE5 is the recommended path — setup takes approximately 10 minutes following the README. For older UE4.27 installations, the plugin requires manual recompilation as a C++ project.
Community Guidance¶
[RESOLVED] Two Integration Methods: OSC and Rite Media LiveLink¶
Community consensus
Option 1 — OSC (built-in): - Enable FreeD/OSC output in Flair: Output → FreeD/OSC → configure IP and port - In Unreal: add OSC plugin, configure OSC receiver to match Flair's output IP/port - Limitation: OSC was broken in UE4.26 beta; reliable from UE4.27 onward - No additional plugin required
Option 2 — Rite Media LiveLink plugin: - GitHub: KevinRiTE/RiTE_MRMC_LiveLink - Connects to Flair's 50Hz XYZ data output (not FreeD) - Default port: 55535 - Provides LiveLink source in UE — camera tracking data available via LiveLink Controller - UE5 version requires no recompilation — follow the README for 10-minute setup - UE4.27 version requires a C++ project (Blueprints-only projects cannot compile plugins)
confidence_score: 0.92
[RESOLVED] MRMC Forum for Virtual Production Resources¶
Community
The MRMC community forum has a dedicated virtual production section with setup guides, plugin links, and operator reports:
- VP overview thread: https://talk.mrmoco.com/c/virtual-production/
- FreeD output setup: covered in the Flair manual and forum VP section
- Rite Media plugin Q&A: active thread with setup tips
confidence_score: 0.88
[INFORMATIONAL] Flair Data Output Protocols Summary¶
Community
Flair supports multiple data output protocols for tracking:
| Protocol | Description | Typical Use |
|---|---|---|
| OSC | Camera XYZ + orientation over UDP | Unreal (pre-4.26 or 4.27+), TouchDesigner, etc. |
| FreeD | Industry-standard tracking protocol | Disguise, Notch, LED processors |
| 50Hz XYZ | MRMC proprietary, 50 samples/sec | Rite Media plugin |
| Sync XYZ | Genlock-synchronised output | LED wall (Brompton, etc.) |
For LED volume work requiring genlock synchronisation, Sync XYZ is the output protocol — it is timed to the genlock signal rather than internal 50Hz clock. See LED Wall Genlock Setup.
confidence_score: 0.90
Related Issues¶
- See also: Rite Media LiveLink Plugin Setup — IP, Port, Step-by-Step
- See also: FreeD / OSC to Unreal - "Receiving" Shows But No Camera Data
- See also: OSC Broken in UE4.26 Beta — Extract 4.25 OSC Code
- See also: Rite Media Plugin for UE4.27 — Manual C++ Recompile
- See also: Rite Media Plugin for UE5 — 10-Minute Setup
- See also: CRITICAL: Unreal/Disguise Network Traffic Can Interfere with Robot
- See also: FreeD / OSC to Unreal — Setup
- See also: FreeD Focus Units - Transmitted as 0-1 Normalised Value
- See also: FBX Export from Flair to Unreal - Z-Up Issue, 90 Degree Parent Actor, Reduce Keys
Related Tutorials¶
▶ 01:02 — Camera tracking sends position/orientation data to the virtual world in real time
▶ 01:48 — Live tracking latency vs motion-control pre-programmed data