Axis vs Cartesian Priority¶
Playlists: Flair 7 Training Videos, Cinebot Mini/Max & Flair 7 Training
Related Issue: Carts Priority - Adjust Track/Base To Preserve Camera Path
Related Issue: Unexpected Large GOTO When Back-Running a Move — Cartesian Convert Trick
Related Issue: FBX Import — Waypoint Axis Positions Don't Match Run Positions (Carts vs Axis Priority)
Related Issue: Cartesian Offset Shortcut Changed from Flair 6 to Flair 7
Related Issue: Carts Priority Hides Pan Flip - Use Axis Graphs and Flip Pan Axis
Related Issue: Scaling Move Flips Camera Upside Down - Initialize Scaling
Related HOW TO: 1-Point vs 2-Point Scaling — Complete Guide
Searchable transcript: Open full transcript
AI Summary
A video explaining the difference between Axis Priority and Cartesian Priority in Flair.
For operators using this as a reference, the main focus is move programming, target tracking, and track calibration. It should help when deciding which Flair workflow, robot behaviour, or setup area is relevant before opening the full video.
The practical setup context is that hardware referenced includes PRECISION_TRACK. This helps connect the video to the rig, accessory, software environment, or workflow label an operator may already be working with.
The chapter links below provide 8 timestamped jumps into the main setup, demonstration, and workflow moments, making it easier to go straight to the section that matches the issue or task being investigated.
Chapters
- 00:16 — fully understand it. Flare when you create a move stores the
- 01:01 — track is because the track is what we
- 01:47 — Okay. But my track if I move it
- 02:34 — adjust the move. But if I just adjust it
- 03:25 — >> okay, and now I go into cartisian control and adjust my track.
- 04:12 — Now if I now adjust one of these, let's say I move my lift up for whatever
- 05:19 — convert these back into axes using this new track value.
- 06:49 — So this is my move.