
- Posts: 3
- Joined: Thu Jun 01, 2023 3:25 am
- Real Name: Arpit Rana
Hi Team,
Firstly, I’d like to thank you for the recent addition of the preferred fonts feature—it’s a much-needed and very welcome improvement, especially for those of us working with multiple templates or clients and want to streamline our font selection process.
However, I’ve noticed an issue that might benefit from a tweak in implementation.
Current Behavior:
When we add a custom list of preferred fonts via the new system, Resolve restricts the available fonts in the dropdown to only those on our list. This is great for staying organized.
But if we apply a preset or animation (e.g., from Fusion or Title templates) that uses a font not in our preferred list—even if that font is installed on the system—Resolve flags it as “Missing Font.”
Suggested Improvement:
Instead of entirely blocking fonts outside the preferred list:
Preferred fonts should only act as a filter for the dropdown UI—for faster manual selection.
If a preset uses a font that’s already installed on the system, even if it’s not in the preferred list, it should still be loaded and displayed properly.
The dropdown can still default to showing only preferred fonts, but internally Resolve should retain full font access to prevent preset breakage.
This way, the user benefits from both:
A cleaner, more efficient UI with preferred fonts,
And the reliability of system-wide font access for templates or presets created by third parties.
I hope this gets considered—it would make the feature both powerful and backward-compatible with existing workflows.
Thanks again for the continuous improvements to Resolve!
Firstly, I’d like to thank you for the recent addition of the preferred fonts feature—it’s a much-needed and very welcome improvement, especially for those of us working with multiple templates or clients and want to streamline our font selection process.
However, I’ve noticed an issue that might benefit from a tweak in implementation.
Current Behavior:
When we add a custom list of preferred fonts via the new system, Resolve restricts the available fonts in the dropdown to only those on our list. This is great for staying organized.
But if we apply a preset or animation (e.g., from Fusion or Title templates) that uses a font not in our preferred list—even if that font is installed on the system—Resolve flags it as “Missing Font.”
Suggested Improvement:
Instead of entirely blocking fonts outside the preferred list:
Preferred fonts should only act as a filter for the dropdown UI—for faster manual selection.
If a preset uses a font that’s already installed on the system, even if it’s not in the preferred list, it should still be loaded and displayed properly.
The dropdown can still default to showing only preferred fonts, but internally Resolve should retain full font access to prevent preset breakage.
This way, the user benefits from both:
A cleaner, more efficient UI with preferred fonts,
And the reliability of system-wide font access for templates or presets created by third parties.
I hope this gets considered—it would make the feature both powerful and backward-compatible with existing workflows.
Thanks again for the continuous improvements to Resolve!