I was putting together a video which had not that many elements which was running smooth throughout the process. Mind you we are running these programs on iMac Pros so it should not be a problem. The video in total was about 2min & 2sec. The problems started to arise when I started to render through Adobe Media Encoder. The render itself took about 35 to 45 mins which is odd. With the number of elements running on the video plus the iMac it’s also running on should not take that long. While rendering I was scrubbing back and forth to see if everything was smooth. That’s when I notice that the video started to glitch. Elements of the video started showing up then disappearing. Going into the comps of the video, the .MP4 element seem to have nothing wrong with it. After the render was complete, I noticed the same glitch in the video. I restarted the program and noticed the same glitch again. I went a step further and restarted my computer to see if that would fix the problem. When I opened up AE again the .MP4 element was completely missing. The final thing I could think of to fix the problem was clear all my disk cache and then restart the program. After doing that I went straight into rendering without scrubbing through AE. That seem to do the trick… for now, but since I work on videos on the daily how do I know that this won’t happen again.

Have anything divided by zero, default to zero value instead of undefined.

In expressions when you divide by zero, it causes the expression to break. it would be cool if AE was smart enough to ignore this and just pretend that anything divided by zero had the value of zero. so we don't have to put if/then statements into our code to avoid this.

an example is if you are using expressions to keep the stroke of a shape layer constant as it scales. the expression looks somewhat like this.

stroke/scale/100

if scale is zero, it breaks, but if the scale of the layer is zero, you can't see it anyways and so having it automatically have a value of zero would be just fine.

Change my mind.

Bug report:

Some worrying behaviour with the latest Adobe After Effects Version 16.1.3 (Build 5).
AE Process may stop responding while doing something intense, tracking in Mocha AE or saving a project.
Saving work may become impossible or saving may take something up to 40 minutes!
Also, iMac OS may become unresponsive needing to hard reset your Mac - losing a lot of work. A couple of times iMac has rebooted itself after freezing.
When this happens both CPU and GPU loads are nothing alarming. RAM is not filled either.

Projects are 32-bit, linear. Using Metal GPU acceleration.

I thought it may be macOS related, some hardware problem in my Mac or faulty Fusion Drive. However, no test shows any problems. Reinstalled operating system from scratch, reinstalled all software and retrieved older system state from the backup. No help so far. I was thinking to scrap everything and take my Mac to get some expert service until I read about similar problems:
https://community.adobe.com/t5/After-Effects/AE-2019-Mojave-Continuously-Freezing/m-p/10252001#M75867

Problems seem to be related to After Effects or After Effects Render Engine.
Today when latest freezing occurred, also my Wacom driver stopped responding.
CCLibrary process as well…

Photoshop did not freeze, so it is not all Adobe.

Machine specs:

macOS Mojave 10.14.6

iMac (Retina 5K, 27-inch, 2017)
Model Identifier: iMac18,3
Processor: 4,2 GHz Intel Core i7
Memory: 40 GB 2400 MHz DDR4
Graphics: Radeon Pro 580 8 GB
ROM Revision: 113-D000AA-931
VBIOS Version: 113-D0001A1X-025
EFI Driver Version: 01.00.931
Metal: Supported, feature set macOS GPUFamily2 v1
3TB Fusion Drive

All projects and material on external RAID: LaCie 6Big with latest firmware versions.
Thunderbolt 3 connection.

Regards
Jari Hakala

When alt clicking a property on a layer to add an expression the editor box because super tall with the cursor stretching the entire size of the editor. Because of this you cannot see what you are typing or select the text. Anything you do is completely imperceptible until you hit enter on the number pad. Once you do that you can see what you typed, but as soon as you go back in to make a change the editor because impossible to use. I tried contacting support, but they were unable to comprehend what the issue was even after showing them live. They kept trying to direct me to the forums on how to use expressions, which is NOT the problem. I have attached images to show what happens. "ex3" even shows the preferences menu which is missing all the example text to simulate formatting. I have tried resetting my preferences, rolling back AE, and even re-installing. Nothing seems to work and as a result I cannot use expressions in my work.

Is this where to do bug reports? Whatever, this is where I'm doing it.

Create an animation in a composition, somewhere in the middle. Create a protected region there. Also create a master property. In my case I added fill and added the color.

Now insert that into another composition. Hit play. Should work ok.
Now hit continuously rasterize.
You Should get an error that AE needs at least 2 frames to play back.

Honestly, this Sort of makes sense. I want to continously rasterize the vector graphics from there, but since I'm changing the color, it shouldn't work? It's a bug because it seems someone at Adobe forgot about someone trying to do that. Rather than throwing an unrelated error, it should say something more like, "you can't mix continously rasterize and ____ feature." I'm not sure which part of the features are breaking this.