
This is obvious when you see that the depth buffer can only hold one value per pixel. It's not possible to blur reflections or objects behind transparent objects correctly. Issues There are common unavoidable problems that all post processing depth of field solutions have. Of course both filters support 16bit image format. Lenscare doesn't produce any such artifacts. Stochastic or super sampled ray traced blurs suffer from artifacts if not enough samples are used. Please note that the After Effects version was honestly adjusted to look as good as possible. The artifacts described above can be seen pretty good in the After Effects version. Here is a comparison of the After Effects standard depth of Field filter compared to Lenscares. Usually this results in ugly glow effects in regions with great differences in depth. A common mistake for 'depth of field' filters is to 'blur' all the surrounding pixels without regards to their depth values. They are just methods that look nice in some situations but fail in others. They don't do their names justice because their algorithms are not physically based. Fortunately for us most don't simulate camera effects properly. Quality Plenty depth of field and out of focus solutions are available. Of course Lenscare takes advantage of multiple cpus if present. Lenscares dof: 6 seconds + 4min no dof Brazil render). Check out this comparison of Brazils depth of field with Lenscares. This is a big advantage especially with high quality global illuminated renders. In a lot of situations you can save hours of render time for just a couple of seconds per frame in post processing. 'Depth of Field' is very fast for what it does. Speed 'Out of Focus' effects is a speedy 2d blur and can compete with any existing solution.
