samples

[owmo-dev]

Modify the "frame" option to be "frames" so that it has a start and end frame. If the two frames are the same, then it's a one-shot, otherwise it'll cycle over multiple frames. Why?

• Render sequences (ex: use execute to draw to canvas, then finish to download PNG for frame)
• Progressive rendering (ex: every frame renders one sample, use frames as a proxy for samples)

May need to make entityManager run everything async to allow for long await functions.

[owmo-dev]

I want to reject the idea of a start and end frame, that is more appropriate for the Orchestrator (already implemented). What is valuable in the Engine is the idea of handling a progressive render loop, where the configuration supplies a number cycles it should loop before considering a frame completed.

• Samples in this case could be considered "iterations" or "cycles" in the engine (more generic)
• Ideal to have an interruption function, which ends the cycles at whichever loop it's at (user bindable to a key)
• Nodes in a Pipeline could be connected such that they require N cycles together, so that you could repeat a draw-->style-->view loop in a progressive render, then once completed do a final processing step or whatever

Nodes would ideally be chained together, rather than individually looped (perhaps both is useful? configurable?). Either way, a change in the condition of completion would be necessitated. Pipelines would keep track of the cycles.

[owmo-dev]

To add to this - I attempted to add logging into my artwork (to show progress of rendering) but because the entire thing is happening within a single requestAnimationFrame the console log doesn't get rendered to the browser until next frame. I need to have some way of managing buckets & samples across individual frame calls, rather than handling that loop in the artwork itself. The change will introduce a breaking change for existing artworks, which will need to be version locked.