Skip to main content
Jan 14, 2013 7:30 PM UTC
Answered

Crummy Camera Lens Blur CS6

The Camera Lens Blur effect that came with AE CS 5.5 and CS 6 doesn't look nearly as good as the old Lens Blur effect that came with CS 5; it's pretty much unusable for my purposes. Foreground elements that should be sharp render sharp, but with a blurry halo around them. The old Camera Lens blur does not exhibit this behavior, nor the Frischluft Depth of Field plugin.

Here's an image showing the depth map and how the three plugins render it:

CameraLensBlur.png

The images are composited from 16-bit PNGs rendered out of Cinema 4D. There's a nasty halo visible around the foreground particle in the upper left in the CS6 Camera Lens Blur version. I saved the old Lens Blur effect as a preset out of a CS5 project and am, fortunately, still able to use that approach in CS6 since the "improved" version of the plugin looks pretty crummy (I skipped AE CS5.5). As a test I installed the demo of Frishluft's Lenscare plugins, and after inverting the depth buffer in the plugin I got a good result.

The "new" Camera Lens Blur is acting like the Compound Blur effect. Foreground elements appear sharp but with a blurry halo since the entire "background" is being blurred, creating a blurred ghost of the foreground element. The old Lens Blur effect was very slow, but it did work.

Anyone know how to make this new "improved" Camera Lens Blur look like the other plugins?  I've posted a zipped file with the image and depth map in a small AE CS6 project here if anyone here would care to check my settings.  Maybe I'm missing somthing.

CameraBlurs folder.zip

Thank you.

Shawn Marshall

Marshall Arts Motion Graphics

    Todd_Kopriva
    Todd_KoprivaCorrect answer
    Inspiring
    Apr 18, 2014 6:15 PM UTC

    Hi Blindesign,

    Sorry you feel that way. If you don't mind, please file a bug report/feature request as my colleague suggested earlier in post #15: Updated link (3/19): After Effects: Hot (1390 ideas) – Adobe video & audio apps

    Thanks,

    Kevin


    The After Effects team does consider this to be a bug, and it's on our backlog to fix. It just hasn't risen to the top of the to-do list because we have seen very few bug reports about it, so it seems that not very many people are bothered by it. We tend to work on bugs in priority order based on severity and how many people report that they are affected.

    So, yes, do submit a bug report to cast your vote.

    77 replies

    Participating Frequently
    Jun 30, 2021 3:13 PM UTC

    Hey, 2021 now...problem still...

    Translate
    Participating Frequently
    Jun 30, 2021 4:39 PM UTC

    I've watched this thread avidly to see if Adobe ever fixes this, I gave in as they NEVER will and bought Fast Bokeh Pro from AE Scripts. There's a free version of it, the pro version just expands upon this. Link: https://aescripts.com/fast-bokeh/

    Translate
    Participating Frequently
    Apr 15, 2020 10:19 AM UTC

    Any news on a fix for this yet, Adobe? 7 years is a LONG, LONG time for a bug not to be fixed.

    Translate
    Five Stone Productions
    Participant
    Dec 4, 2019 10:41 PM UTC

    Please resolve this issue. It's been 5 years. We've needed this to work at our studio so many times now. Very frustrating.

    Translate
    Stefan_Gallego
    Inspiring
    Nov 23, 2020 11:36 AM UTC

    Grab the depth blur from withing this lenscare packet here: https://www.frischluft.com/lenscare/

    It's been creating way better depth blur since many years.

    Translate
    Using AE since 2004
    Participating Frequently
    Nov 23, 2020 11:51 AM UTC

    I've given up on Adobe fixing the issue, it's never going to happen. I did however find a decent, cheaper, alternative to the Frischluft one. Have a look on AeScripts for Fast Bokeh, the free version works correctly and the fairly cheap Pro version is great! 

    Translate
    Participant
    May 17, 2019 9:26 PM UTC

    I've literally had this issue since 2014, 5 years

    Translate
    Participant
    Jan 23, 2018 7:27 PM UTC

    I remember joining this lovely conversation in 2014, thinking I was late to the party... seems I was 4 years ahead of schedule. It's such a pleasure to receive email updates and know the community here is well. I don't look forward to the day where suddenly this issue is resolved and we lose the only thing that binds us together. Thanks Adobe for making this possible

    Translate
    Jan 25, 2018 4:31 PM UTC

    Its been fun, hasn't it!

    On top of this, every bloody year (for the past 5) I've been asking to get the Frischluft Lenscare plug-in for After Effects. Which one I'll get first, I don't know.

    Translate
    Participant
    Jan 22, 2018 1:49 PM UTC

    2018 here still not fixed. Bug report sent.

    Translate
    Kevin J. Monahan Jr.
    Legend
    Jan 23, 2018 12:58 AM UTC

    Thanks Danry86,

    Sorry for this issue. Thanks for filing.

    Regards,
    Kevin

    Translate
    Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
    Jan 25, 2018 4:30 PM UTC

    That's it Kevin, file it away somewhere with the rest of the bug reports for this, we might get it fixed by about 2030.

    Or is that a bit too soon?

    Translate
    Stefan_Gallego
    Inspiring
    Mar 9, 2017 12:21 PM UTC

    This question has not yet really been answered.

    Translate
    Using AE since 2004
    Mar 9, 2017 12:33 PM UTC

    Yep, still! It's still a problem in the latest After Effects. How the hell has this not been sorted yet... Adobe, just buy out the Friscluft plug in and let us have proper depth control already...

    Translate
    Participating Frequently
    Dec 24, 2016 6:32 PM UTC

    This is, 2016 12 25

    The problem still appear in CC 2017...

    Translate
    Szalam
    Community Expert
    Community Expert
    Dec 27, 2016 6:51 PM UTC

    Cliffordli wrote:

    This is, 2016 12 25

    The problem still appear in CC 2017...

    Yes.

    File more feature requests!

    Translate
    Sep 29, 2016 8:36 AM UTC

    Still no fix then?!

    Translate
    Participating Frequently
    Jun 9, 2016 11:43 AM UTC

    This question has not been "answered". I think the answer is that Adobe seems content with having major software bugs because they think they can get away with it.

    Translate