Correction: the error is NOT present in beta 22.6 (build 33). This is not the latest beta, I'm not updating my beta untill the issue is fixed in the release version 🙂 ... View more

Man, seriously, lots of people are having this error (me included) on many projects. AE team has been notified months ago. They know it's a GPU thing, because they keep suggesting to turn off GPU acceleration (which slows down projects). This is not "project specific", as if it's the fault of the user. It's time for a fix, AE has been unusable for me too for a few months! I thought it had to do with unusual comp dimensions, has this been tested? ... View more

Not Fixed in beta 22.6.1 ... View more

This issue is not yet fixed in the 22.5 beta, can you give an ETA on the release? Because turning off GPU rendering is a big hassle: up to 4x slower on some of my renders... Kills my real-time previews... Thanks! ... View more

Why is this not possible for minor versions? 22.4 contains some major bugs, that make it unable to work on  projects. The team knows and is working on a fix I read. Untill then, I'd like to work with 22.1.1, which is still better than having to downgrade to the last major version I can keep running in parallel (18.4.6). Thanks for the update! ... View more

Hi Tiffany, AfterEffects for M1 is out of beta now: you don't need Rosetta anymore, unless you have old Intel-only plugins. See the announcement on Adobe Blog or download the 22.3 and 22.4 update from your Creative Cloud app. ... View more

Playback in AE is often not real-time. The green bar means that frames were rendered and in ram. What many people do to see faster previews, is to go to the "preview" pallette or (choose Window > preview to show it) and set previews to half resolution and frame skip to "1". These low res previews are often enough to work. You can also shorten the work area, to render only a shorter area. If you check "cache before playback", then the green bar fills up first for your work area, and playback starts only when that area is rendered. This avoids stutters.   Bonus tip: try disabling multi frame rendering. On some computers and projects its slower than the promised speed gains. I've personally never known it to be faster for vector motion graphics on my iMac Pro. ... View more

MFR is off (is always slower than non-MFR on iMac pro), I'm playing back my timeline and the error pops up. When I click it away, there arere 2 more waiting. Playback continues in the background below the error.   I tried disabling layers to pin down what causes it, seems to be several layered PNG sequences using luma track mattes in a precomp. There a shape with a color blend mode too, an exposure effect on one of the layers, gaussian blur on another, Lumetri color on a third. The whole precomp has time remapping applied. Alle comp framerates are 25fps. Preview is set to half res and "skip 1" when error is shown.   I had to downgrade to 22.1.1 to remove the error. Creative Clound updater recently removed the option to "keep previous version" when installing a newer or older version, so I can't send screenshots. To be more precise: to keep older versions, you have to enable "auto-update" in CC preferences, but I don't want auto-update. I need to choose when I update, which is when a paid project is delivered. ... View more

I have this problem after updating on MacOS 12.3.1 Intel, AE 22.3. iMac Pro, Vega 56, 64Gb ram.   No video footage, only imported AI files, shapes and PNGs.   Not fixed in 22.4. ... View more

I have this problem on MacOS 12.3.1 Intel, AE 22.3. iMac Pro, Vega 56, 64Gb ram. Popped up after updating to 22.3 on a project that worked fine before. ... View more

Companies that use Apple tools like Xcode and APIs like Metal to write their software can quickly adapt to changes in hardware (m1) and software (Macos). When Apple launches somethink new, they immediaately release the tools that help you adapt your software. That's why companies like affinity and Maxon can release updates so quickly after Apple announces stuff.   Adobe has historically written software differently. When Apple changes something drastic like an API or new hardware, it can take them a long time to adapt their code base. I think this has been changing over the years, Adobe has really comitted to iPhone and iPad recently. There, they have no choice but to use Xcode. From what I understand, more and more Macos and iOS code is shared. ... View more

It's no unusual to have a feature like this in beta for several months. If I remember correctly, native m1 support has been in beta since october. MFR was tested for 7-8 months if I remember: several rounds of comunity feedback.    There are still several issues being reported here and on other forums, like (too) high RAM usage. I would make sense that the feature leaves beta phase when such problems are not being reported anymore.   Many professionals are waiting for these kinds of problems to be fixed before they switch from Intel machines to M1. There aren't even pro desktop M1 machines yet (Mac pro and iMac pro equivalent). ... View more

I'm pretty sure that's expected behaviour. You're asking the CPU to render multiple frames during previe and export, so all of thr cores are calculating at the same time. So the chip gets hot. If you don't like that, you can disable MFT in settings during preview. That's what I do, one core is enough for my previews. I'm seeing similar behaviour in other apps that manage to use app CPU or GPU cores, like Blender or C4D. ... View more

Watch out: somebody reported "If "Cache Frame When Idle" is enabled and you have a heavy comp and you're in Mocha, you may experience performance issues as both AE (caching) and Mocha (doing things you tell it to) will be taxing your system at the same time."   However, Tim Kurkoski from Adobe replied "A bug fix for this was recently checked in and should be available in After Effects Beta builds soon.The underlying problem is that while the Mocha UI, or any third-party UI, is open in AE, speculative preview may start because no UI activities are happening in After Effects itself. The associated resource consumption slows down the third-party UI." ... View more

If you don't see the beta in your Creative Cloud desktop app under "betas" in the left column, it migjt not available in your region. See screenshot attached. ... View more

Update: Adobe did release masking features in Lightroom but isn't reading embedded ProRaw depth maps or Apple generated semantic maps. ... View more

AE public bèta's can be installed from the CC app, they're listed among the other apps you can install. You should be able to install the beta next to the normal version. File format was shared during the previous beta periode. ... View more

Lightroom iOS is doing a lot of things it's probably not "engineered to do". I recently discovered 8Gb of DNG's I deleted over the years, stored in local file storage. Found 6Gb on my girlfriends phone, ranging back to 2017. We both have HDR duplicates all the time, just as much as files that go missing while processing.   And as for transferring DNG's: I've found many DNG's that can't be transferred using apps in any way. I'm not saying you're flagging them as "in use" or locked on purpose, but if an engineer would have discovered that as a methode to keep fremium clients from getting raw files, you'd never admit to it publicly either 🙂 ... View more

Several third party apps offer deeper access to iPhone files than Finder does. This doesn't always work: files can "be in use" or have the wrong permissions, so they can't be transferred. This might be a deliberate protective measure to keep you from getting the files when you're not paying for a plan. Purchasing a single month of the Adobe Photography plan can be less of a hassle, if you remember to cancel in time. ... View more

Sorry, I didn't think about that. I thought I might have missed a feature in some corner and was ready to be schooled.    I'll try again post-MAX 🙂 ... View more

The only reason I'm using the beta is to have multi frame rendering, so I never turn it off 🙂 ... View more

Hi, I tried to make a video, so I switched projects and the issue seems gone right now. Perhaps the disk cache was full when it happened. I deid reboot since the issue, that might be it as well. Should the problem come back, I'll make a screengrab immediately and turn off hardware acceleration one by one to see if that's the culprit.   Thanks for caring, Sander. ... View more

No: iMac pro with AMD.   Could it be that a difference between frame skip in preview settings (I render every other frame in preview) and comp frame rate make the comp glitch while dragging?   ... View more

During MAX, the Adobe team answered many community questions in real-time. They didn't dodge hard questions, like performance and Apple silicone support. ... View more

If the correct graphics card is showing up in your preferences, if the report there shows that the right features are supported and if your project is set to use hardware acceleration in project settings, the GPU should do a lot in many projects. But it depends on the type of projects you're making: AE has many clients doing widely varying jobs 🙂 I do mostly 1920p vector animations using shape layers or imported AI assets, sometimes 16-bit linear comps of 3D renders.   CPU and GPU usage can fluctuate throughout a render: many effects, tranformations and operations like (shape drawing) use your resources differently. One filter can be single threaded, holding the render down to one core. When that filter is out of the timeline, you see other cores join in. The same goes for GPU acceleration. I have a system widget that shows me how my GPU and videocard ram are working. It goes up and down during a render. When motionblur is on for instance, the GPU is working hard.   Understanding which operations in AE are multithreaded and which are GPU accelerated can really help speed up an animation. In your effects list, click the menu to show only the effects that are GPU accelerated.  This link shows the current overview: https://helpx.adobe.com/nz/after-effects/user-guide.html/nz/after-effects/using/effect-list.ug.html#GPUacceleratedeffects   For operations like shape drawing or AI rasterizing, you can sometimes read in the update notes that GPU acceleration was added. Slowly, most parts of AE are being converted. GPU acceleration is going faster than multicore CPU rendering, but that might change in an update. ... View more