Hi,
I didn't know where to report bugs. So I'll do it here.

Project structure in PP after export from AE 2020. Everything looks like it should

After Effects 2021/2022 versions export project to Premiere Pro with errors. The project structure breaks and duplicate elements appear, if you try to remove the duplicate, the original will also be deleted. Items from their folders end up in the root folder

I don't update new versions right away. But there was a need to update. And I was surprised that this bug has existed for several years and has not yet been fixed.

Please let me know if you are aware of this issue and if you plan to fix it?

Sincerely

The internal X-OCN debayer results a) in clamped Highlights even in 32bpc and is b) slightly less sharp.

I compared AE to the Reference DeBayer from Sony (Same as SCRATCH & Resolve in Sony Mode).
Presumably AE debaters in Standard and not in High Quality Mode. Sadly there are no settings possible beyond Colorspace in AE.

And: AE shows a black image and is laggy when enabling linearised workflow and crashed when you try to simulate a Display Workspace in Color Managed workflows.

The DeBayering pipeline seems to be broken / low quality and should not be used in an 16bit Workflow when used natively.
Alternatively export EXR Sequences from RAW Viewer, Resolve, SCRATCH at RGB half (16bit float) with ZIP-Compression for better playback Performance.

AE randomly stops saving projects; Save, Save As, Auto Save, Collect, Quit application prompt to save, none of them work; not grayed out, they’re still clickable, just nothing happens and you still see the black dot within the red circle on the left top corner, and when you quit the application and click save at the prompt, it’ll go ahead and close the application but not save.

It happens at random times, sometimes couple of minutes after I open the project, sometimes couple of hours. So far the problem only developed after working on the project for a while, but if a project has this issue even once, then my experience is it will have it FOREVER on that project. Tried creating a new project and importing the old project into it, does not work, once it’s gone, it’ll be a randomized time bomb, you’ll never know when it’ll stop saving.

I’ve had the same problem happening for the second time now. First time I encountered it being a month ago on a different project, with plugins. Thought it was a plugin issue or the project got corrupted (somehow?), talked to Adobe support, they couldn’t fix it and I just moved on.

Now a month later, I’m having the exact same problem after working more than 10 hours on a brand new project, without plugins, on a newer version of AE, newer macOS build, new assets, less plugins installed than before (all up to date).

I’m on a MacBook Pro M1 Max. Have been using it since January, never had any issues.

I believe it happened after the native m1 support update (which was 22.3?).
Opening Intel/Rosetta version or not, problem persists on both.

Gave AE a lot of access under privacy and security, changed the folder permissions (of Adobe folders, documents / library included, and the project folders) to read & write (on all profiles), even created and logged in as root user, nothing.

This time it started with the preview not updating when I undo something. Soon after it started not saving so I just had to lose my work. Exporting to Media Encoder queue is an option, since it’ll create a project file, but it won’t retain all the files/comps (as far as I know, just the ones linked to the comp you sent to the queue).

Already uninstalled and reinstalled AE, didn’t fix it, so my only option is to uninstall all Adobe software via Adobe’s cleaner tool and see. Wondering if anyone had something similar on an M1 Mac or on another device, and hoping someone has a solution so I don’t have to do a clean install.

Update: After checking forums and Reddit threads and seeing similar problems, I checked whether if I can trigger this problem and I was successful; when I turn off Wi-Fi, it won’t save, turning Wi-Fi on after doesn’t fix it unless the project is restarted. Since I always had my Wi-Fi on before I encountered this problem, my guess is that whenever there is a disturbance in Wi-Fi signal it triggers this behavior. Tested with two different physical locations, 2 different service providers with different speeds and different routers.

Currently the anchor point on comps and templates can only be set to an outside edge or the center. Instead provide an actual field in the composition settings where you can enter the anchor point. Clearly for any layer you can move the anchor point to a specific location, so this isn't a foreign concept. I've been creating templates and the most annoying thing is that in a complex template I can't set the most useful anchor point. The user of the template must either deal with the fact that they won't be able to rotate/animate/etc. the template usefully unless it is fully balanced, or they need to figure out where the anchor point should be every time they use the template. Instead I want to provide the proper anchor point and avoid all doubt (not only speeding up their processes, but mine as well). You could keep the existing arrow control and allow them to toggle between that and providing the proper anchor point, but I would just have the arrow control update the field and then allow them to change it.