"Unable to acquire rendered frame" while using Warp Stabilizer while Dynamically Linked

Hi JakeSully,

I'm working with 6K and 8K .R3D files that are zooming in and out on a 4K UHD timeline (Not sure if that's important to note.)

As I understand it, you're having performance and unexpected behavior issues when performing effects tasks with a computer that has what you feel is adequate for the job. Is that correct?

My observations are the following:

• The following items are taxing your GPU on playback and on encoding
  • Warp Stabilizer while playing back and encoding is a GPU-accelerated effect
  • Scaling while playing back and encoding is a GPU-accelerated task
  • Any other GPU-accelerated effect you add, like Lumetri can hinder performance
  • As Dave mentioned, you could pre-render these effects
• You are working with huge frame sizes
  • Delivering at 2K as an alternative might be a better workflow, is that possible?
• The RED format might be too demanding for doing all you expect
  • During Ingest
    • Transcode to a mezzanine codec
    • Scale the sources to smaller frame sizes during ingest to 4K and 6K
• As good as your iMac is, your hardware might not be up to the task
  • This workflow would even be taxing on my much more powerful PC

You could continue generating singular files in After Effects, or try some of these things and report back if you have better results. Let us know how it goes.

Thanks,
Kevin

I'm a bit confused by your use of the word "zoom".   Are you scaling the clips in PP to simulate a zoom, or do the clips contain actual camera lens zooms?  Either way, they'll be tough to use warp stabilizer on them.

I recommend stabilizing the the clips before you do anything else to them, and then exporting them as new clips.  Weird things happen when warp stabilizer is used in conjunction with other things.  Better to start with a clean slate.

And good luck trying to stabilize camera zoom clips!