Hey,

From what I read I understand that this is common problem.   We try to avoid P&Z and stopped using Moving Pictures.  Now we get this error with IllusionFX like FluidMorph.  The only fix we found so far is render without monitoring video tracks.  Anybody else having these issuses?

xw8400; SN 1.8.1

thx

-matt

There seems to be something involved that is going heavy on your memory.

We used to have this problem often with the Pan and Zoom. It would occur when there were many unrendered Pan and Zoom effects on the sequence. Holding all that information in the system's memory was taxing. Now, we render each Pan and Zoom effect as we apply them. Once rendered, the system doesn't need to store the info in the memory.

Do you have a lot of unrendered effects on the sequence?

What are you applying the FluidMorph to?

No, there are no unrendered fx on the sequence.  FluidMorph is being applied as a transition between two stills (not P&Z).

Have you tried restarting? That would clear your system's memory.

I actually hit this last night trying to apply a fluidmorph effect. The application memory used was only at 34 percent. This is a bug. I'm going to test some more today and see if I can make it repeatable.

PS: The trick to getting bugs fixed is to find a way to make them repeatable. If the engineers can follow certain steps and be able to reproduce your bug, then they can work on fixing it. If you find a repeatable way to make a problem occur, post it here and I'll bet it will get to the right hands.

Yasch:

Have you tried restarting? That would clear your system's memory.

I thought one of the reasons that we work with NLE is that you don't have to restart everytime you want to put on an effect.... but again I might be wrong :):)

--

We were able to make it happen few times but there was no pattern or steps you could follow.  After full reboot, and spending some time editing (app memory was always around 35 to 48%) we tried to render FluidMorph effects.  First one usually went fine and when we tried to render the second one we got "out of memory" error.  We've also been getting 'AVX Execute Exception' error when trying to render those fx.  I'll try to find a pattern in what we do to make them happen.