Mailing List
Home
Forum Home
Softimage
Carrara
trueSpace
Dir3d-l
Maya - a powerful 3D animation and visual effects software
Macromedia Flash Development
Subjects
Cameras
scaleDown command
black out solved
Aircraft Tutorial
Mathematical XYZ ?
Its done This vs That
Its done first week
recommendations for screen video captures?
3DExplorer "Oddity "
New Director
ProTeam renewals
Fuel 's new websites (X post)
Blue peter create a make toy
targeting groups question
XPost: Shockwave 3D game ( sort of )
RES: RES: RES: Fish Modeling
Emitting particles from object intersection
Fuel 's new websites (X post)
Texturing
Big Break Contest Videos
New Plugins
Models and Texture on my updated site
Error Installing Patch tS6 6
Plasma?
Looking for Inspiration
Weird EMail Q
It 's done first week ?
Cherry not cranberry
New game
Camera Animation Problem
Particle plugins?
 
Film mask Plugin in FXTree...

Film mask Plugin in FXTree...

2004-06-28       - By Dan Yargici

 Back
Reply:     <<     11     12     13  

> hook your fileinput into eg. a colorcorrection, that you disable on rgb and
> a in masking, so it does nothing.
> that way you can build your complex tree underneath it and easily replace
> your input.

Yes, of course, but that requires you to do it every time in every comp just in
case you later want
to change this.  That is exactly why I'd like this feature, so you don't have
to.

This is not just about replacing sources (I agree that it could be improved,
but it's still not
*that* hard), but a way that would easily allow you to add nodes to the top of
the tree without
having to reconnect every little input afterwards.

DAN

-- -- Original Message -- --
From: "peterb" <peter_b@(protected)>
To: <XSI@(protected)>
Sent: Monday, June 28, 2004 12:38 PM
Subject: Re: Film mask Plugin in FXTree...


>
> > For me, I can do it in any order at all and it still crops very top-heavy
> as if it's expecting an
> > NTSC frame......
> >
> > I really have tried every order...  :-/
> >
> > Also, I had an idea for a tiny workflow feature... Sometimes you have a
> huge tree with one clip at
> > the top feeding many inputs accross this tree.  Now suppose you want to
> dissolve that top clip with
> > another and pump the result into all those same inputs, you have to zoom
> right out until everything
> > is teeny-tiny, making hooking up nodes impossible...
> >
>
> If I understand you correctly,
>
> hook your fileinput into eg. a colorcorrection, that you disable on rgb and
> a in masking, so it does nothing.
> that way you can build your complex tree underneath it and easily replace
> your input.
>
> This said, I still would favor an easy way to replace an input node with
> another one.
> (as in "replace source" functionality that can be found in many
> editing/compositing applications)
> You can often have not one but several inputs (your passes for instance)
> that go into your composite in very different ways.
> If you have to replace them all for another take it can be complex
> sometimes...
>
> ---
> Unsubscribe? Mail Majordomo@(protected) with the following text in body:
> unsubscribe xsi
>

---
Unsubscribe? Mail Majordomo@(protected) with the following text in body:
unsubscribe xsi