Paul Connors
1
COW Coin
Forum Replies Created
-
Oops! You’re absolutely right! I’ve just updated that but am getting the same error:
txt1 = "\"" + thisLayer.name + "\"";
txt2 = "\"" + thisLayer.name + " 0" + "\"";
thisComp.layer("csv test - Sheet1.csv")("Data")("Outline")(txt1)(txt2)
-
Hi Walter. Thanks very much for your insight. In the interest of learning something new I’m going to do some digging on the manual-type instructions you provided, but in the meantime, how do you set up groups in Essential Graphics? Is that a CC 2019 feature? I can’t seem to see it in CC 2018. Thank you!
-
Hi Kalleheikki. That is a great suggestion. I just went ahead and tried that and the parented global position is in fact being calculated and used. I think it’s some strange anomaly with the stacking of the expressions. I actually just made two layers for each bit of text. One that is only visible when the global position is greater than 960 and the other that is only visible when the global position is less than 960. While my timeline is much more complicated now it seemed to get the trick done. Thank you for your response!
-
Hi Dan. Thanks very much for your response. I’m running AE 15.1.2. Unfortunately I’m having the same issue with your update. Based on the size of the bounding box it looks like the underlying text generated from the expression is working, but it’s still displaying the base value of the text layer. Interestingly, again, when I turn off the expression on the anchor point the text generated by the expression on the source text is correctly displayed, but now the orientation/position of the text is incorrect.
-
Hi Kalleheikki. Thank you very much for this bit of code. It’s fantastic. I was wondering if you might be able to help me take it a step further. I’d like to distribute the separate lines of text that your code makes onto separate text layers. So the words that fall within the 0-60 characters limit would appear on “New Text Line 1”, the characters that fall within the 61-120 limit would appear on “New Text Line 2”, 121-180 would appear on “New Text Line 3”. Etc. Does that make sense? I’ve tried everything I can think of but just can’t seem to crack it. Thank you!
-
That makes sense. Well, the two lines works amazing! Thank you very much! 🙂
-
Hi. I’m just flying by but figured I’d give my two cents. Perhaps using a sourceRectAtTime along with “height” and “width” for each layer and then using the dimensions of the comp would be a place to start. For example, if your comp is 1920×1080 you’d want the sum of the widths of cells A1+B1+C1 to equal 1920 and the sum of the heights of cells A1+A2+A3 to equal 1080. I’m SURE there are way smarter people than me that might have a better way of doing this though. Good luck!
-
Howdy Dan. Thanks so much for this. It works like a charm! I’m trying to retrofit it to work for three lines instead of two. So, using the original text example of: “Once upon a time there was a princess” that would get split into 3 lines of “Once upon a” “time there was” “a princess”. Is that possible? If so, is it easy to update the expression to work for 3 lines, 4 lines, 5 lines, etc? Thank you!
-
Hi Walter. Thanks very much for your response. Like always it was a major help. The errors looked much worse than it actually was. In the end it being only one comp that was being referenced by expressions only that was causing the issues. I made a note of it, added it to the MASTER comp for reducing and voila…no more expression errors and a seriously clean project file. Thank you!
-
Howdy. Did you ever get an answer to this?