Help with a spate of Font Problems

1) other users must install the same fonts used in a template in order to function exactly the same. Font Substitution is a cornerstone of Macintosh font management.

2) Some fonts are designed specifically to create a design more than have typographic characters. I've created dozens of them. All of these fonts validate perfectly. Most of them have no character width and when typed in sequence, seem to overwrite the same space — but they're like puzzle pieces that fit together. Poorly designed fonts of this sort will use the A-Za-z character spaces with non-character shapes. There is also the possibility that the fonts were designed for other operating systems (Windows, Linux, etc.) and use a different encoding — there are some encoding variations the Mac simply will not deal with correctly. There is also the possibility that a font is designed for a specific foreign language (to U.S. English) and encoded for a different type of keyboard altogether — these can usually be fixed by changing your keyboard preference.

If you validated the fonts in Font Book, it would have warned you of duplicate fonts (type [.otf, .dfont, .ttc, .ttf etc.] doesn't matter]).

If you are going to be requiring the use of specific fonts in your templates, then you need to direct users to where they can obtain the font (or provide it if you have the license to do so) and direct them to install it which requires restarting Motion or FCPX to use it.

Haven't installed Mojave yet, but I seriously doubt that's the issue.

I have no idea what you're talking about — installing for FxFactory? Why would you do that? Are you making effects for FxFactory?? If so, then that's something completely different and you shouldn't be installing the fonts in Font Book (although, usually, Mac OS differentiates between "resource fonts" and user installed fonts.)

What are the names of the specific fonts you are having issues with?

I have no problems with Alex Brush or Copse which I have installed. I don't have Almendra or Kamera. Almendra is one of the Google fonts so I'm pretty sure its been vetted. Bebas Neue is one of the provided fonts in Motion AND Final Cut Pro X (https://fcpxtemplates.com/fonts-inside-final-cut-pro-x/) so everybody who has a copy of either one of these apps has it available for use inside Motion and/or FCPX. To make it useful system wide, follow the instructions on the linked page. You can install *copies* of these fonts in Font Book for system-wide use but you *must* leave the originals installed in Motion and FCPX. There will be no conflicts.

There MAY be conflict if you try to install Bebas Neue downloaded from another online resource. There are several available to get it from and that does NOT guarantee its the *same* version Apple used for Motion/FCPX. Font Book would have allowed you to install the font without reporting a duplicate conflict. [Resource fonts do not show up in Font Book.]

I recommend uninstalling Bebas Neue from Font Book, then digging out a copy from Motion and installing *that version* into Font Book for system-wide use so you will have the exact same version installed. If you do not need Bebas Neue for any other application then don't bother doing this — just remove it from Font Book. You can be assured that this font *IS* available to all users of Final Cut Pro X (unless Apple has different versions for different countries, but all I know about it is that Apple has different language translations for menus and such for the base application.) I design a lot of my templates with the "FCPX collection" set of fonts only and letting the end user choose any font *they* have installed once they apply the template to the storyline. This ensures that the template will function properly when first applied.

You cannot depend on what any given end user may or may not have installed on their systems. The "resource fonts" inside FCPX/Motion guarantee that at least those fonts will be available.

FxFactory handling of fonts: you are correct — the FxFactory app makes sure that the fonts will be applied so that the end user doesn't have to manually install the fonts themselves. Whether or not they are literally resource fonts — I don't know — I don't use FxFactory and won't have it installed on my system so I don't really know how they handle this feature (whether or not they even check for duplication errors, etc.). Their product installs software in locations other than the Apple recommended locations. For Motion templates specifically, those templates are installed in Macintosh HD/Library/Application Support/Final Cut Pro/Templates/... So I would hazard a guess that the fonts you supply for FxFactory templates you create would be placed in Macintosh HD/Library/Fonts/... in other words, the system "global" areas and not the Apple recommended User account areas.

If you're having font problems, you might recheck your font collection — you might also want to check what FxFactory has been up to behind the scenes (check your global fonts vs your user fonts — you may have to do more research on how FxFactory installs fonts.)