Skip to main content
Participant
August 5, 2021
Answered

Rotobrush tool crash After Effects

  • August 5, 2021
  • 4 replies
  • 6625 views

Hello. 

When I try to work with rotobrush, I make it on first frame and then when I push space or cmd + → to move forward, After effects just closed without any messages. 

I use Macbook M1 with lastest Bigsur. After effects 18.4. 
I also try to reinstall After effects, and I try 18.2 version. Still dont work. 

This topic has been closed for replies.
Correct answer Rick Gerard

The bug is caused by the IOS 11..15.1 updates. It is documented, bug reports are filed, and every available version of AE will crash immediately if you try and propagate Rotobrush. We will have to wait for an update. It may take a while. Premiere Pro, Audition, and a bunch of other Adobe apps are already Universal (M1 compliant) but After Effects, even AE Beta is still a universal app that needs to run under Rosetta.

 

Most of the time, before I run an IOS update or a Windows update, I make a bootable copy of my boot drive co I can roll back in a couple of minutes if there are problems. This was one time I got caught so my M1 Mac is useless for Rotobrush until an update fixes the bug caused by Apple "improving" security. It's a killed background process that causes the crash.

4 replies

ColbyFulton
Known Participant
January 18, 2023

This is causing one of my projects to crash. It's 2023. I'm on a mac m1 max. Hitting caps lock prevents it from crashing, and selecting Version 1 Classic in the drop down. But WTF? It worked when I built the project just a week ago.

keithm1972
Inspiring
January 20, 2023

Same thing happened to me. My project worked fine after hours in the session, then I come back to it a few days layer and it crashes in seconds.

 

How do you select Version 1 Classic? Which dropdown?

Participant
April 20, 2023

What is your os version


And your after effect version 

Participant
November 3, 2021

I moved the rotobrush setting back to 1.0 classic and it seemed to fix the issue for the clip I needed. 

Participant
October 4, 2021

As mentioned by Rick Gerard, Its the update that is causing the crash. 

But I found a workaround, 

Once you did painting with roto brush, before proceeding to the next frame.

Change the roto brush version to classic.

It works that way. 

Note : But even after IOS 11.6 update the crash continues.

 

 

Yiannis72
Inspiring
October 19, 2021

I had the same problem and I noticed the following: When my working space in in "None" I have no problem with Rotobrush. When I activate a specific working space color profile (for examble, I am always working using the color profile of my monitor calibration) then rotobrush crashes. If I have working color space off, it works fine, if it is on, it crashes. So I do my rotobrush work with no color space and after I am done, I reactivate the working space. If I use "None" as my working space, then I am not having any issues.

Participant
October 25, 2021

I tried your solution but it didn't work on my laptop Macbook pro M1 with the last version of After. 

 

Rick GerardCommunity ExpertCorrect answer
Community Expert
August 5, 2021

The bug is caused by the IOS 11..15.1 updates. It is documented, bug reports are filed, and every available version of AE will crash immediately if you try and propagate Rotobrush. We will have to wait for an update. It may take a while. Premiere Pro, Audition, and a bunch of other Adobe apps are already Universal (M1 compliant) but After Effects, even AE Beta is still a universal app that needs to run under Rosetta.

 

Most of the time, before I run an IOS update or a Windows update, I make a bootable copy of my boot drive co I can roll back in a couple of minutes if there are problems. This was one time I got caught so my M1 Mac is useless for Rotobrush until an update fixes the bug caused by Apple "improving" security. It's a killed background process that causes the crash.

vahabs418073
Inspiring
August 6, 2021

It there a way to turn off the OS function of killing background process that causes the crash???