v0.14.4 — the fixture that would have caught all three
examples/sample.fcpxml is spine-based, starts at 0s, and has no connected clips. That shape hid three separate bugs in a single afternoon, every one of them found only by pointing the tool at an actual project.
examples/music-video.fcpxml reproduces all three conditions on purpose:
tcStart="0s"disagreeing with element offsets that begin at 3600s- a 23.98 sequence format followed in the file by a 50p source format
- a spine holding one
<gap>, with all 8 clips connected across lanes -1, 1 and 2
Proven rather than assumed. Reintroducing each fixed bug against it:
| sabotage | result |
|---|---|
| origin forced to 0 | every clip at left:100% |
| last-format-wins restored | 50.0 fps on a 23.98 timeline |
Neither is reachable with sample.fcpxml.
Guard tests assert the fixture keeps those properties, so it cannot quietly drift back toward the shape that hid the bugs. Issue #16 now has something to be fixed against.
Full Changelog: v0.14.3...v0.14.4