The Grey Cow

My feedback

  1. 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 » General  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Thank you for filing this report.

    When exporting via the Render Queue, there is an option in the Render Settings dialog which determines whether or not motion blur will be rendered. By default, the Motion Blur control defaults to On For Checked Layers, which will render motion blur for any layer on which the layer’s motion blur switch is enabled, regardless of the state of the comp’s “master” motion blur switch.

    Are you changing this setting in the Render Settings? Does its behavior otherwise align with your experience of which layers do or don’t render motion blur when exported via the Render Queue?

    An error occurred while saving the comment
    The Grey Cow commented  · 

    Hi Tim,

    Yes I am changing it in the Render Settings. And no, when it is set to "On For Checked Layers", it puts motion blur on random layers, despite there being not a single motion blur switch checked on for any individual layer. It does turn it off when I set it to "Off for all layers", but like I said, none of the switches are on in the first place.

    This is only the case in this one project however, and in my others it is working as usual.

    Also, what is the point of the Master switch then in the main comp to be rendered? As far as I remember, this used to be the way to turn motion blur on and off. It just makes it more confusing having that control be in the render setting, which makes the master switch purely a preview control.

    Thanks for responding.

    The Grey Cow shared this idea  · 
  2. 12 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

    0 comments  ·  Premiere Pro » Adobe Interoperability  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    The Grey Cow shared this idea  · 
  3. 546 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

    49 comments  ·  Premiere Pro » Performance  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Under Review  ·  Reg Santo Tomas responded

    As Wes noted, we are looking at many areas for optimization and have made strides in the last few releases already.

    We recognize there are still many areas to improve performance and we are investing in appropriate areas.

    Threads that are catch-alls are often non-actionable. Please keep giving us specific feedback on what workflows are slow for you.

    Technical solutions may not always be as obvious as some people may be suggesting as the application architecture is often very different than people’s conception.

    Short answer. Yes, we want to and will make it faster.

    The Grey Cow supported this idea  · 
  4. 305 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

    Under Review  ·  24 comments  ·  Premiere Pro » User experience/interface  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    The Grey Cow supported this idea  · 

Feedback and Knowledge Base