George Shubin
Forum Replies Created
-
yes, that was my first take as well, and ultimately that is probably what is going to happen. The problem arises because of the distortion from the lens. The brick line just below the graffiti is curved slightly different then the brick above it, so the lines don’t quite match up. Of course I can bezier distort it to match, but I was hoping that there might be something a little overall I could apply.
Thanks,
George Shubin -
sure, I just trying to do regular NTSC DV using the standard presets from Adobe both in AE and PPro. I’ve tried using the Microsoft DV codec, QT Animation codec, Uncompressed AVI, Uncompressed QT, progressive, lower first, upper first, square pixel, 0.9, 1.2 aspect ratio – these all have the same results.
If you preview them in Media Player they look fine. If you reimport them into an AE timeline they look fine. It is just when they go onto a PPro timeline that they look weird.
Thanks,
George Shubin -
I am wondering if you ever got a solution to this problem? I too have recently discovered this problem with my CS3 PPro footage. It doesn’t matter what type of footage it is – I’ve rendered out uncompressed, animation QTs, DV, whatever, they look great when I reimport them into After Effects. But once they are on a time line they look like crap.
To describe it, at first glace you would assume a field issue, but playing with the field options produces no solutions (with the exception of the ‘Flicker Removal’ option which minimizes the issue but doesn’t solve it (and besides then you have to render out the clip). I doesn’t matter how the original clip was rendered out either, be it progressive, upper first, or lower first it is the same result.
At first I thought it was a codec issue. So I created a new PPro profile to use uncompressed footage. Same issue.
I’m at my wits end on this. If I save a frame out from the timeline it renders these errors and are quite obvious. So it is not just a display issue.
Any help would be appreciated.
BTW – my system: WinXP, 4gig RAM, Matrox RT.X2, Matrox Parhelia APVe display card
Thanks,
George Shubin -
Cool, I’m going to try this. I should be able to play a little better with depth of field using this solution. Particular doesn’t utilize the AE camera DOF. Thanks.
George -
Cool, I’m going to try this. I should be able to play a little better with depth of field using this solution. Particular doesn’t utilize the AE camera DOF. Thanks.
George -
Yes, I did. Thanks for your suggestions. While I’ve not pretty much got the motion of the particles the way I want it, I’m now faced with trying to make the particles look like they are backlit. Also the DOF doesn’t work on the AE camera with particular. Looks like there will be a lot of layering for me is in my near future.
George
-
Yes, I did. Thanks for your suggestions. While I’ve not pretty much got the motion of the particles the way I want it, I’m now faced with trying to make the particles look like they are backlit. Also the DOF doesn’t work on the AE camera with particular. Looks like there will be a lot of layering for me is in my near future.
George
-
Yes, I thought of shooting it practical, but I want to have a camera move in the shot and I was hoping to have that 3D effect with the particles.
-
Yes, I thought of shooting it practical, but I want to have a camera move in the shot and I was hoping to have that 3D effect with the particles.
-
Hey, man I feel your pain. This happens to me every once in a while as well. In fact this just happend to me over the weekend. AFX block everything including my USB mouse, although the keyboard worked so I was able to cancel AFX and reboot. But it gets annoying and I don’t know why it does this. I have noticed that is seems to do it most when I am rendering or working on HD files, but I was working in SD over the weekend and the same thing still happened. AFX takes up 100% of the CPU usage even when it is minimzed and doing nothing.
So good luck to you, and to us all.
George