Page 1 of 1

F8 Bug? Render/saver different from saved file.

PostPosted: Sat Apr 16, 2016 11:37 pm
by Rick Tillery
I have a small project that works perfectly in the Fusion 8 editor, but is wrong when saved to a file. Specifically, I have a bitmap loaded and resized over time using keyframes. The 1st (0) through 15th (14) frames have no resize, and are fine. Starting with the 16th (15) frame, the bitmap begins shrinking. This looks perfect when viewing the final merge node or saver node in the F8 editor:
Image

But, after saving the output file, the 16th (15) frame resize is wrong and the bitmap is even cropped:Image

I had similar issues (but different specific resize/crop failures) with the F8 beta, but I was hoping that the released F8 would work correctly, but no joy.

Here's a shot of the same frame from the timeline view (with the resize parameters shown):Image

I'm also attaching the composition itself. Unfortunately, if I include the background bitmap, the zip file is too big to attach, so I left it out. You can grab it here: http://content-na.drive.amazonaws.com/cdproxy/templink/lHn1K-4fxJe1RYg6d95c_RhdX5BysMK6BszGt1MykEILAYspN/alt/thumb?viewBox=1920 (and rename to 354c06dd474a3e4bb98fd1830316027e-dimmed.png). And the paths appear to be hard-wired full paths, so you may need to tweak them to get the composition loaded.

Can someone please tell me why this is failing?

Thanks!
Rick

Re: F8 Bug? Render/saver different from saved file.

PostPosted: Sun Apr 17, 2016 12:32 am
by Chad Capeland
Don't use Resize. Use the Scale parameter in the Merge, or use a Transform and scale with that.

Resize is integer only, so you'll end up with jittery animation because it can't interpolate smoothly.

Re: F8 Bug? Render/saver different from saved file.

PostPosted: Sun Apr 17, 2016 12:39 am
by Rick Tillery
That seems to work. Thanks!

But it still seems like a bug to me, that the editor view doesn't look like the file.

Rick