This is a really nice idea mark.
I love the idea of reducing CPU demand from brushes by reducing project size.
I also love that it retains any layers that were added in the subcomp.
It's obviously a product evolved from well experienced time with TVP.
I'll need to see how it integrates into my workflow, but I already see how beneficial it is for large poster artwork.

One issue: when capturing, it merges all layers, but creates a duplicate of the layer which was selected before capturing. Maybe you can add a "Layer: Clear" command to the script, and this cleared layer will be used as non-destructive layer on which to apply any artwork.

P.S - I duplicated the "commit, close, save" button, but removed the "save" function. I think this will be the most useful function for me, as I don't necessarily want to save everytime, especially if the project is really large.

lemec wrote:
Unfortunately the script will override the current active custombrush. I have to figure a way around this.

Weren't there a couple of approaches to toggling back the last used tool?
i remember a script or two going around.

Oh, the isolator does toggle back to the last used tool - but the problem is that part of the scripts rely on image-based custom brushes to transfer imagery back and forth. Thus, if you have used cutbrush tools to chop out pieces of image to stamp later on, or if you've got image data saved in your Custom Brush, then that data will get overwritten by the merged image.

This is because I'm using the functions tv_imageToClipboard and tv_brushFromClipboard to grab and stamp merged imagery. I picked this method over having to merge ALL layers within the main canvas, use tv_spareCopy, or tv_layerHold, and then undo the merge. Performing full-canvas layer merges, and then undoing them on a high res image is very burdensome on the system. tv_imageToClipboard let me grab merged imagery without having to actually merge layers.

The best solution, I suppose would be if I had scripting commands to set or unset the 'Display' checkbox for tv_BrushCut. This way I wouldn't have to touch the clipboard at all, and would only have to cut or copy the pixels I needed. I couldn't even find scripting commands to crop the image (using only the current frame). There's a lot of new functionality that had to be kludged in. I'm making lemonade from the situation as best as I can.

I suppose I could add some routines to save off custom brush image data to temporary files in the hard drive prior to capturing data, but it'll cost us in terms of speed.

Too bad TVP doesn't have some sort of built-in function to cordon off a rectangular area within which all image operations are constrained.

malcooning wrote:Is there a way, maybe, to save the custom brush to the Spare before grabbing the new custom brush, and then re-grabbing it once returning to the main comp?

Oh, even more than that! If the custombrush is an animbrush, the whole sequence can be saved to a *.dip (DEEP) format (among others, but this is the most "native" format). The question remains, though, which is more important? Speed and interactivity, or retaining your custombrush? Heh, it's a tough question, like asking someone if they want to lose an arm or a leg!

EDIT: well, I guess you'll never know unless you try... I'll try to work custombrush-saving functionality into it tomorrow.

One suggestions: can the Capture mode for grabbing a portion of the image be a freehand select tool , instead of a square or rectangular box shape , to allow for more precise capture of complex detailed areas ?

One suggestions: can the Capture mode for grabbing a portion of the image be a freehand select tool , instead of a square or rectangular box shape , to allow for more precise capture of complex detailed areas ?

Unfortunately, it would be really tough to do because most of TVP's scriptable image manipulation functions all work on rectangular regions.

Oh, I forgot to mention - you can have multiple Isolators open. Just remember that if you make changes in one Isolator, to use Revert on the other isolator. This is useful if you have several regions you need to work on, or if you want to work on different layers.

I must remember to make the isolated layer mode match the same layer mode as the original source layer...