2 Replies Latest reply on Nov 17, 2016 6:37 AM by 21cls

    Displacement effect not affecting all layers below the same way.


      I am trying to apply the Jittery Effect I found here to the light beams on the train tracks (Jittery Type After Effects Tutorial - YouTube ) where it uses the displacement and fractal noise effects. I tried applying them to the beams I generated for each of the 4 lines for the train tracks. It only seems to apply it to the first 2 beams (beams 1 & 2) on the left side and it seems when I change the position of the beams to make them look like they do on the right train tracks it doesnt work for those anymore. They look like they jitter slightly on the starting and ending points of the beams on the right (beams 3 & 4) but not correctly. I can't figure out what would be the issue, I have included screenshots to try and explain my project and point out my settings. I have also included a short video export of the effect in motion. I would really appreciate the help!


      Video Clip Example: 21cls.com/downloads/neon-train-tracks-02.mp4



      screenshot 01 below:


      screenshot 02 below:


        • 1. Re: Displacement effect not affecting all layers below the same way.
          Rick Gerard Adobe Community Professional & MVP

          Fortunately I just sent a rotobrush shot to the renderer so I have time to dig into this problem.


          I see a couple of workflow issues. First, it's possible to put multiple beam effects on a single layer. Just duplicate the first beam effect and select composite on original. I would do that or pre-compose all of your beam effects if you want to effect all of the beams at the same time. You can also apply displacement map to the bottom of the beam stack like this:

          Screen Shot 2016-11-07 at 8.58.10 AM.png

          Second issue, if you have gray over beam 1 and black over beam 2 and white over beam 3 and a different gray over beam 4 then the end points are going to move in different ways. If you want the end points to stay fixed then you need to do an overlay on the end of the beams so the end points all stay in the same position. A luminance value of middle gray will keep the ends in their original position. You can do this with a gradient shape layer, a gray solid and your fraction noise layer and a blend mode in your pre-composed displacement map. (what I would name the comp with the fractal noise).

          Screen Shot 2016-11-07 at 9.07.04 AM.png

          Here's another thought. The displacement is going to look different on the lines slanted to the right vs the lines slanted to the left. Here's why. With a positive value for horizontal displacement black will move pixels to the left and white to the right. This will give the displacement a different look depending on the angle of the line:

          Screen Shot 2016-11-07 at 9.29.38 AM.png

          To fix this problem you'll need to separate the left leaning lines from the right leaning lines and apply a displacement map with different values to the each pair of lines, one with positive values the other with negative values. This is not a bug, it's just math. I hope this makes sense.


          I'm wondering why you have cameras and lights in the comp with the tracks. I'm assuming from your main comp screenshot that the footage is on the bottom and only the tracks are on the top. I also do not see any 3D layers other than the null and there is no camera in your Main comp so the camera is doing nothing to the layers in the screenshots. The only thing I would have in the beams comp is the beams and the displacement map.


          If these workflow suggestions don't solve the problem we need more workflow details.

          • 2. Re: Displacement effect not affecting all layers below the same way.
            21cls Level 1



            Thank you for your response, I haven't been able to get back to this project but will definitely try this method as well. I saw your comment on another duplicate thread and I apologize, I was either having issues with my internet or the website was having issues and it resulted in multiple duplicate threads.