If I use Master Properties to edit text inside a pre-comp, I get a "string memory leak" error when I quit After Effects. If I then clear the custom text by clicking the "Pull from Master Comp" icon, and then save and re-open After Effects, I no longer get the error (at least until I edit the text again through Master Properties).

As an example, I have attached two files. The file with text edited through Master Properties gives me the error upon quitting AE. The other file is identical, except that the text has not been edited through Master Properties, and it does not give me the error when I quit.

Exporting from premiere I got an "Unable to create frame" error on an AE linked comp (error code -160962695). The comp was an animation of a PNG graphic with some Mesh warp "glitch" effects.

Tried to render from AE, initially got an error about the memory requirements of the frame while in 32bpc color (error 12804) but after switching to 8bpc I started to get a different error, after that point it was the same error in either 32 or 8pbc.

The final error was a Bad parameter error (error 516) and I discovered that it was the animated Mesh warp effect that caused it. Redid the animation for the effect and that fixed the issue.

If you resize the composition using the "Crop Comp to Region of Interest" feature in version 17.5.1, there will be a difference in the display between 2D and 3D layers with the same X and Y numbers.
It didn't happen in versions prior to 17.1.4.

The following reproduction procedure
1, Creating a composition
2, Create a new layer
3, Resize the composition using "Crop Comp to Region of Interest"
4, Check the 3D layer.

Other than "Crop Comp to Region of Interest", the same phenomenon occurs when resizing with "Composition Settings / Advanced / Anchor" selected other than the center.
Also, if you open a project file saved in version 17.5 or later in version 17.1.4 or earlier, the displayed position will change.

The workaround I've found is to place the camera layer to restore the display.

Thank you.

Being able to paste from Premiere into After Effects is awesome, but there is a bug when pasting footage/audio from the Premiere timeline into an already existing composition in After Effects. The After Effects composition will automatically change duration without your input and it won't respect "Paste At Current Time". Do this to re-create the problem.

• Create a new After Effects comp, either from Premiere's "Replace With After Effects Composition" feature, or an independent project. Make it something like 10 seconds.


• Copy any footage or audio clip from a Premiere timeline into an After Effects composition. But make sure the copied clip is from a spot that is well into the timeline, lets say 2 minutes in.


• In After Effects, you'll notice that the copied clip is pasted at the same timecode that it exists within Premiere, at that 2 minute mark. Which is fine, it's a little annoying to have to bring it back to the beginning of the composition, but I can live with it. The trouble is that it automatically changes your composition duration to 2 minutes aswell. It doesn't respect your current composition settings.


• Every time you paste into After Effects your duration will change to a completely random duration depending on where you copied that clip in the Premiere timeline. Try it with different clips in Premiere at different times. Super annoying.


• I've tried "Paste at Current Time" in After Effects hoping that it would paste where I wanted it to, but it still pastes that clip at 2 minutes.

I understand having the ability to paste into After Effects at the same timecode that's in Premiere, that can come in handy alot. But lets have an option to just paste that clip wherever the playhead is, just like you can pasting layers within After Effects. And then lets also not have the After Effects composition change the duration settings on you every time you paste. I can't imagine a situation where you would actually want the comp duration to change on you like that, but if there is an need for this that I can't think of, can we atleast have it not be the default behaviour?

If a valid json footage asset is imported into a project and used for Expression data in a layer, and it is subsequently overwritten by an ExtendScript process, After Effects CC 2019 will not auto-refresh the JSON footage item in the project nor in any layer referencing the JSON footage layer. Choosing "Reload Footage" on the json footage item does not seem to do work either — this this did work in CC 2018. However, if focus is removed from AE, and a different process opens and overwrites the source of a JSON footage item, then focus is returned to AE, the JSON file updates immediately.

It seems like the method by which After Effects "refreshes" or "re-reads" changes to imported JSON files needs to be addressed. At least on macOS, it seems like writing to the imported JSON file via an ExtendScript is likely not being broadcast as an fsevent which is what AE might be latching onto to detect changes to the file.

Expected Result: When an ExtendScript process writes to a JSON file imported into After Effects, the corresponding data and any expressions using that data are updated immediately upon write.

There seems to be a bug when working with parametric ellipse paths in tandem with trim paths.

It only seems to occur when the Start or End properties in the trim path are set to 50%, while the other is set to 0%. I've attached a couple videos for reference.

When the ellipse path position is adjusted the ellipse path will occasionally close itself, resulting in an unwanted half-circle. The half circle is a result of the Start property set to 0%, and the End property set to 50%. However, when the values are swapped (Start: 50%, End: 0%) it results in a completely different shape entirely.

Changing the group position in the layer doesn't cause this, and neither does the layer position. Other values for Start and End didn't seem to cause the issue either, only the 50/0 combination.

Some known workarounds include:
- Setting the value to something very close but not visibly different, such as 50.0001%
- Using an if/else expression to prevent a frame landing on 50% if the property is animated.
- Adjusting position with the group transform or layer transform properties

This has been tested on multiple machines running the latest version of After Effects (15.1.2), and while the issue occurs at varying positions, it seems to always result in the same shapes being created.

When attempting to add a sourceRectAtTime() expression to a Mask Path property that references a text layer, After Effects will immediately crash upon evaluation.

Reproduction steps:
1. Create a new project
2. Create a new composition (tested with HDTV 1080 29.97 preset for repro purposes)
3. Add a text layer
4. Create a comp-size solid
5. Add a comp-size mask to the solid by double clicking the mask button
6. On the "Mask Path" property of the mask created in step 5, add the expression: `thisComp.layer(<nameoftext_layer>).sourceRectAtTime()

After clicking out of the expression editor and allowing AE to evaluate, After Effects crashes.

OS: Windows 10 Pro
OS Build: 19041.572
AE Version: 18.0.1 (Build 1)

Since a couple of updates I've had this weirdest glitch.

On imported RAW images, when the preview resolution is set to anything less than "Full", the layer's gamma suddenly gets waaaaay off.
This only happens if "Linearize Working Space" is checked in Project Settings.
I've also reproduced this bug with .dng instead of .RAF, so the RAW image format does not seem to matter.

Currently using AE 18.1 on windows 10, Camera Raw is up to date and this glitch happens whether GPU acceleration is on or off.
Unfortunately I can't seem to find on which version thig bug appeared, since I do not have access to anything prior to 17.7 and the glitch is still present there.

It is possible to compensate the layer's gamma offset manually, but it's still a major workaround to get the preview working properly.

I have attached two images and also made a small project to show this issue. If anybody wants to look into this, you can simply switch the composition_01 resolution from "Half" to "Full" and the bug shoud be pretty clear.

Here is the project: https://drive.google.com/file/d/1ensmhOuLroMKAdCmpdrynHDOw8J40TjH/view?usp=sharing

Thank you for helping me out!