[Ben Wolfinsohn]

oh yes. i know how to do that well. but i just needed to use the motion tracker to track moving pixels in another comp. so not possible then?

thanks!

[Ben Wolfinsohn]

i’m having all the same problems you are having. can’t snap with cut tool. I can’t figure out how to snap to the current in or out point. pitch thing sucks. and can’t figure out how to copy everything within the in and out points of the timeline ether. any luck on any of these working for you?

thanks

[Ben Wolfinsohn]

got it. yeah, doing any of those helped.
thanks!

[Ben Wolfinsohn]

thanks! wonder how that even got changed like that if i was the one who created the doc and never used that feature before.

[Ben Wolfinsohn]

i have 16 gigs installed, but could get 32 if it will help. and how much does graphics card help too? is it best going with the best card or more processors or both?
thanks!

[Ben Wolfinsohn]

works great! just had to make all the number after the “>” all be 1.
thanks!

[Ben Wolfinsohn]

maybe i can explain a bit better what i’m trying to do –

I have 6 null layers, 1 though 6, with sliders in them.
I have a 7th null that has a slider.
when null 1 has a value greater then 1 in the slider it forces the 7th null to go to a value of 1
when null 2 has a value greater then 2 in the slider it forces the 7th null to go to a value of 2
and so on down the row….

thats what i need if that makes sense.

thanks!

[Ben Wolfinsohn]

i thought i got it below, but it gives me an error – getting an error of – invalid numeric result (divide by zero?)

slider = thisComp.layer(“all head-body contols view 1”).effect(“turning”)(“Slider”) > 1;
comp(“body-head together comp Pre-comp 1”).layer(“Null “+ clamp (parseInt(slider,10),1,8)).transform.position;

[Ben Wolfinsohn]

slider = thisComp.layer(“Null 5”).effect(“Slider Control”)(“Slider”);
thisComp.layer(“Null “+ clamp (parseInt(slider,10),1,4)).transform.position;

one last thing on this one regards to the above-

instead of the slider on null 5 telling it which null it should follow, what if i had 4 more nulls, each null had its own slider, the nulls were called null 6 though 9, and when the slider on null 6 was > 1 then it would follow the position of null 1, and when the slider on null 7 was > 1 then it would follow the position of null 2 and so on all the way to null 4. does that make sense?

thanks!

[Ben Wolfinsohn]

yeah, i’ve been on 1/4 res previews. I guess I just always assumed that once 1 frame is rendered and its ready to move to the 2nd it just saves the image to ram as an image. that no matter what amount of math was needed for the frame, once done with the frame a frame is still just a frame and it doesn’t really matter. but maybe not the case? and no way to save the preview to disk instead of ram?