Known limitations

Limitations, as of 0.2.4

1. Windows only right now. There is no Mac build yet, and none is part of 0.2.4.
2. Sony 4:2:2 10-bit footage (XAVC S, S-I and HS, for example from an FX3, FX30 or A7 series camera): tracing needs an NVIDIA RTX 50-series graphics card. On other cards Ball Tracer cannot read these files, and Trace stops with a message. Workaround: convert the clip to ProRes first.
3. Clips whose frame rate really changes can be refused. Workaround: convert the clip to a constant frame rate first.
4. Clips with big moves, zooms, rotation or stabilisation before Ball Tracer can be refused ('the picture was changed'). Workaround: trace first, then stabilise or reframe.
5. The camera clip itself must be on the timeline, not inside a nested sequence or a compound clip. Make Ball Tracer the first effect on the clip.
6. Graphics cards: tested on NVIDIA RTX cards. AMD and Intel graphics are not tested yet.
7. Landings outside the shot are estimated. For an exact landing, place a Landing marker.
8. Very small or fast balls can be lost right after impact. Workaround: add a few Ball Marks along the flight.

Found something else? Report it in our Discord or with Send to Support in Ball Tracer. What changed in each release.