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

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

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

    Interesting idea, Warren.

    Can you expand why this would be helpful? I understand the basic visibility part, I want to understand the workflow better. What does this allow you to do that you couldn't do before, or how does it make working in After Effects faster for you?

    Also: would you expect to be able to snap to these keyframe indicators, by holding the Shift key while dragging the CTI or other keyframes, as you can with markers and visible keyfrrames?

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

    Thank you for filing this bug report.

    We need more information in order to investigate:
    - Does the problem persist after you restart After Effects?
    - Does the problem occur only in this project, or in any project?
    - What version of After Effects are you using? (ex., After Effects 16.0.1, from the About After Effects dialog box.)
    - What OS and version are you using? (ex., Windows 10 or macOS 10.14.3)

    An error occurred while saving the comment

    Thanks for the additional detail. Knowing the problem isn't persistent, that restarting After Effects clears it at least temporarily, is helpful. But what we really need to understand what condition After Effects is getting into that causes the problem.

    Just prior to the problem occurring, what actions do you take in After Effects? What have you changed, clicked on, or asked After Effects to do before it starts misbehaving? In order for us to investigate this problem, we need to be able to replicate it, which means understanding what you're doing that puts After Effects into this state.

  3. 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

    0 comments  ·  After Effects » Animation  ·  Flag idea as inappropriate…  ·  Admin →
  4. 10 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  ·  Media Encoder » Batch Processing  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment

    After Effects has similar functionality as requested, the output file naming templates:
    https://helpx.adobe.com/after-effects/using/basics-rendering-exporting.html#specify_filenames_and_locations_for_rendered_output

    Would it be sufficient to port this functionality from After Effects to AME, or is there additional or different functionality that you're looking for?

  5. 44 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

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

    @Nick R. - Sorry, no, there's not currently a built-in method to force new projects or the Save As command to default to a particular folder. (You could rig something up with scripting, but there's nothing in the UI.) That would be a great, separate request. Please file it here at this UserVoice site!

  6. 6 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  ·  After Effects » Stability  ·  Flag idea as inappropriate…  ·  Admin →
  7. 15 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 » User experience/interface  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment

    Thanks for posting your idea.

    I agree that double-tap keyboard shortcuts are easy and useful. There are, however, some challenges:

    1. They're not discoverable. When you're new to an application and trying to learn how it works, keyboard shortcuts are actually one of the best ways to hide application functionality. The functionality, at the very least, needs to be discoverable via a different method and keyboard shortcuts should only be a time-saving method. However, that still leaves them farther up the learning curve. Personally, I'd prefer to design an application that is discoverable and intuitive.

    2. They're difficult to implement in code. Not impossible, just difficult. The double-tap (or triple-tap, as you suggest) require specific code to capture the timing of the keyboard input. This is different from single keyboard presses where existing, OS-provided event listeners can be used; much simpler. Additional code is required if the double-tap shortcut is going to be customizable separate from the equivalent single-press keys: the customization code needs to be able to capture that difference.

    I'm not saying that we couldn't ever do this in After Effects, and I look forward to seeing who else will vote on or comment on this idea. I'm just pointing out some of the challenges that we face as application developers. What seems easy and logical on the surface is not always simple when you start digging into the details of implementing that idea in code.

  8. 385 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

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

    Thanks all for the great feedback so far.

    As this discussion has progressed both here and on Twitter, I'm wondering if this request needs to be split into two parts. While I appreciate the universal approach of "Alt/Option + drag = duplicate", it sounds like there's a wider variety of behaviors desired here. So we'd need two different stories:

    1. Alt/Option + drag = duplicate for layers, Project window items, shapes, effects, and other objects where it makes sense.
    2. A larger story around better behaviors for duplicating or copy/pasting keyframes that covers the issues people have raised here regarding multi-layer cases, selection boxes, and modified paste behaviors like time-reverse.

    Your thoughts?

    An error occurred while saving the comment

    We were recently evaluating part of this request, to duplicate keyframes by holding the Alt/Option key and dragging. This is something we'd love to add to After Effects. But we've run into a couple of issues.

    As mentioned in the video, Alt/Option + dragging keyframes is currently occupied by the time-stretch keyframes behavior. The video suggests changing that behavior to use the Control/Command key + dragging, however that begins to get fuzzy because Control/Command + _clicking_ on a keyframe changes its interpolation to Continuous Bezier; there's a lot of opportunity here for accidental clicks.

    A related problem is muscle memory. Any time we change a mouse or keyboard input behavior, we get negative reactions from our user community. The video tends to dismiss the need for time-stretching keyframes, but I both disagree with that, and want to emphasize that changing muscle memory is very disruptive.

    Another complication is that Alt/Option + dragging on a layer's in/out points will time-stretch the layer. (This was added in recently, in After Effects 16.0, but we used time-stretching keyframes as the model for which keyboard shortcut to use.) If we change the meaning of Alt/Option + dragging keyframes, we may need to align other behavior as well, breaking more muscle memory.

    Regardless, we agree that the existing convention of Alt/Option + drag to copy is a desirable feature for After Effects (for both keyframes and other types of objects, but one thing at a time). We discussed what other keyboard modifiers the time-stretch keyframe behavior could be moved to, but we could not find an obvious answer because After Effects is already heavily loaded with modifier key + mouse click/drag behaviors. Even something as simple as adding the Shift key would interfere with snapping behaviors.

    Given those complications, how would you suggest the behaviors of clicking and dragging keyframes in After Effects be adapted?

    - What modifier key + click/drag combos would you like to see?
    - How do you feel about disrupting muscle memory, for both yourself and other artists?
    - Do you feel a preference or UI option would be needed to allow users to enable/disable the new behaviors and return to prior muscle memory?

    We will continue discussing this internally. Your opinions will help shape the conversation.

  9. 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

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

    Thank you for filing this bug report.

    We need more information in order to investigate:

    - What format is the footage that you are working with?
    - What version of After Effects are you using? The version number can be found in the About After Effects dialog (ex., After Effects 16.0.1).
    - What OS and version are you using? (ex., Windows 10 or macOS 10.13.6)

    An error occurred while saving the comment

    Thanks for the additional information, Nina.

    The More Options button in the Interpret Footage dialog should not be active for HEVC footage. It is a bug that you can click on it, but nothing is expected to happen. The More Options button is only active for footage types that have additional decoding settings, like raw video (RED R3D, ARRI raw, Sony raw, Canon raw, CR2/NEF/DNG still camera raw, etc.).

    I don't have a clear explanation for why your videos were being decoded as green. My best guess is related to the fact that After Effects can use Intel Quick Sync Video features to accelerate decoding of H.264 footage on Windows, and H.264 and HEVC on macOS. (This option can be disabled in Preferences > Import > Enable hardware accelerated decoding.) You said that you are on Windows and that your footage is HEVC, which is not yet accelerated, but because the decoder libraries for both H.264 and HEVC are closely coupled, the fact that your Intel GPU was disabled may have caused some sort of downstream failure in the software HEVC decoder.

    Regardless, it appears that you've solved the problem, and I'm glad to hear that. If you continue to experience issues, I recommend you contact my co-workers at Adobe Customer Care to assist you with troubleshooting the problem. You can open a case with them via call or chat at this link: https://helpx.adobe.com/contact.html

  10. 194 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

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

    > Agreed, some time ago there was a new feature that said AE can play some video formats directly, without caching - that is bull.

    It is not bull. But your description is not accurate, and the functionality is limited.

    When you start a preview in After Effects, assuming the Cache Before Playback option is not enabled, After Effects will pre-cache video footage (video footage formats only: MOV, MXF, etc.; still image formats aren't included) into it's RAM cache as fast as it possibly can, prior to playback. Basically, this means that as playback moves forward, After Effects will copy frames from the footage into the RAM cache for playback as fast as it can; you can see the green cache marks fill up in the timeline ahead of the CTI. This differs from other cases where After Effects will load the RAM cache one frame at a time as they are rendered, instead of pre-caching the frames without additional rendering, as happens in this case. (That said, After Effects always tries to load frames into the RAM cache as fast as possible. If the comp can be rendered faster-than-real-time, you'll see the green cache marks advance ahead of the CTI, so there's nothing terribly special about this behavior.)

    The major limitation here is that there must be no rendering involved. Only unaffected footage in a comp qualifies for this optimization. Any rendering (transforms, effects, blending modes, color management, etc.) will force the frames into the usual process of rendering before pushing them into the RAM cache.

    The other limitation here is that After Effects can't decode some footage formats quickly. Decoding and debayering 8K raw R3D frames, for example, isn't likely to decode quickly enough to take advantage of this optimization. (Although enabling GPU acceleration in the project settings can help a lot with this.)

    Overall, this is a small optimization, but it is helpful in certain cases and helps streamline the overall rendering pipeline.

    In regards to the overall concept of disk playback vs. RAM playback, I agree that it would be a useful improvement for After Effects.

  11. 7 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

    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.

  12. 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 →

    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.)

  13. 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

    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?

  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

    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.

  15. 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

    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.

  16. 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 » 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.

  17. 8 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 →

    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.

  18. 4 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

    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.

  19. 21 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 » User experience/interface  ·  Flag idea as inappropriate…  ·  Admin →
  20. 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 » 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.

Feedback and Knowledge Base