Fighting to update the FXTree is not a solution imho. Supporting a
compositing software in an already heavy lifting 3d software is quite
hard. Especially if it wasn't thought off from the ground up. I'd be
more happy with a plugin like what Maxon and Adobe is doing. Code
something that reads a .emdl/.scn file straight into nuke or more likely
an export-to-nuke xml file from softimage. Wouldn't that be more
usefull and require less intense programming ?
Js Guillemette // SHED
3D Artist
www.shedmtl.com
On 4/8/2013 10:31 AM, Paul Griswold wrote:
Wouldn't the solution be to update the FXTree so it can use OFX plugins?
That opens a lot of doors.
-Paul
On Mon, Apr 8, 2013 at 10:27 AM, Luc-Eric Rousseau
<luceri...@gmail.com <mailto:luceri...@gmail.com>> wrote:
> What does the FX Tree lack compared to AE / Nuke ?
It's not a good question to ask. It's like asking, what's the
difference between OneNote and EMACS. People use EMACS for a thousand
different reasons than taking notes, and so do people using AE or
Nuke.
The low hanging fruits that are missing in the fxtree, for its main
intended purpose which it could hopes to fulfill are nodes for the
most common post processing for CG renderers, which includes 2D motion
blur and lens effects, and a quick text node. All of which is actually
in Composite, but we didn't have any the FX R&D at Avid (bafflingly, I
still don't know what the DS fx team worked on). Then again, someone
is always going to need some specific AE plug-in like "frischluft
lenscare" for AE, and dismiss the FxTree for that.
