Skip to main content
Known Participant
December 7, 2013
Question

constant warp stabilizer crash with CC AE

  • December 7, 2013
  • 12 replies
  • 21379 views

I have used warp stabilizer a lot in the past, and don't recall it ever crashing. Today, it will does nothing but crash. I have warp stabilizer with 4 different pieces of footage, and every attempt results in a crash. On two occassions, immediately after completing the analyzing process (1st step) AE went into auto-save mode, but the progress indicator never started. Activity seemed to cease for 3+ minutes, so I assumed the worst and chose to force quit. Other attempts simply crash immediately after the analysis step.

The footage I have tried to stabilize is 1920 x 1080 MTS and MOV files. I have worked with the files before, and they play back fine, showing no sign of corruption. FWIW, I tested one of the video files in CC Premiere Pro and warp stabilizer worked without crashing.

I rebooted my Mac, cleared all AE caches, rebooted AE a second time, tried to stabilize new footage, but same results.

My machine is a Mac 5,1 with 32GB RAM, OS X 10.8, CC AE 12.1.0.168

Any suggestions on how to proceed would be appreciated.

    This topic has been closed for replies.

    12 replies

    Participant
    December 3, 2014

    So this is still not fixed?

    The only thing everyone seems to have in common is that we are on the late 2013 6 core mac pro.  Doesn't matter how much RAM you have.  Although seems like someone in here is able to do a 20 sec clip which I would kill for.  I have 16gb ram and I can only do 1 second.  I'm trying to do a 400 frame shot.

    I've closed out of all other apps and it still doesn't work.  Funny thing is that I did this a month ago to a bunch of shots that were all roughly the same length and file format (r3d) and it worked. 

    Also btw Adobe... turning off autosave doesn't fix this. 

    This needs to be fixed right now. 

    Participant
    December 3, 2014

    Actually I fixed this issue. My issues were happening when attempting to open prior CC or CS6 projects. So here's my suggestion that worked for me:

    1. Do not open old projects.

    2. Create a brand new empty project with the latest CC version.

    3. Now import old project into this one (entire project or sequence does not matter - both worked for me).

    4. Relink media if necessary.

    5. Whalla - everything worked as per the usual from there on out...

    Lonnie

    Szalam
    Community Expert
    Community Expert
    April 21, 2015

    update fixed the problem


    ovideomovies wrote:

    update fixed the problem

    Yay!

    Participant
    November 12, 2014

    Same issue here... Come on Adobe - the problem is too consistent among different users for it to be user/random error. This isn't my first rodeo either. Adobe - please try sending a clip from a PP timeline via Replace w/AE Comp, add WS, and as soon as the last frame is analyzed - the program automatically auto-saves and hangs. It never use to do this. Mac Pro 5,1 6-Core, 32GB ram, 10.8.5, AE 13.1.1.3, the clip was XDCam EX 1080p 29.97, 6 seconds in length.

    ...and Todd - turning off Auto-Save via preferences does not fix. It still attempts to auto-save on the last analyzed frame and then hang up (spinning beach ball).

    Installed RAM: 32.00 GB    Current RAM Usage: 3.09 GB    Allowed RAM Usage: 24.00 GB

    Process ID    Application Name    Min Needed Memory    Max Usable Memory    Max Allowed Memory    Current Memory    Current Priority  

    533    Premiere Pro    0.50    32.00    5.12    1.91    3 - Low  

    548    aerendercore    0.00    32.00    4.62    0.91    3 - Low  

    551    After Effects    0.40    32.00    14.26    0.27    1 - High  

    Thanks,

    Lonnie

    Participant
    November 12, 2014

    I may have to eat some words - but perhaps we have a smoking gun... this was an old edit that I had to make changes to and the timeline is long. And I "thought" all the clips were original Xdcam EX - but after enlarging the timeline - the clip that wouldn't WS in AE was an h264 mov file - rendered out from Media Encoder, and reimported into the project. I'd like to think AE's warp stabilizer is codec agnostic - but perhaps this is not the case. I found the original Xdcam EX mp4 file, "replaced with AE Comp" from a PP timeline, and the WS worked as it should have....

    Thoughts...

    Thanks,

    Lonnie

    Participant
    October 24, 2014

    If you're on a Mac, try turning off Spotlight. The way it was explained to me is that Spotlight constantly wants to update the files. Warp Stabilizer constantly updates the files. Stack overflow.

    I find this works for me. And if I turn on Spotlight, Warp Stabilizer crashes all the time. (Not playing pre-rendered previews, but making new Warp-Stabilized clips.)

    Hope this helps someone. I find it a hassle, obviously, that Spotlight is off. I turn it on from time to time to rebuild the cache so I can use it to find files. I also do Unix find commands in the Terminal, a bit of a hassle.

    I'm using CS6 on a MacBook Pro laptop with 16GB RAM, 500GB internal, etc. Fine but not outstanding, always crashes on WS when Spotlight is on.

    Participant
    November 3, 2014

    finally, the spotlight deactivation worked (mac pro 6-core)... big thanks!

    Participant
    October 20, 2014

    looks like the latest update from Adobe has fixed this on my system.

    bitstreamtv
    Participant
    October 23, 2014

    We are having this issue as well, fully updated. Mac Pro 6 core with OSX 10.9.5

    Participant
    September 30, 2014

    I'm also stuck at the auto save loop. Is there anyone who have found a fix for this?

    Todd_Kopriva
    Inspiring
    September 30, 2014

    For now, the surest way to avoid this problem is to turn off auto-save.

    NeonHeatDisease
    Participant
    October 1, 2014

    Im still getting the error even with autosave turned off. Mac pro 6 core. Infuriating.

    Participant
    August 26, 2014

    I got the exact same problem, auto save loop after warping. Tried different location of project files, cache files, file formats etc. But still this.

    I am also on a Mac pro, 6-core, 16gb Ram.

    Participant
    August 26, 2014

    Has there been any development with this? It is very frustrating.

    Community Expert
    August 26, 2014

    Just a little FYI on all four of the Macs that I am working with on a daily basis I have not been able to reproduce this problem. Warp stabilizing any footage that I have put into the system so far as work just fine. Please note that the shots that I have picked for Warp stabilizing have a lot of detail and are shot with professional cameras. I even tried some iPhone footage this afternoon and that worked just fine.

    Participant
    August 26, 2014

    Holy Smokes, I may just be an idiot.  I closed all other apps I had open (mail, safari and what not) and it worked fine.  Well it did do one auto save randomly a bit after but a massive improvement.

    Participant
    July 9, 2014

    having the same issue. Brand new machine and brand new Adobe CC install (running after effects 13.0.0.214). Doesn't matter if i try to use warp stabiliser on a TIFF sequence or a prores 4444 or a prores 422, still getting a crash after the analysing finishes.

    Participant
    July 9, 2014

    FWIW, I installed After Effects CC in Boot Camp under windows 8.1 Pro (Mac Pro Late 2013, 64 GB RAM) and had no problems completing a warp stabilizer VFX analysis and stabilization. The problem is likely Mac specific.

    Participant
    June 1, 2014

    FWIW, I've been having the exact same issue on my late 2013 6 core MacPro with 64 GB of memory. After the first analysis pass of warp stabilizer, an autosave is triggered (despite it being disabled) that never progresses past 0% and AE becomes unresponsive. Strangely, I have no issues (other than being very slow) with applying Warp Stabilizer VFX to the same footage from AE running on my MacBook Pro Late 2013.

    I'll try the steven command and report back before I give up on using my MacPro.

    Participant
    June 1, 2014

    After trying sudo echo "setenv KMP_DUPLICATE_LIB_OK 1" > /etc/launchd.conf (which, incidentally, repeatedly denied me permission and required that I log in as root to use it), I now get the error "unable to acquire rendered frame" during the analysis phase of Warp Stabilizer VFX.

    If I click okay, the analysis proceeds as normal and then the same error as before, where the save dialog appears and everything freezes occurs.

    Participant
    May 19, 2014

    Everyone experiencing this problem, could you do the following:

    1. Open the Terminal Application.

    2. Paste in this command: sudo echo "setenv KMP_DUPLICATE_LIB_OK 1" > /etc/launchd.conf

    3. Reboot your system.

    4. Now run Warp Stabilizer in AE.

    5. Please report back here with your results (crash resolved or not resolved).

    Thanks!!!

    Paul Uusitalo

    After Effects Quality Engineering

    Participant
    May 19, 2014

    Note, after pasting the command into the terminal, then hit "Enter".