Jump to content

Compile Blocks- need 2nd compile begin

Recommended Posts


In the examples for compile blocks there are 2 'compile begin' SOPs. I also need a 2nd compile begin in order to omit incompatible nodes from being included in the block.

In the attached pic the null node on the left should be a compile begin node.

No matter what I try, am unable to do this without getting an error. "Violation of strict nesting of blocks" (see pic 2)




Edited by art3mis

Share this post

Link to post
Share on other sites

In this case you also need a second begin block in the foreach loop ;) Sesi said they may change this in the future, but for now you need strict encapsulation of loops+compile blocks.

Share this post

Link to post
Share on other sites

No an extra foreach_begin between the compile_begin3 and copypoints2, set to "fetch input" probably ;)

Edit: or to get the complete idea, watch the video in the post below, its a good one I think :)

Edited by acey195

Share this post

Link to post
Share on other sites

What I do find is, if you need more and more compile begin block nodes, the gain of actually compiling the block decreases quickly,
to the point where the overhead is larger than the amount of time you save.
This of course depends on what you do in the loop. the more expensive the loop, the more useful it is to compile of course.
But if your compiled block contains exclusively attributeVops/Wrangles sometimes it is not worth compiling at all.

In your case I am pretty sure it will be worth to compile the loop, but I always like to compare the cook times afterwards using the performance monitor.

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now