Introduction to 3D Text Styles Development

Final Cut Pro 10.2 and Motion 5.2 introduce a new 3D text engine that allows users to save and reuse styles of their own creation.

Developers can use the same technology to distribute their own libraries of 3D Text Styles, packaged in such a way as to appear in their own category inside the Final Cut Pro or Motion UI1).

Much like Motion Templates, each 3D text style is defined by a combination of files on disk. When these files are installed at specific locations in the file system, the corresponding text style appears inside the 3D text style popup menu in the Final Cut Pro and Motion apps.

FxFactory supports a new product type designed to give developers a few important advantages for quickly deploying products for the new 3D text engine:

  • No installer required. When users download your product through FxFactory, our software takes care of creating and maintaining the corresponding directory structure on their system2)
  • Reliable deployment. Common problems are detected and fixed through the FxFactory application.
  • Media consolidation. If multiple text styles reference the same graphic, FxFactory can consolidate the media for you. This operation reduces the size and complexity of your product, making it simple to revise graphics3).
  • Watermarking of trial versions. Provide trial versions of your product even if the underlying 3D text engine lacks specific support for licensing.
  • Product Bundles. You can bundle 3D Text Styles together with a separate set of Motion Templates, allowing you to provide a better user experience: list the styles included with your product under the 3D text style popup menu and provide Motion Templates designed to showcase each text style.

Next step: Create 3D Text Styles Products

This allows users to access custom style libraries with minimal clutter added to the standard UI.
This should be familiar to any developer who has shipped FxTemplates products. The FxTextStyles technology is a further refinement of that concept, with a more sophisticated feature set.
When an asset is shared, you only have one file to update. The changes are propagated to all text styles that reference said asset.