AdminTim Kurkoski (After Effects Senior Quality Engineer, Adobe DVA)

My feedback

  1. 7 votes
    Sign in Sign in with: Adobe ID
    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

    Some of this data (but only some) is available when you use the Collect Files command. You can specify in the options dialog to only generate a report, if you just want to collect that data.

  2. 2 votes
    Sign in Sign in with: Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  After Effects » General  ·  Flag idea as inappropriate…  ·  Admin →

    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

    Glad to know that the problem is limited to the single project.

    If you'd like us to look at it, post a link to your files here, or if you prefer not to post publicly you can send it to aebugs@adobe.com. (If you send to that address: A) Do not send .zip files, they will be blocked; renaming to .thisisazipfile is OK. B) Post a comment here when you have sent the email. I need to manually check that inbox.)

  3. 3 votes
    Sign in Sign in with: Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  After Effects » Stability  ·  Flag idea as inappropriate…  ·  Admin →

    Thank you for filing this bug report.

    We need more information about the conditions you experience the problem.

    • What OS and version are you using? i.e., Windows 10 or macOS 10.14
    • What graphics card is installed? What driver version?
    • Does the this problem only happen in your existing projects, or does it occur if you create a new comp and a new solid, and apply only the Transform effect?

    Update 26 Nov 2018:
    Could you share a project with us that exhibits the problem? I think we need to inspect the specific conditions of the comp that you’re using. We’re not able to reproduce the problem with a simple comp + solid.

    Post a link to your files here, or if you prefer not to post publicly you can send it to aebugs@adobe.com. (If you send to that address: A) Do not send .zip files, they will be blocked;…

    An error occurred while saving the comment

    Could you share a project with us that exhibits the problem? I think we need to inspect the specific conditions of the comp that you're using. We're not able to reproduce the problem with a simple comp + solid.

    Post a link to your files here, or if you prefer not to post publicly you can send it to aebugs@adobe.com. (If you send to that address: A) Do not send .zip files, they will be blocked; renaming to .thisisazipfile is OK. B) Post a comment here when you have sent the email. I need to manually check that inbox.)

    An error occurred while saving the comment

    What are the dimensions of the solid and comp that you are testing?

    If you reduce the size of the layer, does the GPU request for the Transform effect succeed?

  4. 3 votes
    Sign in Sign in with: Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  After Effects » Compositing & effects  ·  Flag idea as inappropriate…  ·  Admin →

    Thank you for filing this bug report.

    Update 14 Nov 2018 – I received the files, thank you.

    After playing with the project for a little bit, I see how the Write-on effect is not behaving correctly. But I’m not able to deduce what the cause of the problem is. I’m not able to reproduce the problem from scratch, and if I make modifications to your project, it starts to render correctly.

    My best guess is that the keyframe data of the Write-on effect in your project became corrupted somehow. It’s relatively easy to fix, although a bit tedious:

    1. On each keyframe, modify the property value. (I made small adjustments, like rounding fractional X or Y values up to the nearest integer, or increasing the brush size by 1. Any change to the keyframe’s value should work here.)
    2. Edit > Purge > All Memory & Disk Cache.

    If…

    An error occurred while saving the comment

    I don't think attachments are allowed in comments, only in the original request. Can you post to Dropbox or another file share service and post the link here?

    If you prefer not to post the files publicly you can send it to aebugs@adobe.com.

    If you send to that address: A) Do not send .zip files, they will be blocked; renaming to .thisisazipfile is OK. B) Post a comment here when you have sent the email. I need to manually check that inbox.

  5. 11 votes
    Sign in Sign in with: Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  After Effects  ·  Flag idea as inappropriate…  ·  Admin →

    What additional features would you like to see in a bug reporting tool?

    The UserVoice platform is a new tool (as of 2018) that Adobe DVA product teams are using to track user feedback, and allow public voting and commenting on suggestions. Prior to this, reports were not visible to the public, so no voting or discussion could occur on a given report.

    Submissions to this site are reviewed by the Adobe DVA product teams. Not every submission will receive a response, but we are reading the submission and using the feedback in our planning process for future updates to After Effects, Premiere Pro, and our sibling applications. We’ve closed many submissions to this site as completed after a new update has been released, when the submission was addressed by the update. Other submissions are closed as not actionable, or declined, if the request does not align with our development…

    An error occurred while saving the comment

    Thanks for the additional detail, Mike.

    In general, I agree with your assessment. Information like reproducibility, system information, and priority/severity are all important to a well-written bug. Having spent a decade in software QA, such detail is critical to a well-written bug report.

    That said, in my experience, well-written bug reports are not often received via public forms. There are a people like yourself that understand what information to supply in a bug report, and I always appreciate that, but most of the time bug reports require a little imagination from the QA or developer receiving them. Even when we've provided templates or fields that require such details to be filled out, they're often blank or incorrect.

    Regardless, as I mention above, I hope to make some improvements to how we use UserVoice to track bug reports. We don't want any feedback to be considered insignificant.

    Thanks for your attention. Please keep the suggestions coming.

  6. 2 votes
    Sign in Sign in with: Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    This is an interesting idea. I don't think I agree with it.

    You can create a shape layer that is the size of the composition by double-clicking on the Rectangle tool in the Toolbar.

    Is the request that you want to be able to control the dimensions of the rectangle shape when it is created, the same as you do in the New Solid dialog? That's a good request, but different from what you've described above.

    Another way to go about this would be to have the Layer > New > Shape Layer command create the shape, possibly with a similar dialog for controlling shape properties. Right now that command only creates an empty shape layer, which I've never found useful. Again, this is a different request that what you've described, so if you think this would be useful, best to create a new request at this site so it can be voted on appropriately.

  7. 8 votes
    Sign in Sign in with: Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  After Effects » Stability  ·  Flag idea as inappropriate…  ·  Admin →

    Thank you for filing this bug report.

    Are you still experiencing this problem in After Effects 15.1.2 (July 2018 release) or After Effects 16.0 (October 2018 release)?

    Many issues with importing QuickTime .mov files were fixed in these releases.

    If you continue to experience problems, please post or link to a sample file that is not working as you expect.

    Note that After Effects 15.1 was the removed support for legacy QuickTime formats and codecs. After Effects 15.1 and later remain capable of importing and exporting QuickTime .mov files with common codecs, like Apple ProRes, Avid DNxHD/HR, and others. The main difference now is that After Effects supports these codecs natively instead of relying on external QuickTime components.

    More detail and a list of supported codecs is here:
    https://helpx.adobe.com/x-productkb/multi/quicktime7-support-dropped.html

    If a codec you want to use is not on that list, please post a new request here with the specific…

    An error occurred while saving the comment

    > They have removed the support for MOV files

    This is not true. After Effects still supports importing and exporting QuickTime .mov files. What changed in After Effects 15.1 was the removal of legacy QuickTime formats and codecs. After Effects 15.1 and later remain capable of importing and exporting QuickTime .mov files with common codecs, like Apple ProRes, Avid DNxHD/HR, and others. The main difference now is that After Effects supports these codecs natively instead of relying on external QuickTime components.

    More detail and a list of supported codecs is here:
    https://helpx.adobe.com/x-productkb/multi/quicktime7-support-dropped.html

    If a codec you want to use is not on that list, please post a new request here with the specific codec. (As of today, this list does not include that the Hap codec can be imported into the October 2018 release of After Effects CC or Premiere Pro CC; versions 16.0 and 13.0, respectively.)

    Note that plug-ins can also be built using the After Effects SDK to add additional codec import and export support.

    If you have a QuickTime .move file in a supported codec that is not importing or is experiencing other problems, please post a new request on this site with a link to the file so that we can inspect it. In the subsequent releases to After Effects 15.1 (15.1.1, 15.1.2, and 16.0) we have fixed many problems reported by customers. Most of these cases were due to poorly formed header data in the QuickTime files; the now-removed legacy QuickTime support was more tolerant of such problems.

  8. 4 votes
    Sign in Sign in with: Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  After Effects » Workflow & interoperability  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment

    Please see my previous comment. The reason that the file can not be imported into After Effects 15.1 is not because it uses the ProRes 4444 codec, but because there is some other issue with the QuickTime file that After Effects is unable to parse.

    (Summary of my post below: QuickTime files contain other data than just the video or audio streams. Header data, edit lists, etc. That data could be malformed, or it could be a type of data that After Effects doesn't know how to read.)

    Please file a new request on this UserVoice site that is specific to the problem you're experiencing with that file. In order to investigate the problem, we will need to examine the file, so please either post it or provide a link to where we can get it. Or, if necessary, we can give you an alternate, non-public method to share the file with us.

    An error occurred while saving the comment

    The forum thread mentioned in the previous comment is misleading, in that it does not accurately describe how After Effects and other Adobe applications currently support codecs in a QuickTime container. Apple ProRes codecs are, in fact, supported.

    Please refer to this page for a list of codecs supported for import and export in After Effects, Premiere Pro, and Adobe Media Encoder:
    https://helpx.adobe.com/x-productkb/multi/quicktime7-support-dropped.html

    Since QuickTime 7 legacy support was removed, we have investigated reports where some QuickTime files result in errors or other problems when imported into Adobe applications, even though they use codecs that are supported.

    These problems generally fall into one of two categories:
    - The QuickTime file was not formatted correctly by the application that wrote it. In previous releases of After Effects, where the legacy QuickTime 7 support was available, if After Effects could not read a malformed file natively, it could be passed to the QuickTime 7 components, which was often more tolerant of faults like missing or bad header information (for example). Now that the QuickTime 7 components are not available, there is no backup case for these files. When customers have provided us samples of such files, we have made adjustments for some of these cases to provide tolerance for common malformed files.
    - The QuickTime file requires a feature that was specific to the legacy QuickTime 7 components and is not natively available in After Effects. An example of this is complex edit lists, which was like an NLE's edit list in that it could specify playing segments of a video or audio track out of order. Similar to the malformed files problem I describe above, previous versions of After Effects could not read these files natively and would pass the file to the QuickTime 7 components, and that backup no longer exists. Again, we have examined sample files provided to us, and we are making adjustments for some of these cases, but others (including complex edit lists) require significant engineering effort.

    In this context, it is helpful to remember that QuickTime is a 25+ year old software package that has evolved to include many unique features. Re-engineering all of that functionality is not simple.

    Our goal is to keep up with the most modern workflows, support formats, and codecs broadly used across the professional film and video industry. Part of that means no longer relying on legacy components like QuickTime 7.

    When you find a file that should be supported but produces errors or other problems, please report the problem as a bug here on this UserVoice site. Sample files will be helpful. We can arrange a method for you to share them if you don't want to post them publicly.

    If you have a file that is not currently supported but you would like it to be, please file a feature request for the codec or functionality that you would like to see added.

  9. 21 votes
    Sign in Sign in with: Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  After Effects » User experience/interface  ·  Flag idea as inappropriate…  ·  Admin →
  10. 2 votes
    Sign in Sign in with: Adobe ID
    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

    The crash report data is anonymous, unless you fill out the form with your email address. In any case, you have chosen to be anonymous on this User Voice platform, I have no way to correlate the data without your assistance.

    Regardless, crash reports are only half of the picture. They can tell us that a crash occurred in a certain condition, but they don't always tell us how you got into that condition. That's why I asked for specific steps, project files, and/or screen recordings. If we can induce the crash ourselves or at least see the crash in action, that's better than just getting the log after the fact.

  11. 2 votes
    Sign in Sign in with: Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  After Effects  ·  Flag idea as inappropriate…  ·  Admin →

    Thank you for filing this bug. Can you provide us with a link to a file that will not import into After Effects 15.1? Send it to aebugs@adobe.com if you don’t want to post publicly.

    After Effects 15.1 does support DNxHD and DNxHR codec QuickTime files. The problem you are experiencing is likely either a limitation of this support, or a damaged file.

    Since the release of After Effects 15.1, we have seen reports of similar cases where QuickTime files using natively supported codecs will not import. When files are available to us we can inspect them; mostly what we are finding is that the QuickTime file in question is structured in a way that is no longer supported. As the QuickTime format was developed over many years, it incorporated a number of unique features that are not supported natively by After Effects. (For example: complex edit lists, where the…

    An error occurred while saving the comment

    Thanks, we'll have a look at the file. It would also help us to know what application created the file.

    You can install older versions of Creative Cloud applications; instructions are here:
    https://helpx.adobe.com/download-install/using/install-previous-version.html

    When you install a new version of a Creative Cloud application, there are two scenarios:
    - Yearly upgrades install into new folders, and are usually differentiated by whole version-number changes. (Ex., 14.0 vs. 15.0, or CC 2015 vs. CC 2017). Note than when installing a yearly upgrade, there is a hidden option you need to disable to prevent the installer from removing the previous version.
    - Updates and patches install over the previous release of the same version, and are usually differentiated by decimal version numbers. (Ex., 15.1.1 vs. 15.1 vs. 15.0) You can not have more than one of these versions installed at the same time.

    By using an old version of After Effects or Adobe Media Encoder to transcode the video, I meant that you could install a previous year's version (ex., After Effects 14.2 or Adobe Media Encoder 11.2), as offered through the Creative Cloud desktop application. Or, if you wish, revert your installation of After Effects or Adobe Media Encoder to the version last capable of using 32-bit QuickTime processes (15.0.1 or 12.0.1, respectively), before reinstalling the latest updates.

    I hope that helps clarify what's possible.

  12. 2 votes
    Sign in Sign in with: Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    Thank you for filing this bug. Can you provide a link to a sample file that behaves as you describe?

    With the same file, do you get the same results or different results in After Effects 15.0.1, 14.2.1, or any other earlier version of After Effects?

    The Guess 3:2 Pulldown and Guess 24Pa Pulldown options analyze the footage to try to determine the field/frame cadence of the pulldown. There can be cases where it can fail to do this. In this case, you will need to choose the cadence manually from the Remove Pulldown menu.

    Without a sample file and comparison to earlier versions, we could not say whether what you observe is a change in behavior between versions, a bug, or simply a file that can not be analyzed. My tests on files with known pulldown cadences is not failing in After Effects 15.1.1.

  13. 2 votes
    Sign in Sign in with: Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    Thank you for filing this bug. Can you please provide more detailed steps to reproduce the problem? Is this on macOS or Windows? Can you provide a link to a file that causes the issue? (I am not able to reproduce the problem with the files that we have.)

  14. 3 votes
    Sign in Sign in with: Adobe ID
    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

    Can you please provide a link to a sample file that demonstrates the problem? Thanks.

  15. 4 votes
    Sign in Sign in with: Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  After Effects » Workflow & interoperability  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment

    Do either of the Opacity properties have expressions applied? Master Properties override the base value of the property, which won't have an effect if the expressions don't actually use that value. To have an effect on the pre-comp's layers you need to either override the expression on the master property, or make the expression use the value.

    If these properties are not using expressions, can you post the project somewhere so we can look at it?

  16. 3 votes
    Sign in Sign in with: Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    Thank you for reporting this bug.

    Can you provide us with the project file causing this problem? We will need to inspect the project to understand why it is causing this error. Please post a link to the file, or send an email to aebugs@adobe.com. Thanks.

  17. 6 votes
    Sign in Sign in with: Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    Thanks for filing this bug. I am unable to reproduce the problem you describe using a simple test case. Can you please provide sample files? Post a link here or email to aebugs@adobe.com and we will investigate.

    Does the PSD or AI file contain a Type 1 Postscript font? We are evaluating a problem where After Effects can not load certain fonts of that type, and it's possible that this is the root cause of the crash.

  18. 2 votes
    Sign in Sign in with: Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    Thanks for submitting this, Nick.

    Could you provide a link to screenshots and/or a sample project that demonstrates the problem. It would help if we could see what you're seeing. If you prefer not to post publicly, send the link to aebugs@adobe.com.

  19. 2 votes
    Sign in Sign in with: Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    Can you please be more specific? Which commands? What about them is not working?

  20. 3 votes
    Sign in Sign in with: Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    Thank you for submitting this request, Michael.

    We could use clarification. After Effects can already render to many different video, audio, and still formats, with and without alpha, that are compatible with Premiere Pro.

    If you're having difficulty with a given format, perhaps some investigation is needed. To help you troubleshoot this, it would be best for you to start a new conversation on the Adobe Community Forums:
    https://forums.adobe.com/welcome

    Once you do that, post the link to the discussion back here and I'll take a look.

Feedback and Knowledge Base