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

    steveezell
    Participant
    May 18, 2014

    Still no resolution to this? I'm on a brand new 6 core Mac Pro and can't get past the autosave loop to save my life.

    Community Expert
    May 18, 2014

    Turn off auto save while your are using warp stabilizer.

    steveezell
    Participant
    May 18, 2014

    I've tried. AE still auto-saves (or tries to) and then crashes.

    Community Expert
    December 7, 2013

    If you have cleaned out everything and you have plenty of disk space for the cache I would first try changing your memory and MP settings. Give plenty of memory to other apps because warp stabilizer is another app.

    If that fails I'd try rendering your files to a suitable DI (digital intermediate) with a production codec that is lossless or nearly lossless and try stabilizing that.

    I'd also trim the clips to just the part that you are going to use in the final production to limit the memory and cache requirements.

    davidp158Author
    Known Participant
    December 7, 2013

    Rick - Thanks for the reply. I have 32 GB on my 6-core Mac. Any suggestions on how I should allocate my memory settings?

    I am having crashes with ONLY After Effects and the Mac's finder open. I'm not clear about how AE manages memory for plug-ins, but I haven't changed memory settings and never had a problem with warp stabilizer and larger files in the past.

    The footage I am trying to stabilize is quite short (less than 20 seconds long). I have stabilized much longer footage in the past, so I rendering to another codec to solve a problem that I never had before seems rather extreme.

    Participating Frequently
    January 20, 2014

    Also, some formats and some shots will just not solve well. This can cause a crash. Trying to warp stabilize a shot from a boat on open water is one example. With nothing stable in the frame the calculations can be so complex that the solution is unavailable.

    If you think your shot should stabilize because there is a lot of fixed geometry in the shot and you're still getting crashes then try rendering an image sequence using jpgs and stabilize the sequence. Try cutting down the length of the shot. Try another shot. Generally, if the footage can be stabilized and the shot is short enough that you don't run out of system resources, Warp Stabilizer works quite well.


    Just for thoroghness Iv'e tried  a radically reduced memory allocation to after effects so that it can leave more memory available for warp which is unfortunatly not recognised by after effects as part of its memory allocation????? this seems like a really round about the houses approach to using one of AFX's inbuild modules, i would much prefer after effects to simple allocate memory to all modules and effects that are a part of of after effects.

    this time it did not bring up a disabling autosave loop but instead failed on the stabilization part 2 of the proceddure.

    i then tried the identical (exported for cs6) warp in CS6 and it handled it easily.

    This is definatly a bug in AFX 12.

    in the past i have warped way way more complex shots and pushed the effect beyond its parameters to great and interesting effect.