Sam Moulton
Forum Replies Created
-
the movement might also be at a critical panning speed. anyone that’s shot 24p or film for that matter knows that there are certain speeds where motion just stutters. it’s called stroboscopic effect and the only way around it is to change the speed of the move or increase the blur.
-
puppet tool… huge to me
color management, also huge
complete integration with other apps like Photoshop layer styies … really huge
expressions to shape vertices, very huge
expanded 32 bit effects very huge
clip notes another biggie
3d for individual characters…way big
and I love the idea of Brainstorm, but then again, I also love Apple’s Motion. Never got so many ideas so quickly, also never used anything from motion just the way it comes in, like I’ve never used any of AE’s templates without some major editing, but I probably start with one about twice a week.
Better flash integration – really excitingand these are just things that I’ve seen at https://www.adobe.com/products/aftereffects/
I can’t wait to get my hands on it.
-
yes, it’s probably coming from the detail setting on the camera. too much sharpening. It’s a pain to deal with.
-
it’s most likely that the image needs to be interpreted as square pixels so that it looks oval in the composition and correct on tv
-
i’ve been following vista development for a while now and it seems like there’s about 50 million lines of code that were being rewritten as late as 3 months ago. There’s lots of display adaptors that just won’t work on vista, and a ton of other problems. It does not surprise me that lots of developers, not just Adobe, are not jumping on the free update for vista bandwagon. I’ve even heard reports that MS Office 2000 doesn’t play well with vista and that you’ll have to pay for an upgrade if you want word, powerpoint, and excel to work well.
-
I always use cmnd option shift H and not f… if there’s a mis match in scan lines or any other size, F will distort, h fits the layer to the width and preserves the pixel aspect ratio. I think it was Chris Meyer that gave me the idea. He said, at least I think it was him, that he never uses fit, only fit to width. You can get there from the the layer>transform window.
-
I’ve seen a test somewhere on the cow that showed two resolution charts, one scaled to 90% and one at 100%. One way you lost horizontal resolution, the other vertical. I’ve always worried about scan lines and how horrible they look when things are not right so I go for the 648 X 486 route most of the time for full screen artwork. I don’t like the horizontal edges to go soft. I really don’t think there’s much of a difference. I really don’t like scaling up D1 video to fit in 720 X 540 comps because of the scan line problems that can happen either.
I found the thread. You can see the difference by dragging the movie control between 90 and 100%. I made my decision by looking at the lines of text as well as the charts. However, most of the time my graphics are moving around so there’s really no point to worrying about the 90 or 100% scale for graphics rule anyway.
https://www.creativecow.net/forum/read_post.php?postid=107196265377204&forumid=50&archive=_2003
-
Sam Moulton
March 19, 2007 at 3:10 pm in reply to: How do you create water surface without plug-ins?fractal noise.
There’s a bit in the Adobe book Studio Techniques and Chris Zwar did a tut where he showed a water example.
-
Thanks…. This opens up a bunch of new ways to use the slider that I have wanted to do for a while.
-
btw… doesn’t work with angle control either. It’s really weird. I’m usually pretty good with expressions and java in general but I can’t figure out why this expression is generating an error with the slider control and angle control supplying the numbers and doesn’t give the error when you use either of the point control values [0] or [1].
There must be something in the way the different expression controls generate numbers, or I’m missing something else…