[Dino Juarez]

Actually, I misunderstood your suggestion. So the precomping DOES work. I put the blur in the PRECOMP layer, then applied the mask in the second comp and that did the trick. Thanks.

[Dino Juarez]

I tried to precomp but that doesn’t work either. I just think masks can’t “mask” a blur. I guess I have to use a track matte.

[Dino Juarez]

I already sort of just did what you suggested. I ended up using a script called Demo Palette.jsx which among other things, allows you to scale an entire comp up. So, I applied this script to all 5 of my comps (my actual project was a bit more complex than the scenario I described to you – but I wanted to just give you the basic problem).

Then I had to go back in and reset some of the scale properties on some of the layers to 100% (the script sized them up to 222%). It actually did not take that much time, but it still seems to me that the cont. rasterize button is problematic.

I would be curious to know from Adobe as to why a nested comp with a 3D camera, loses all of its properties when Cont. Rasterize is turned on.

Anyway, consider this case closed. Thanks again for your input.

[Dino Juarez]

Dave,
Thanks for your prompt reply. However, I am only using one camera. The single camera is in the smaller 864 x 486 comp. This comp was then nested into a second comp which is set to 1920 x 1080. There is no camera in the second comp. The only thing I do in the second comp is A.) scale up the 864 x 486 by 222% and B.) Enable the Continuously Rasterize button.

If you haven’t done so, try to set up my exact arrangement and you will see what I mean. As soon as you check the continuous rasterize button in the second comp, all translation properties from the 3D camera (which is in the smaller, original comp) are lost.

This seems to be an issue that Adobe needs to address as I have located numerous posts on the same subject.

Thanks for your input…