Cassius Marques
Forum Replies Created
-
well, can you at least tell us why/what is causing the expression errors? Do the layers resume correct position after you fix them?
Do the expressions link layers to the absolute or relative path? Can that be set? I’ve never used the plugin.
-
Isn’t it all controlled by cineware now? Have you tried it? I’m still with cs6
-
If you have 17gb reserved for AE. It should be using all of that. If its only allocating 4gb you may have something wrong.
some noise effects are indeed slow to calculate, but it shouldn’t be that much.
As to which hard drive to read/write/cache to: the fastest one you got, no matter whereas AE is there or not.
I have no clue about which effect/plugin you are using neither I know much about noise correcting workflow, but I’ll suggest you try a different one.
-
And just to elucidate, earlier in the morning (here in Brazil) you asked but I didn’t had the time to figure out a proper answer to why it happens, so now I’ll try and here it goes. Check this image. It shows the expected behaviour of a real camera. Once you hit that 180º angle on the y axis, you gotta turn the camera around otherwise the whole world would turn upside down.
Perhaps the underlying math in the plugin doesn’t account the fact that we would interpolate frames, or perhaps it does but it chose that “optimal” solution because of some other expcted behaviour that we would never predict.
-
Silly question: Are your memory settings allowing more than 4GB?
-
Damn it! haha. I guess it can only be because AE can do subframe calculations(for motion blur reasons), and between frame 231 and 232 there are still negative values. Once it hits 232 and the expressions kicks in, values change for positive but with still subframe negative values. Expressions must only affect full frames and not for the n*samples subframes generated for the motion blur computation.
That’s my best guess.
-
I can’t understand what you’re after. You’re contradicting yourself.
[Andrés Borghi] “If I lower the quality of the layer to avoid antialiasing so it remains pixelated”
If you try to avoid antialiasing, yes text will become pixelated/aliased.
But then you say:
[Andrés Borghi] “The ideal outcome would be to have the text perfectly pixelated just as the one you’r reading here”
A text rendered by a browser ain’t pixelated (is doesn’t look as it, because you don’t see the pixels) because it is antialiased!
So if you want to allways have a render perfect text, just do as Dave said and check “collapse transformations” for any composition that has a text layer inside.
-
Yes, that logic is correct. I tend to save some expressions on a text file, cause I can never remember the notation without copying/pasting. =P
-
sure, it’s an IF ElSE check.
“a” has the Z rotation value.
It says if “a” is higher than 0 (positive). It will keep “a” as result. Else it will add 360 to “a”.
-
A vague idea yes. Its a matter how the gimbal rotation works when the camera has a target. you can’t pass the 360º angle. You either have to “invert” the Z axis or the other 2.