Skip to main content
Moritz Janknecht
Participant
November 2, 2022
Answered

Mogrt in Premiere wont calculate Expression in Export

  • November 2, 2022
  • 1 reply
  • 302 views

Hey everyone,

I just realised that when I export a project using my mogrt-lower third the elements wont scale properly, though they seem to be working perfectly in Premiere and the origin AE-Project.

Left: In Premiere
Right: After Export

 

 

 

Both After Effects and Premiere are up to date (23.0), and the error occurs on several Windows 10 based systems.

The yellow box scales according to the text size. This is the used expression for rectangle path size:

var s=thisComp.layer("Instagram_Text");
var w=s.sourceRectAtTime(s.outPoint).width;
var h=s.sourceRectAtTime(s.outPoint).height;

[w+thisComp.layer("Slider Control").effect("Padding y")("Slider"),85.6+thisComp.layer("Slider Control").effect("Padding X")("Slider")];

 The expression for the position works similar:

var s=thisComp.layer("Instagram_Text");
var w=s.sourceRectAtTime(s.outPoint).width/2;
var h=s.sourceRectAtTime(s.outPoint).height/2;
var l=s.sourceRectAtTime(s.outPoint).left;
var t=s.sourceRectAtTime(s.outPoint).top;

[w+l,-29.6];

Any idea how to fix this issue?

This topic has been closed for replies.
Correct answer Mylenium

You are referencing the out point, which simply won't evaluate in your triple-nested scenario. This is even mentioned in the docs somewhere if I'm not mistaken. You need to use a different methodology like dialing in the value with a slider that is actually part of the graphics template or enforce a continuous evaluation on the values themselves with valueAtTime().

 

Mylenium 

1 reply

Mylenium
MyleniumCorrect answer
Legend
November 2, 2022

You are referencing the out point, which simply won't evaluate in your triple-nested scenario. This is even mentioned in the docs somewhere if I'm not mistaken. You need to use a different methodology like dialing in the value with a slider that is actually part of the graphics template or enforce a continuous evaluation on the values themselves with valueAtTime().

 

Mylenium 

Moritz Janknecht
Participant
November 4, 2022

Thanks a lot, that seems to have done it.
I must have skimmed over that part of the documentation.