Loop: Bailout / Stop input

If I have the loop set up with 1000 iterations, but the result may already be available after 2 iterations - how do I get out?

I may fail to see the obvious solution - but it seems we need a way to "get out" of the loop before it reaches the maximum number of iterations.

I propose a special input called "Bailout" that if non zero will stop at the current iteration.

(btw. the need for that functionality was mentioned during the V4 beta rounds)

Not exactly the same thing, for it still would run through all the loops, but using the OR component to produce a different input (fully transparent, for instance) for the loop instead of the complex (whatever you are building) once a certain condition has been met might help in speeding up rendering...? Just a theory.

An exit option would obviously be better.

Ok, how about another inefficient idea then: A Script component that either passes the source image through or, after a condition has been met, outputs a transparent black for every pixel regardless of source input?

Perhaps this could be made as a slave "Stop Condition" node that works somewhat like the If components (but with grayscale map inputs instead).

The "Stop Condition" slave node would have two inputs, A and B and an operator selector like the If.

You can then force the iteration to stop before it reaches the maximum iterations e.g. when A == B

Bump, mappable loop iteration count / break would be great!

It definitely would be nice to escape a loop at a user determinable point. Seems basic.

I would even ask for more : a way to stop the rendering process, by a keyboard shortcut or maybe a component, that you can include into your filter.
I often see results on my screen while still rendering, that look far better than the final result. I do not know if the screen build up kind of parallels the actual rendering in memory, but if that is the case, I'd like to stop the rendering as soon as I like the result I see on the screen. I have the same experience in Topaz Simplify, where the 'crude' result on my screen often looks far more interesting, than the final, precisely rendered result.

Beat

Nice pun

Sorry, I felt it touched upon the subject, stopping a process. But no problem if you think it's too general or too far removed from the topic. I will post it in a separate thread.