Why don't my fonts load on export?

[unknownsailor]

Hi,

I'm getting pretty tired of this issue. I create my titles and lower thirds using specific fonts. They display as expected. Then after rendering, a default font has replaced them. This is especially annoying as my preferred fonts are sans serif yet the replacement font is serif.

If I catch this in time, I end up just replacing all my lower thirds and subtitles with Aerial, which is a pretty poor workaround.

Why does Premiere randomly switch my fonts, and why should it do this upon export?

TIA

[R Neil Haugen]

Do those fonts show in the Creative Cloud Desktop app's Fonts tab?

[Ann Bens]

Look for your font on the web and install in your OS.

[Warren Heaton]

This is unusual and unexpected.  The font being used while working in Premiere Pro should remain active while exporting.

Which version of Premiere Pro is this happening with and under which operating system?  Also, what is being used for font management?  

If you're exporting with Adobe Media Encoder, what happens if you export using Premiere Pro?

If you are not able to get the font to remain active, I would consider promoting the Graphics to Source Graphics, exporting them from the Project panel or Bin panel as still images with an alpha channel, and then replacing the use in your Timeline.  Another work around would be to create the titles in a layered Photoshop document and then save them as PNG files for use in Premiere Pro.  That's more work than should be necessary, but will maintain the appearance of the text.

[unknownsailor]

Hi. Yes, they show as 'in Adobe and other local apps'. I have a few that say 'a font could not be added due to a conflict' when hitting the recycle button, but these are not the fonts I am having a problem with.

[unknownsailor]

Hi. They are already. Unless I'm reading this incorrectly, Myriad Pro (one of the problem fonts) is installed locally:

[unknownsailor]

Sorry, I normally include this info. Pr is 24.2.1 (build 2) and the OS is Windows 10. I've had to go down the PNG route previously and it is a long-winded work-around!