I'm trying to do some serious linking for a motion template, and have the following problem:
When linking a A.position.Y value to a different B.position.Y-value with Link and then Replace with Source, that works as expeced and B.position.Y will show exactly the same as A.position.Y.
If I, however, link A.position.X to B.position.Y the value is not identical.
While I can somehow work around this, it's a lot more dummy objects with values in it to store and adjust, so I'd love to know, how to apply "correct math" in Motion links.
peteramwiggins wrote: You can add the custom behaviour to offset or multiply another parameter
Well, I'm doing that, ain't I?
I go to for example a Y position of a group, right click and then choose link from the custom behaviour menu. Now I have a link behaviour and drag and drop a different element into the source of the link, and now I can choose which value I want from it. If it is also a Y value, everything works great, if it's an X-value, the Y value of the group I'm replacing will not be the X-value of the other element, but some seemingly random number. 🤷🏻♂️
Or what are you talking about?
The underpinnings of Motion are that all dimensional coordinates are in 0 - 1 format. For your convenience, Motion converts those values to pixel values based on the project settings. So, for a 1920x1080 project, the raw value X is multiplied by 1920 and the Y value is multiplied by 1080. Technically, your linked X/Y parameters ARE equal, but translated. [X 0 is the left edge; Y 0 is the bottom edge].
To deal with the parameter values in Transform Position, you would Scale the link > Position>Y value by 1.7777777 to be able to see pixel equivalents. Going the other way, try 1080/1920 or about 0.5625 to convert in the other direction.
You will run into these disparities a lot using other parameter values when the they are not "like" valued - for example - linking a Numbers Value to the position parameters will display values 100 times the actual 0-1 range (or consider it percent, if you will).