Something strange happens to me recently. I have a project with a lot of text-inserts and various fonts used in those. When I open up the project all titles using a specific font (in this case Proxima Nova) were garbled gibberish. The font is activated and available to other apps (including Motion) and can be used normally there, but not in FinalCutProX. I changed the font to something else — the text appeared normal. When I change it back to Proxima Nova it's a jumble of letters again. It seems only "Proxima Nova Regular"and Bold are affected.
This happened to me in 10.3.4 and now in 10.4.0 too.
I do not use Font Book for font management but rather a font manager named "Suitcase Fusion". It does not mark the font as corrupt though and as I said it works fine in Adobe products and Apple Motion, which uses the same type engine as FinalCutProX does. Very strange.
Font Book is vital, and it tracks every font on your computer, regardless of what other app you use for simple management. Use it, verify it, or we can't proceed. First step to troubleshooting a third party font is have Font Book verify it.
I have FontBook installed of course, but it only "sees" fonts that are installed at one of the three default locations (~user/Library/fonts, /library/fonts and /system/library/fonts. Suitcase Fusion can activate fonts out of it's own repository when needed, and can synch fonts across machines — which is what we use it for here at the facility. So If "Proxima Nova" is activated out of Suitcase, Font Book does not see it. To rule out "Suitcase", I moved Proxima out of Suitcase to the desktop, so wether Suitcase nor Font Book sees the font. Now things get even stranger. FinalCutProX still sees "Proxima Nova" even though EVERY OTHER APP on the machine does not see it anymore. I restarted FinalCutProX, but it could still see "Proxima Nova" and yes: I did not look at rendered Titles but could still edit them in a font that theoretically was not installed anymore. I created a new Library, but still "Proxima Nova" was available to me in FinalCutProX,even though it was deactivated. FinalCutProX must have an internal font cache somewhere and there is a corrupted version of Proxima in there — hence my problems. I used Suitcase Fusion's "clean font cache" feature and rebooted the machine — Proxima Nova ist still available in FinalCutProX. I am utterly confused now.
I have likely found the culprit and it is not Suitcase Fusion nor is it a bad font it's FinalCutProX itself!
A little explainer why something Suitcase Futon is necessary: We have the need to properly archive and share a great number of fonts we get from clients and/or license for them across machines (some of which use FinalCutProX, some ADOBE or other creative software packages), keep the up to date and organise them by client, job and version. Suitcase Fusion also auto-activates fonts so that not all fonts need to be loaded at all times, which saves RAM and resources on the machine. If you only dabble in typography or use standard fonts and maybe a few extra, something basic like Fontbook might do the trick, it does not an my company. It's a bit like the arguing that no one needs FinalCutProX, because there's iMovie, which can also edit.
But back to the problem:
FinalCutProX does have its own fonts INSIDE it's application bundle(!):
Final Cut Pro (right-click and Open Bundle) /Contents/Frameworks/Flexo.framework/Versions/A/Resources/Fonts/Proxima Nova.ttc
There are also a bunch of other fonts there, which are not seen by Font Book, Suitcase Fusion or ANY other App other than FinalCutProX.
I can only speculate why this is the case but I'm pretty sure that's the reason why my extra copy of Proxima Nova activated by Suitcase Fusion (or even FontBook for that matter) might clash and cause the troubles I've been describing.
I have also found ANOTHER copy of Proxima Nova:
system/Library/PrivateFrameworks/Slideshows.framework/Versions/A/Resources/Content/Fonts/Proxima Nova Bold.ttf
Again I have no clue why it's there, but it's both on my MacBookPro and on my freshly installed MacPro. I guess font management continues to be a mess on the Mac.
FWIW...there used to be an issue using multiple font managers on a mac and it was recommended not to use any manager alongside Font Book. Not sure if Sierra or HS works differently or maybe even El Cap, but back in the days of Yosemite and Mavericks multiple managers were a no-no.
Yes I did. Just look at my last post. FinalCutProX has a number fonts INSIDE it's application bundle that only it sees. When another font with the same post-script name is added on user/system or OS level FinalCutProX seems to get confused. Nothing to do with font managers at all.