Mylenium
Forum Replies Created
-
Thanks for the kind words…. I’m working on more stuff, so you will definitely see more articles some time soon. Just can’t give you more concrete dates as it’s rather hot at the moment here and on some days I just don’t feel like doing a lot of work on the videos (yeah, call me lazy) and all this soccer/ football frenzy here in Germany is somewhat distracting as well (though I’m not particularly a fan, it’s hard to escape). ;o) So best stop by at the COW from time to time to keep track of things.
Mylenium
[Pour Myl
-
It’s not part of Photoshop, it’s a third-party plugin that you need to buy.
Mylenium
[Pour Myl
-
Most likely your images are simply too low res and the sampling/ filtering will make them look blurry. Turn it off alltogether or use another method than the default MIP (in the material properties for the texture layer). The format of the images shouldn’t matter – to C4D its all just pixels once it has loaded an image regardless of the format.
Mylenium
[Pour Myl
-
You need to add a dedicated “visible in Renderer” Track in the timeline window for each object that shall behave this way.
Mylenium
[Pour Myl
-
Try Microcosm fromn Digital Anarchy or if you have QT Pro on a Mac Pixlet. Alternatively separate Alpha and RGB and save them as separate files. This could yield substantial savings. For distribution you could use torrents. just make sure you conatin your stuff in na encrypted file so nobody else can access it.
Mylenium
[Pour Myl
-
In principle you are right. The result should be about the same. I believe, though, that Fast Blur would still look different since it seems to mess with the sub-pixel smoothing (which Box Blur doesn’t – it works strictly linear). I don’t no and Stu doesn’t seem to know that for sure either, so I can’t provide further explanations.
Mylenium
[Pour Myl
-
Box Blur will do exactly what it says – it will blur pixel separately for each iteration. So if you have 3 iterations and a Blur width of 3 pixels, the first iteration will blur each pixel across an area of 3×3 pixels with centered weighting. After that it wil use the already blurred/ interpolated data and apply the other iterations. If you draw that on paper as a pyramid like that
your shape will look like a Gaussian curve (each o represents a pixel). The more iterations, the wider this gets.
Fast Blur basically is just one iteration. It will blur your image more because it only increase the size of the blur area, making the result less precise the larger it becomes (because the average value of all pixels becomes more “samey”). You loose a lot of detail and the blur increases linearly wheres Box Blur by its very nature acts more like a camera based Blur and maintains much more detail and crispness even at high settings.
Mylenium
[Pour Myl
-
Box Blur will do exactly what it says – it will blur pixel separately for each iteration. So if you have 3 iterations and a Blur width of 3 pixels, the first iteration will blur each pixel across an area of 3×3 pixels with centered weighting. After that it wil use the already blurred/ interpolated data and apply the other iterations. If you draw that on paper as a pyramid like that
your shape will look like a Gaussian curve (each o represents a pixel). The more iterations, the wider this gets.
Fast Blur basically is just one iteration. It will blur your image more because it only increase the size of the blur area, making the result less precise the larger it becomes (because the average value of all pixels becomes more “samey”). You loose a lot of detail and the blur increases linearly wheres Box Blur by its very nature acts more like a camera based Blur and maintains much more detail and crispness even at high settings.
Mylenium
[Pour Myl
-
Set your Keyframes to linear or use Ease-in/ Ease-out. What you describe is normal interpolation behavior of Bezier keyframes.
Mylenium
[Pour Myl
-
I don’t quite get what you are trying to tell us… Expressions use absolute name string based references, there is no way around that. AE 7 will keep track of those and rename references where appropriate (though it sometimes does not work as expected). Your only other simple option is to use references based on layers’ and effects’ indices e.g. comp(“Main”).layer(1).effect(1)(“Slider”) as opposed to comp(“Main”).layer(“X”).effect(“Effect”)(“Slider”). If you are really daring in nature, you can build your setups based on filtering name strings, but the overhead is substantial and not really worth the effort. Apart from all said above, you should simply re-think your workflows. Make use of the “Copy Expression only” function and regualrly save your expressions into animation presets so you can easily re-apply them to layers en masse when required.
Mylenium
[Pour Myl