Kevin Camp
Forum Replies Created
-
jimmy, if your still working on this, i created an expression based off of dan’s bouncing ball expression on motionscript.com… it seems to work, just paste it in the position expression for the bouncing ball and start adding keyframes for where the ball lands…
BounceHeight = 30;
if (numKeys < 2){ position; }else{ nextKey = nearestKey(time).index + 1; prevKey = nearestKey(time).index - 1; if (time >= nearestKey(time).time){
if (nextKey > numKeys){
freq = 1;
}else{
freq = 1 / (2 * (key(nextKey).time – nearestKey(time).time));
}
}else{
if (prevKey <= 0){ freq = 1; }else{ freq = 1 / (2 * (nearestKey(time).time - key(prevKey).time)); } } posSin = Math.abs(Math.sin(freq * (time - nearestKey(time).time) * 2 * Math.PI)); y = BounceHeight * posSin; position - [0,y]; } you can set the 'bounceheight' as needed. -
owc.com usually has good ram prices, they test their products on mac and certify that it meets or exceeds apple’s standards.
crucial.com is a good source for ram, they actually make the ram chips, not just the modules, so you can be sure that all the ram you buy from them has matching chips. and they will be cheaper than apple.
Kevin Camp
Designer – KCPQ, KMYQ & KRCW -
i was hoping to disable opengl use all together… it’s a feature that can be problematic, and is largely unnecessary.
have you searched the ae archives for ‘vista’? there have been several issues noted with ae in vista, this may be one of them… you might also want to search or post on adobe’s ae forum. if there is a known issue, you should find it there.
Kevin Camp
Designer – KCPQ, KMYQ & KRCW -
i’m sorry, those instruction are for mac os x… sometimes i get my posts mixed up.
i will have to check where windows quicktime components get stored…
Kevin Camp
Designer – KCPQ, KMYQ & KRCW -
if you wanted to make sure that there were no thirdparty quicktime components taht were creating a conflict goto library/quicktime and move all files those files to a folder on your desktop. then goto users/username/library/quicktime and move all those to another folder on you desktop.
leave the system/library/quicktime file alone (unless you know you’ve been putting codecs/components in that folder, then you’l’ wan’t to remove any that you’ve added).
then restart ae and try importing a troublesome file… if it works, then try re-introducing the components/codecs, until you find the bad ones. you can then try to find updates for those and re-install them if you need them.
Kevin Camp
Designer – KCPQ, KMYQ & KRCW -
i’m not familiar with you camera, but if you have the manual, or download it from the manufacturer, you’ll want to look up adjusting either shutter speed or shutter angle.
shutter speed is somewhat dependent on framerate, in that if you shoot 60i, the minimum shttuer speed is 1/60 of a second.. a more ‘normal’ speed would be 1/120 of a second, but many cameras will adjust the shutter speed based on the amount of light available, unless set otherwise. so if you can override the shutter speed a setting around 1/250 or maybe 1/500 would greatly reduce any motion blur.
shutter angle is a bit obtuse is video, but many video cameras have this adjustment. a setting of 180 is considered ‘normal.’ that 180 is essentially half the frame rate, so in the example above it would equate to a 1/120 shutter speed. so a shutter angle of 90-45 would give you an effective shutter speed of 1/250 to 1/500.
Kevin Camp
Designer – KCPQ, KMYQ & KRCW -
yep, you can get a lot of probelms when you upgrade one piece of software that older software needs… if you can, determine which version of qt was recommended for ae6.5, download that version, uninstally the current version and install the old one.
if you are using another piece of software (say, fcp) that requires a later version of qt (but not quite as new as the version you are running) then try the minimum version for that software to see if that helps ae6.5.
Kevin Camp
Designer – KCPQ, KMYQ & KRCW -
you should be able to pre-comp the 3 layers, but then check the ‘t’ box in the modes panel for the overlay layer (it’s between the layer mode pulldown and the trakc matte pulldown).
that should matte the overlay layer to just the visible areas of the underlaying layers, and allow for correct compositng in the main comp.
Kevin Camp
Designer – KCPQ, KMYQ & KRCW -
you can use a the linear() function to try and interpret rotation as position. something like this as the position expression would move a layer as a the 3d ‘rotation layer’ turns on the x and y axis:
x = linear(thisComp.layer(“rotating layer”).transform.yRotation, -45, 45, 0, 720);
y = linear(thisComp.layer(“rotating layer”).transform.xRotation, -45, 45, 480, 0);
[x, y]it takes the rotation values between 90 degrees (-45 – 45 = 90) and plots that value over a 0-720 px (the comp width) horizontally and 480-0 px vertically… you would like to know the camera’s viewing angle so you could use that to define the rotation — in my expression i arbitrarilly used 90, but if your veiwing anlg was 60, the values might be -30, 30.
using this will most likely require some trial and error to get values that will seem natural.
do you think you’d be better off using the 3d camera data on a 3d camera and position your layers in 3d space? you should get more realistic movement in you scene.
Kevin Camp
Designer – KCPQ, KMYQ & KRCW -
if interpret footage says the footage is 960×720 with a par of 1.33, then setting the comp to either the same settings as the footage with par correction enabled in the preview window, or setting the comp to 1280×720 with square px should correct the ‘squeezing’ you are experiencing.
i prefer the later option of dropping it in a 1280×720 square pixel comp… if you need to, you can always create a preset for the size, par and framerate that you are working in, to make it easier to set your comps up.
Kevin Camp
Designer – KCPQ, KMYQ & KRCW