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

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; renaming to .thisisazipfile is OK. B) Post a comment here when you have sent the email. I need to manually check that inbox.)

Thank you for filing this bug report.

We need more information in order to investigate this problem.

• What OS and version are you using? i.e., Windows 10 or macOS 10.14
• Are you able to reproduce this problem, or does it only happen once?
• Do you get any error messages associated with this crash? If so, what do they say?
• Do you get the Adobe Crash Reporter dialog? If not, choose Help > Adobe Crash Reporter from inside After Effects. We like receiving crash reports, and prefer that you use the “Always show this dialog” option so that you can fill in the additional information after the crash. When the Adobe Crash Report dialog appears, please always provide notes about what you did before the crash occurred. If you have filed the bug, please include a the bug number in the notes. We also appreciate if you fill in your email address and check the “Yes, Adobe can contact me” option; we may contact you if we need to follow up with you about the crash.

Can you give us more detail on specifically which plug-ins were causing After Effects to hang during launch?

After Effects already does this when it can, but detecting the cause of crashes is not as simple as it seems as first. The cause of the crash may not always be clear, and may not necessarily be the plug-in itself but After Effects crashing due to a bad (or valid) request.

For example (theoretically; this is a simplified example, not a real-world case), using the After Effects API, a plug-in may request After Effects to allocate some memory that is more than is available on the system. The bug is clearly the bad request from the plug-in, but if After Effects doesn’t trap that request and reject it, After Effects could end up in a bad state and crashing.

That’s why we need to know what specific plug-in is causing the problem. If it’s making a bad request to After Effects that isn’t being handled gracefully, then we have improvements to do on the After Effects side, as well as notifying the plug-in developer of what went wrong.

Thank you for filing this bug report.

Is this on Windows or Mac? Which version of the OS?

Can you provide us with specific steps that cause the crash? ex., Apply Curves with X settings and add X number of masks. Or whatever steps lead to the crash.

Or, could you send us a project file that demonstrates the problem? You can post a link here, or if you prefer you can send it to aebugs@adobe.com. Please post back if you send an email, as we need to check that inbox manually.

A crash log would also be helpful. Do you get the Adobe Crash Reporter dialog? If not, please choose Help > Adobe Crash Reporter, and set it to always show the dialog. When you get the crash, make sure to add a comment. We also like it (but it is not required) when you include your email address and check the fist box that allows us to contact you about this issue; the engineer who tracks our crash reports can respond back if he needs more info.