Text Updated by Templater seems to override setFont settings in text.sourceText prop
-
Looking for confirmation on this so I don’t burn my weekend trouble-shooting this further.
A Critical Detail of the Dataset is as follows - Each Row of text corresponds to its own text which is in a different language. As a strict rule implemented via Expressions in the text.sourceText prop, each Row/Language also helps to define the specific Font to be used.
Also, I have Templater Rig, does this mean I cannot use the Spot Check, Replicate, Render and Bot features - these are grayed out.
TIA
-
OK. So … the issue has to do with the Base Number. The Array I set up for font selection, based on the active TSV Row has to be set, based on Templater’s setting which starts at 2 instead of 0.
Changing my Expression to start reading from a Base Number of 2 (instead of 0) fixes the issue perfectly.
-
There is still an issue with reading from the font “MalgunGothic”, “SimSun”, “NirmalaUI”. So … there is still an issue with non-English fonts.
-
Hello,
Could you give us some more information about the Expression that you’re using to determine the font changes in this project? I did some testing this morning with the fonts listed (MalgunGothic, SimSun, and NirmalaUI) and was able to load them without an issue. However, I’m unsure whether the code we’re using is significantly different since I’m not using an Array.
For my test, I brought the font name I wanted to use in on a layer named “font” and then used this Expression:
text.sourceText.style.setFont(thisComp.layer("font").text.sourceText);To reference the text in that layer in order to specify the font in the target layer. Could we try this Expression in the project file in question and see if it’s able to reference font changes made via that layer?
One other quick note about using this method to change fonts in AE. After Effects is very particular about the naming of the fonts in Expressions. For my test, I used the values: “MalgunGothic”, “SimSun”, and “NirmalaUI” to designate the font changes I wished to make. These values were derived by going to the Expression language menu, navigating to Text>Font, and specifying the font I wanted to reference.
Let us know some more about the Expression that you’re using, and we’ll see what we can do to help out.
Thanks!
-
@jeff
Thanks for the the reply, Jeff.Notes -
-
My fontNaming conventions are good - they work outside of Templater and were sourced in the same way you sourced yours fontname list.
-
I am using an Array in a text.SourceText Expression which corresponds to a DropMenu that selects a Language (each language has its own corresponding font) while you are directing your font selection via a link, to a “Targeted” Text Layer.
Below is the structure I currently have, to select THE font associated with a DropMenu selection. The code/logic works if Templater is not part of the equation.
// declare dropMenu with Language Items
const languageDropMenu = comp(“bGEMs - ADJ - ParaLong Text HD1080”).layer(“Controller - Language - Text Input”).effect(“Language”)(1);// display font Array. The font array/list corresponds to the language Array/list above.
const fontsArray = [“FuturaPT-Book”,“Myanmar Text”,“FuturaPT-Book”,“Adobe Devanagari”,“FuturaPT-Book”,“MS Gothic”,“MalgunGothic”,“FuturaPT-Book”,“SimSun”,“Nirmala UI”,“FuturaPT-Book”, “Simsun”,“FuturaPT-Book”,“FuturaPT-Book”,“FuturaPT-Book”,“FuturaPT-Book”,“FuturaPT-Book”,“FuturaPT-Book”,“FuturaPT-Book”];const myFont = fontsArray[languageDropMenu-1];
-
-
Thanks for the update. I did some testing with the Expression snippet from your last post, and outside of adding a line to apply the selected font to the layer (text.sourceText.style.setFont(myFont);), it worked without an issue with Templater. I was able to bring Templater data into the text layer that contained the Expression and then successfully changed the font using the Dropdown Menu Control set up on a null layer.
It’s possible that we might be missing something about how the system is set up that’s causing the issue that you’re encountering. With that in mind, I think we’ll need to get some further information about this project.
Specifically, I think it would be helpful to see some screenshots of the layer that’s using this Expression with the entire Expression text displayed. It would also be useful if we could see a screenshot of the details of the Dropdown layer as well as some examples of how the Data Source is set up. Finally, it would probably help if we could examine the templater.log file for this project to see what data is being brought in behind the scenes.
Since this information could be potentially sensitive, please feel free to contact us directly at support@dataclay.com if posting the requested data in this space would be an issue.
Thanks!
-
@jeff Thanks for the reply Jeff. Unfortunately, I will have to KIV this for a while - I’m on something with a hard deadline.
I will post here when I can get back to the “Font Project” BUT it’s great to know you have no issues getting expected results.
-
@jeff I wrote this in my initial post -
“Also, I have Templater Rig, does this mean I cannot use the Spot Check, Replicate, Render and Bot features - these are grayed out.”A reply will be great. TIA
-
Apologies, I got caught up in the Expressions troubleshooting and overlooked this. Automatic Replication, Rendering, and Spot Check features are only available in Templater Pro and Templater Bot. With Templater Rig, outputs will need to be manually added to the Render Queue, Adobe Media Encoder, or any other processing software that’s compatible with AE.
This restriction is because Templater Rig was mainly envisioned as an editing tool for Templates that would then be processed by either a Templater Pro or Templater Bot setup. Hopefully, that makes sense, but if you have any other questions, please don’t hesitate to let us know.
Thanks!
-
@jeff Thanks for the reply, Jeff.
