- This topic has 11 replies, 7 voices, and was last updated 13 years, 8 months ago by .
-
Posts
-
In Batch within an Action node is there any way to simply kick out layer specific mattes instead of copying Action nodes to isolate that layer or saving keys and reapplying in a new Action layer.? That would be awesome.
u mean turning blend matte on fer a specifc layer and piping it into something else ?
I suspect you are looking to get multiple matte outputs from one action node? Not possible unless like you say you copy the node and choose a different layer to output on the copy.
If you just want one layer or multiples combined together that is possible, but there is only one matte output out of action.
Jeff
yea.. it can be a pain. if there’s a ton of layers in the action setup, i usually end up just rendering out mattes from that one action node, rather than duplicating anything… just make sure you name your matte clips appropriately so if you make changes to that action node, you dont accidently use the old mattes
Yes I am speaking of multiple matte outputs from one Action node. When the compositing within an Action node becomes somewhat complex and you are starting to dealing with multiple layers and finding the need to isolate certain properties of that comp (layer mattes) for lighting, effecting or what have you further down the batch pipeline to copy that action node just to get the isolation you need doesn’t sound like the right formula for comping in Batch. To have to render out individual layer mattes not only becomes time consuming but messy as well. Wouldn’t it be great to have the power to select a layer in Action and be able to kick that layers matte out of the node and continue to work in your pipeline without any further work arounds. I guess it’s on my christmas wish list to Discreet.
heres a question i asked autodesk a few weeks back..[ im on 9.5.14 tezro ]
> re-work batch so that each LAYER with individual matte is available as a
> separate node for operations such as addin sparks/output/export etc etc
> and especially for logic ops on matte layers WITHING THE SAME ACTION SETUPautodesk reply>
Maybe I’m misunderstanding your request…
Version 2007 has significantly improved source nodes which now give you
direct access to all Action blending modes for matte compositing. So you ca
n
perform Min, Max, Multiply, etc… operations between multiple mattes withi
n
the same Action setup. You just need to add your matte surfaces to a Matte
Source, and you can do full blown Action comp on Mattes and re-inject the
result as a Matte layer – without leaving Action.how different is 2007 on linux from 9.5.14 on tezro with the extended feature licence???
I find myself more and more finding ways to do things without action. I like to build all my mattes in batch. I will use the keyer in batch and not inside action. The gmask, mono, 2Dhisto, and edge nodes come in very handy. Think modular keyer, but in the main level of batch. My batch setups are full of Quickcomps puting this layer over that layer. Think over in shake, or merge in Fusion. What this also gives you is the ability to pipe that matte into anything you need to. If you need to reposition the layer then you have to go into action. I also find myslef using multiple action nodes instead of multiple layers in one action node. I hate comping myself into a corner. You end up with a lot more nodes, but it’s well worth it when you can do what you need to without saying if I could only just…….. It also becomes easier to pre-render clips.
One thing I would love to see implemented is a blend matte out of action when using projectors….
Jason Fotter
Visual Effects Artistyea.. it’s rare that i pull keys in action. im in the same boat with you in that i *prefer* to keep everything in that top level of batch and not have to go deep inside modules (mk, normal keyer, action) …that being the said, i do occasionaly end up using the normal keyer to generate mattes, just bc edge+historgram are already there.
my problem is i do always funnel things into one giant action setup… which, as you mentioned, only leads to grumbling and sighs 😉
It is definitely a balance between action convenience and limits. A repo node in batch would help but then you’d surely end up wanting more than x and y and you’re back in action.
I usually start in batch not using action except where I need it. So much depends on how much I know about the result I am trying to achieve. I love Action – it is the heart and soul of the flame but I find more and more of my comping relies on blend modes and using maths in logic ops to combine elements.
Back to the original subject… it would be great in action if you could set multiple matte outputs. Even if it was an artificial limit like 4 extra outputs it would be great. Maybe when you added an action node it automatically added a linked split out node on the matte output to give more real estate for the output tabs.
Jeff
That would be great to have multi matte outputs from action, as well as multi fill outputs, for cc’d backgrounds, foregrounds and all the myriad options that might need to be utilized downstream, as well as archived as isolated f + m elements…
That’s cool to hear how you guys work. However I find working the way you guys said makes the Batch files a NODE cluster fuck and very messy. It’s a much cleaner way to work within Action and makes it easier for someone else to pick up the setup, without them having to try and understand what this bowl of Node spaghetti is. My question however is not to stay within the Action node but kick it out for use down the Batch pipeline. But I guess it’s not possible just yet;) Thanx guys.
“One thing I would love to see implemented is a blend matte out of action when using projectors…. ” brilliant idea…very handy when its a matte per layer.
- You must be logged in to reply to this topic.