Welcome to TVPaint Community forums !

I just tried to render a scene that includes some motion keyframer fx stack, but the fx does not render for the output. I need to apply fx stack before rendering.

Is this really not possible?

Hi RUne,

I'm not sure to understand what you mean. Do you mean you cannot see the keyframer's preview without applying it ?

no, I am exporting the scene as a quicktime in order to see it play realtime without dropping frames.

The FX stack doesn't "render" to video file output. You need to "render" (= apply) it to a layer, then export the project. This makes sense because in most cases you'll have more than one layer.

As fo getting a reliable preview: with bigger project dimensions it might help to play around a bit with the preview settings.

In that case, change the proxy settings (Windows > Settings > Preview settings)

Check the options :
• Background Proxy Render
• Force Proxy Render
• if you are not using a powerful computer whereas your project is really heavy, you can lower the quality.
• if you want also to watch all images, check "play all".

yeah, I figured that would be the workaround.

However, I think it would be better if one would have the option to render fx for exporting playblasts.

I think it would be great if there was an option to render the FX stack on export, without rendering it before on the layer itself - it would save time and hard-disk space, and whats more important - the layer would remain non-"destroyed", which is very important when need to make some changes later. But this would probably require to attach each FX stack to a specific layer, otherwise the export would only render one selected layer and that's it... That's the way FX stacks work now. I already asked before about a possibility to attach FX stack to each layer, but as I was explained it is not yet possible and doesn't seem to be in the nearest future... or will it?

Soom wrote:I think it would be great if there was an option to render the FX stack on export, without rendering it before on the layer itself - it would save time and hard-disk space, and whats more important - the layer would remain non-"destroyed", which is very important when need to make some changes later. But this would probably require to attach each FX stack to a specific layer, otherwise the export would only render one selected layer and that's it... That's the way FX stacks work now. I already asked before about a possibility to attach FX stack to each layer, but as I was explained it is not yet possible and doesn't seem to be in the nearest future... or will it?

+1

I don't know if it's possible (I think it could be), but it's a great idea

Elodie wrote:I don't know if it's possible (I think it could be), but it's a great idea

I think if the developers could look into it, many people will praise TVPaint even more

changing preview settings doesn't help at all on previewing any keyframer transformation. The computer I work on may be the issue (only 2 cpus and 4Gb ram). Still, I would have thought Background Proxy Render would render it.

Soom wrote:

Elodie wrote:I don't know if it's possible (I think it could be), but it's a great idea

I think if the developers could look into it, many people will praise TVPaint even more

It's on their to do list now

brilliant! Thanks alot

ryberg wrote:changing preview settings doesn't help at all on previewing any keyframer transformation. The computer I work on may be the issue (only 2 cpus and 4Gb ram). Still, I would have thought Background Proxy Render would render it.

As far as I've figured out, at least in TVP 9.5, the render proxy option doesn't help at all, no matter what kind of machine you have - we had to turn off all the proxy render options in order to get an acceptable preview. There was a topic about it somewhere in the forums, but no real solution then - don't know how about TVP 10...

Elodie wrote:It's on their to do list now

WOW! Thanks! Will it also look into attaching FX stacks to specific layers, or only rendering the preview on export?

I can't answer you Soom, I'm not a developer :p

And the "to do" list means "something we have to peek an eye on in order to define how long it would be to add this in the software and, of course, if it's possible :p"