Jonas Espinoza
Forum Replies Created
-
Jonas Espinoza
September 16, 2009 at 1:19 am in reply to: workflow ? – animate a string that morphs into a handful of shapessomething like this
[URL=https://img38.imageshack.us/i/examplev.jpg/][IMG]https://img38.imageshack.us/img38/3761/examplev.th.jpg%5B/IMG%5D%5B/URL%5D
-
i knew it was somewhere, thanks!
i could probably set up a nice expresso null to control a bunch of these if it came to it…
one more question: in a MoGraph cloner sittuation, could i stagger these by putting these into the multishader? would i use index or brightness? how would i have an effector only offset the start times of the animated texture?
thanks
-
i knew it could be done!!
thanks much
i love checking shots out in colorista so i know if i can tolerate them in the edit…
-
thanks again dan!
however, I have a few followup questionswont changing seed just make it pop to another value every second?
is there any type of noise, kind of like a wiggle that evolves more than pops to another value for more organic movement? i guess im just into learning about what i can do with noise, since ive found noise to be super useful in C4D xpresso setups
and what exactly does the math.floor element do?
btw – am working my way through “learning processing’ its really helped me understand some more about how java works an an environment where i can see what i’m doing, but still reliant on code. good stuff
-
Jonas Espinoza
September 5, 2008 at 10:33 pm in reply to: wiggle frequency on a animated slider is jerkythanks so much
so a slider for amplitude and time then, makes sense
also is there a way to limit the wiggle to a certain range?
as in wiggling opacity, to have it be between say 0-60%
-
thanks you, that helps a lot
so in expressions language:
Layer1.toWorld(x,y,z)
within the () are the layer-space values being translated “toWorld”
i guess i wrongly thought to always have the value being fed to the “toWorld” coming to the left of it
-
L = comp(“Pre-Comp”).layer(“FOLDING SIDE”);
CL = thisComp.layer(“Pre-Comp”);
CL.toWorld(L.toWorld(L.anchorPoint));can i ask about the coding of this?
I’m a little confused, within the parenthesis you get a 3-value for the world location of the anchor point in the pre-comp, but from that, how does that array interface/translate with the last statement “CL.toWorld”
why couldnt you just take “CL.toWorld(L.anchorPoint)”
if anyone gets to this, thanks
-
i do have some different pulls/moves going on different null layers
im just perplexed that all there is is the speed graph, when it would make sense to have some kind of better way to smooth the in and out of a keyframe. the speed value handle doesnt work the same way i would expect bezier handle editing of keys – even the older versions of AE have this
i think in version 8 no less that this shouldnt be a problem!
this functionality, unless someone tells me different, feels very much like an iApp
-
HD 720 29.97
we are exporting a lot of ProRes stuff, but that doesnt make a diff on in-comp ram previews does it?
am in the process of checking RAM right now
this kind of response sucks, which you guys know is half of the importance of having a fast machine – renders themselves are impressive, but it just feels like this thing has flaky memory
also – should my pairs of memory be like this? (system profiler)
RISER A – 1 1GB
RISER A – 2 1GBRISER B – 1 2GB
RISER B – 2 2GB