mberetta
Member
What about adding the ability to use a node based non destructive user interface to manage the “developing” process?
Every time I used software with node UI I found useful and productive because it allows me to toggle a node, move a branch before or after a process and having a clear overview to the workflow.
I used this kind of interface for the first time with Nothing Real’s Shake twenty years ago and I remember that even though it was designed for video compositing, I often used it for colour correction on photographs because the interface was more powerful than Photoshop correction layers (I don’t remember it there was already non destructive correction layers or not in 2002).
Other software I use where I find useful node interfaces are Origami Studio
DaVinci Resolve Fusion
And procedural nodes in Blender
The most of the nodes could be processes with one input and one output but there could be some nodes like PixelMath, ChannelCombination with multiple inputs.
Editing a node at the top of the flow could be heavy to calculate, but there could be an alert before editing the “non last” node. A caching system could help to improve the performances If a node is temporarily disabled or modified and then returned to its previous state.
Every time I used software with node UI I found useful and productive because it allows me to toggle a node, move a branch before or after a process and having a clear overview to the workflow.
I used this kind of interface for the first time with Nothing Real’s Shake twenty years ago and I remember that even though it was designed for video compositing, I often used it for colour correction on photographs because the interface was more powerful than Photoshop correction layers (I don’t remember it there was already non destructive correction layers or not in 2002).
Other software I use where I find useful node interfaces are Origami Studio
DaVinci Resolve Fusion
And procedural nodes in Blender
The most of the nodes could be processes with one input and one output but there could be some nodes like PixelMath, ChannelCombination with multiple inputs.
Editing a node at the top of the flow could be heavy to calculate, but there could be an alert before editing the “non last” node. A caching system could help to improve the performances If a node is temporarily disabled or modified and then returned to its previous state.