[Levi Borland]

If you are only trying to replace the content of the iPhone screen, then a third-party plug-in called mocha Pro is your most direct solve for this type of effect. What is so great lately, is that most of these third-party software companies are not requiring you to purchase the software up front, or buy a year-long license. This allows you to sign up and use the software with a monthly subscription, which may seem like a stretch for some, but if it saves you a few hours and a few trips to the hospital from beating your head against the wall, then a single one month subscription of mocha Pro and a few hours on YouTube watching tutorials on screen replacement, will be your best bet. There are a ton of tutorials online right now that teach you this exact process, to include having your actor interact with the new content you are replacing the original screen with. And the best part is it’s for the most part a pretty automated process, requiring you to only open the software and to make a few selections, followed by allowing the software to do what it’s supposed to do. If you need any help, or would like some more specific directions… I’d be happy to try and lend a hand. I’m pretty sure that this can also be done with the built-in Mocha AE plug-in, without the need of purchasing a subscription to mocha Pro. But let me tell you, mocha Pro it’s pretty sick and absolutely well worth twenty or thirty bucks a month.

[Levi Borland]

I knowI know that you have already tried, and this will sound very level 1 support savvy. However, this very well could be an issue with the installation of Adobe Media encoder. As I’m sure you are very well aware, media encoder we’ll install alongside your installation of Adobe After Effects. Several times now, I have had similar as well as completely on relevant problems working with the new 22 release of After effects. What I would suggest you do, and this works for me most of the time but not always, is to just uninstall After Effects, media encoder, as well as the Adobe Creative Cloud application. Then reinstall the Adobe Creative Cloud collection application, and then of course reinstall both Adobe After Effects 2022 and Adobe Media encoder 2022. For an additional description of what could be causing this problem, it is most likely an issue with Adobe Dynamic linking between After Effects and Adobe Media encoder. I have just within the past few days used media encoder to export a gif without any problems. It isn’t likely any configurational setting on your computer that is causing this issue. So sometimes the simplest way and most direct path is to reinstall the software. Just to save you the trouble and time, I am also suggesting to reinstall the Adobe CC creative app during this process as that has sometimes been a required and necessary extra step from my experience while trying to resolve similar and non related issues here on my end.

[Levi Borland]

So I’m not entirely sure how I fixed this problem for myself, but I did have the exact same issue. What I had to do until the problem went away, was right click on the layer that I wanted to access the effects for on the effects panel. I then went to reveal, and then selected effects in the FX control panel. This then opened up the effects for the selected layer inside the effect panel. Oftentimes however, the effect panel was just a duplicate panel, and the layer that was previously open is still open inside another effect tab, similar to having more than one composition inside the comp View Window available

As I mentioned, I am not entirely sure what was causing the issue that I was experiencing, and seemingly what you are also now having trouble with. I am not even entirely positive that there was something I did to make this problem go away. It may just be something that stopped all on its own. I also have an older version of Adobe After Effects installed and I find myself using that version exclusively instead of the 2022 release. There have been beta releases of After effects 2022 available, however I have had several issues using the beta versions before in the past when trying to use third party plugins such as trapcode particular. For that reason, I have been reluctant to install any of the beta versions. Especially since they don’t outline the specific bug fixes that beta version specifies they have fixed.

Please rest assured that I am aware that I have not sincerely offered you a clear-cut remedy to your problem at hand. Instead I have only offered An Inconvenient manner of getting around the problem. But I did just want to let you know that you are not in fact the only one experiencing this issue, and I’m sure that if you notified Adobe just as I have, and hopefully others as well have oh, that they will identify the problem and fix it in the next release, or at the very least release a beta update specifying the specific issue and assuring that it has been resolved.

 

It has however and treats me that others are starting to talk about the same problem. So I’m going to spend a few hours digging around and seeing if I can once again replicate the problem and figure out if it got fixed on its own, or if there was something I did with inside the settings or workspace selections that took care of my issue. If I find that there was something I had done, and can offer you a more definitive and direct solve on your end, I will be sure to update you.