> 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.
