Allow rendering in slices

[Vitor Bosshard]

Currently, fr0st won't allow you to render if you don't have enough memory available.

Possible solutions are:
-automatically slice images when memory usage is exceeded
-allow setting of slices in render dialog (This is my preferred option, as it implicitly allows memory limiting as a bonus).

In the case of the second solution, the render would just refuse to start until the user has changed his settings to fit available memory.

[Vitor Bosshard (algorias)]

Some notes:

Sliced rendering can be implemented by making copies of the flame in python and sending multiple requests. However, this requires using a fixed seed to avoid visible seams caused by density estimation.

[Vitor Bosshard (algorias)]

I'd rather get a beta out the door sooner and deal with this later. It's hardly a deal breaker for 99% users. Removing from milestone 1.0

[foundation (brynf)]

I'm one of the 1% that likes to render in high resolution :)

[foundation (brynf)]

Is there anything I can do to help with this one?
Having this there could help with the crashing via to high memory use on flam4 as it could be the default for flam 4 to render in slices that only use 100mb of memory of something like that

[Vitor Bosshard (algorias)]

I am writing a little script to slice and join larger renders. When it's done, I'll need help testing it. Eventually, that logic will be added directly into the render dialog. I will let you know once it's available.

[Vitor Bosshard (algorias)]

As promised, I've released a script to render in slices. It can be downloaded here:

http://fr0st.wordpress.com/2010/06/28/rendering-large-flames/