Well, some of those features do exist if not obvious:
- If you select your operator from the FX Operator selector, middle click
each node you want to act as input to the selected operator, then middle
click into the empty workspace to insert the selected operator, the picked
inputs will be automatically connected to the new node upon insertion. For
example, get two file input nodes, then choose the "over" node from the FX
operator selector. Middle click each file input node in turn, then middle
click in the empty workspace to insert the "Over" node. The file input
nodes will be automatically connected as inputs to the "over" node.
- could possibly implement a 'paste at cursor' function with a self
installing plugin. Getting mouse cursor screen coordinates is trivial, but
not sure if FX tree exposes coordinates to make a conversion from screen
space to FX Tree space.
- not familiar with the copy/paste bug you speak of.
- Can't help with the optimization requests other than to say to
deactivate/mute a node if it's a problem so the computation doesn't trickle
downstream. If caching is active, then this should behave the same as you
request (sort of). There is a proxy mode you can take advantage of to
minimize the hit of a larger tree. Also consider using multiple trees
instead of one big kahuna containing multiple node graphs, that would give
you the ability to selectively turn on/off the trees in use so the FX Tree
only computes what it needs to compute.
In your wishful thinking list:
- not sure what you mean of better handling of 32 bit depth. Do you mean a
32 bit RGBA image (8,8,8,8) or 32 bit per channel image (32,32,32,32)? And
what needs improving?
- live 3D nodes exist as any image clip can be accessed in the FX Tree from
the clips menu. The image clip will have an input and output node. Just
insert your desired nodes in between and the results will be visualized in
the 3D viewports and renders. This includes paint capabilities.
- I think I exposed a few hidden features ;-)
Message: 1
Date: Fri, 19 Dec 2014 09:03:52 -0500
From: Jason S <[email protected]>
Subject: Re: Lets Hope Autodesk Buys the Foundry!
To: [email protected]
Realistic (but unlikely)
Move node or drag connection pans window
way to Insert node after current while keeping connections (1 click even if
10 connections)
copy paste at cursor location
Fixing Ctrl-c ctrl-v intermittent fail (workaround: right-click /tap "C"...
right-click /tap "P")
Make it not update if nothing has changed, (for optimisation of tree bits
that process still images, & 3D playback with texture processing)
Wishful thinking (highly unlikely)
-Better handling of 32bit depth
- Some ice-ification.. drag drop nodes, tab search input box, drop node on
pipe to insert
-"live" 3D nodes like little scene nodes refferring to some groups, layers
or passes (rendered on the fly with renderer of choice or HQ-OpenGL)
that can be part of tree and that you can pipe textures or footage in.
-Better exposed hidden features that you have to know about to know that
they're there
Otherwise it's really good, very swift and very memory efficient (can handle
loads of nodes in super big rez at 1 to 5 sec per frame renders)
-has tons of features no one knows about
- And your (intuitive/versatile) 3D environment can be your final comp.
