AdminJohn Colombo (Quality Engineer, After Effects, Adobe, Adobe DVA)

My feedback

  1. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Needs More Info  ·  4 comments  ·  After Effects » Compositing & effects  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment

    Hi Jim,

    Thank you for reporting this issue. The screenshots you mentioned don't seem to have attached to your original post, would you mind reattaching them as a comment?

    Thanks very much and sorry about the upload glitch,
    - John, After Effects Engineering Team

  2. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Needs More Info  ·  1 comment  ·  After Effects » User experience/interface  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment

    Hi Usul,

    Thank you for reporting this issue and for your system details. Could you give a little more information on what is not working with Mercury Transmit in After Effects 17.7? It appears to be working as expected on our test systems here.

    Thanks so much for any further information,
    - John, After Effects Engineering Team

  3. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Needs More Info  ·  1 comment  ·  After Effects » Compositing & effects  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment

    Hi Justas,

    Thanks for reporting this issue. Would you be able to provide the project file you were working with? We have an investigation in progress for a similar issue in AME, but we would need to test your project file to confirm if you are experiencing the same issue.

    This issue may also relate to your computer's specs: would you please post your OS version, RAM amount, etc?

    Thanks very much for any additional information,
    - John, After Effects Engineering Team

  4. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Needs More Info  ·  3 comments  ·  After Effects » Stability  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment

    Hi David,

    Thank you for reporting this issue. Would you be able to post a screenshot showing the visual artifacts you are seeing with the GPU-accelerated Gaussian Blur effect? A comparison with the Legacy Gaussian Blur over the same image would be helpful as well. In doing a quick comparison here, I'm not experiencing any obvious artifacts at 32bpc.

    Thank you for any further information,
    - John, After Effects Engineering Team

  5. 5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Needs More Info  ·  4 comments  ·  After Effects » User experience/interface  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment

    Hi Pieter,

    Thank you very much for all of those details. Thanks as well for your patience, I wasn't notified of your responses until now.

    In regards to the crashing issues, there were several crashing bugs fixed in the versions of AE from 17.5 onwards. You may have been encountering one of these, especially with your mention of auto-save appearing to increase the likehood of a crash. What is your experience like with the latest version of AE ( 17.7 ) or with the latest available Beta version?

    In regards to the slow performance, yours is not the first customer report I've seen which mentions other apps lagging while running AE and we are investigating this issue. This can be caused by a variety of different factors, including RAM usage, GPU usage, and disk I/O to name a few but we would need perhaps a screen recording during the slowdown and a view of the Task Manager to start trying to diagnose which one to look more into. Having only 16 GB of RAM definitely could be a factor. I would also consider your GPU drivers and if they are updated to the latest ( compatible ) version; GPU drivers are very often a cause of general instability. Anecdotally, we have heard some positive reports coming from customers underclocking their GPUs for better stability.

    The issue you've mentioned where an Opacity property follows the Scale animation is strange indeed. Would you be able to share either a screen recording or project with us showing the issue?

    Thanks again for your patience,
    - John, After Effects Engineering Team

    An error occurred while saving the comment

    Hi Pieter,

    Thank you for reporting this problem. I hear your frustration with these extreme performance issues and I hope we can track down what is causing them. Our testing team here is not experiencing these same issues, but there are many variables that could be causing them.

    - What are your system specs? OS version, hardware, RAM, GPU, etc.
    - What third-party plug-ins or panels do you have installed? Are they all updated to their latest version?
    - Did the performance problems start with a certain version of After Effects? Does the latest Beta exhibit the same problems?

    Thanks in advance for any additional information you can provide,
    - John, After Effects Engineering Team

  6. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Needs More Info  ·  1 comment  ·  After Effects » Workflow & interoperability  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment

    Hi Todd,

    Thank you for reporting this issue. Are you still seeing this behavior in the latest version of AE? If so, would you be able to provide us a sample of the MPEG 2 footage which doesn't import?

    Thanks for any further information,
    - John, After Effects Engineering Team

  7. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  After Effects » Performance  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment

    Hi Adrian,

    Thank you for reporting this slowdown. This is a known issue with .csv or other data footage within project files, specifically when added to a Composition as a layer as required to track the data footage as a dependency for rendering in Media Encoder or in Motion Graphics Templates. The team is aware of the issue and is considering possible solutions.

    In the meantime, a workaround is to place your .csv into a single Composition ( we'll call this the "Data Comp" ) and place that comp as a layer of the rendering Compositions to track the data footage use. To reference the data, either pick whip to it directly in the Project panel or pick whip to specific data items within Data Comp. While not as easy as adding the data footage directly as a layer, this should greatly improve your saving/loading times when working with data sources.

    Let me know if that all makes sense, happy to describe or demonstrate in more detail.
    - John, After Effects Engineering Team

  8. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Needs More Info  ·  1 comment  ·  After Effects  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment

    Hi Pawel,

    Thank you for reporting this issue. We aren't able to reproduce the alpha of a layer being inverted with Liquify is applied in a 32bit project, would you be able to share a project or screen recording with us that demonstrates the issue?

    What you're seeing may be related to the Liquify effect only supporting 8 or 16 bpc color, as indicated by the dialog shown by clicking the warning triangle next to the effect's name when it is applied in a 32bit project.

    Thanks for any further info,
    - John, After Effects Engineering Team

  9. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  After Effects » Compositing & effects  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment

    Hi Tristan,

    Have you tried using Pixel Motion Blur instead? CC Force Motion Blur is only able to generate motion blur in cases when there is sub-frame content present. Since a CG render on its own only changes on each frame, there is no sub-frame information for CC Force Motion Blur to sample. The same would be true for any footage which matches the composition's frame rate.

    Please let us know if you see similar issues with Pixel Motion Blur.
    - John, After Effects Engineering Team

  10. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  After Effects » User experience/interface  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment

    Hi Constantin,

    Thank you very much for reporting this issue. We have passed this info on to our localization team.

    Cheers,
    - John, After Effects Engineering Team

  11. 3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  After Effects » User experience/interface  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment

    Hi Constantin,

    Thank you very much for reporting this issue. We have passed this info on to our localization team.

    Cheers,
    - John, After Effects Engineering Team

  12. 18 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  After Effects » Performance  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment

    Hi Rashid,

    Thank you very much for filing this report! We have opened an internal bug on this and the team will be investigating.

    Thanks again,
    - John, After Effects Engineering Team

  13. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  After Effects » Stability  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment

    Hi Sungwon,

    Thank you for that additional information. We have able to reproduce the lagging in both 2020 ( 17.7 ) and in 2019 ( 16.1.3 ) due to the number of repeated shapes, but we have not been able to reproduce the crash or failure to display the Composition. Even with 30+ layers with Repeaters on each set to 3000 copies, the project only lags but does not crash when using a system with specs a little less powerful than yours ( 64GB RAM, i7, dual GTX GPUs ).

    When you experienced the crash, was it in the latest 17.7 version of AE or an earlier version? If possible, please try again in the latest version of After Effects (Beta) in the Creative Cloud app and see if the result is the same.

    A screen recording or project would still be the most helpful in diagnosing the problem. We definitely understand that company assets wouldn't be sharable, but if you are able to recreate the setup in another project and see the same result again, please share that project/recording with us.

    Thanks again,
    - John, After Effects Engineering Team

    An error occurred while saving the comment

    Hi Sungwon,

    Thank you for reporting this issue. We unfortunately are not able to reproduce the freeze in the latest release or Beta builds when adding more than one Shape layer with a Repeater or stacking multiple Repeaters in a Shape layer. Would you be able to post a link to a project file that demonstrates the Shape Repeater setup which is causing After Effects to freeze? A screenshot of the Timeline showing the structure of the layers would work as well.

    Also, what are the system specs on the computer where you are experiencing the freeze with Repeaters? This info might be helpful to diagnose what is causing the freeze.

    Thanks very much for any additional information,
    - John, After Effects Engineering Team

  14. 3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  After Effects » Stability  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment

    Hi Michael,

    Thank you for reporting this issue, that sounds extremely frustrating. What are the specs/OS of the machine where you're experiencing this issue?

    If you are on Windows, there is a known issue where changing/removing any audio devices can cause RAM preview to stop working. Rather than re-opening AE, try toggling the Default Output in Edit > Preferences > Audio Hardware. This is a workaround, not a fix, but may save you some time while the true fix is being investigated.

    If the above workaround doesn't help, your specs/OS will be the next step as we try to reproduce the issue on our end.

    Thanks again for reporting,
    - John, After Effects Engineering Team

  15. 3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  After Effects » General  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment

    Hi Dillon,

    Thank you for reporting this issue. We are able to reproduce it as well with the steps you provided ( thanks for those! ). We will be taking a look at possible causes and solutions.

    In the meantime, a workaround is to add ".value" to the end of the property reference e.g. "transform.position.value" or, if the expression is referring to its own property as in your example, simply use "value" by itself to achieve posterization of the pre-expression keyframed values.

    Thanks again for reporting this bug,
    - John, After Effects Engineering Team

  16. 3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  After Effects » Stability  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment

    Hi Javeed,

    Thank you for reporting this issue. We can see the same error when pick whipping to the Direction property of Advanced Lighting and will get a bug ticket filed internally.

    In the meantime, there is the workaround of using the index of the property rather than the name. To do this, hold the Alt/Option modifier key while releasing the pick whip. This will create an expression link that works just like the name and avoids the bug while we investigate a solution.

    Thank you again for reporting this issue!
    - John, After Effects Engineering Team

  17. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Needs More Info  ·  1 comment  ·  After Effects » General  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment

    Hi Omri,

    Thank you for reporting this issue. What version of After Effects is affected and what OS are you running? If you can capture and share a screen recording of the random windows opening and closing when you use the shortcut, it would be extremely helpful in identifying what is going wrong.

    Thanks very much for any additional information,
    - John, After Effects Engineering Team

  18. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  After Effects » Performance  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment

    Hi Linus,
    Thank you for reporting this issue. After opening your .aep, I wasn't able to see any render differences between the 17.6 Beta and 16.1.3 ( CC 2019 ) while changing the project bit depth and toggling on the Offset effect.

    Would you be able to provide screenshots of the difference between 17.x and 16.1.3?

    Thanks so much for any additional info,
    - John, After Effects Engineering Team

  19. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Needs More Info  ·  5 comments  ·  After Effects » General  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment

    Hi Florian,

    Thank you for reporting this issue, and our apologies for the long delay in responding. Is this issue still persisting in the latest version of After Effects? It looks like some pixel data might be "stuck", possibly due to a GPU issue. Does the odd smear persist after rebooting the machine?

    Please let us know if you are still experiencing this in the latest version.

    Thanks again,
    - John, After Effects Engineering Team

  20. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  After Effects » User experience/interface  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment

    Hi Andrei,

    Thank you for submitting these issues. To address each separately:

    In your example screen shot with the expressions, you are adding a wiggled Slider value ( a single number ) to a Scale value ( which is an array of two numbers ). Expressions automatically convert the values to match in this case, so "transform.scale + effect("Wiggler 2")("Slider")" becomes "[100,100] + [ 12, 0 ]". The X and Y values are added separately, similar to your topmost expression, but the Y value for the Slider is 0 because only a single number was given.

    If you apply the wiggle() expression within the Scale property, rather than linking it to a wiggled Slider, it will automatically return an array of two different values. If you want to have a wiggled expression controller, perhaps to link multiple properties up, you should use a Point Control instead of a Slider so that the number of values/array length matches up.

    The issues you are seeing with the Threshold effect is related to its implementation; in the UI, the values shown correspond to the project bit-depth by default. So 0-255 is shown for 8bit, 0 - 32,768 for 16bit, and 0 - 1 ( floating-point ) for 32bit. However, the expression value is always in 32bit and therefore from 0 - 1.

    We will get a ticket filed for this internally for evaluation, as I can see how this would be confusing. A workaround which will work in AE today would be to set the Color Display preference in the Info panel's context menu ( the three lines aka "hamburger menu ) to "Decimal (0.0 - 1.0 )". This will cause the Threshold's Level property to always show the floating-point value instead of the 8bit or 16bit value, regardless of the project setting.

    Thank you again for your feedback on both of these issues. I hope the explanations above are helpful, but please feel free to ask any additional questions.

    Cheers,
    - John, After Effects Engineering Team

Feedback and Knowledge Base