It's a little unclear what you're doing.

@michael-harrison - Apologies.

Are you using the remove capabilities in Silhouette paint

@michael-harrison - No.

or are you using some other BCC plugin?

@michael-harrison - As I said, I'm using BORIS MOCHA Pro.

If the core problem you're having is preview becomes sluggish or unusable after doing a lot of work in BCC/Mocha, I can confirm.

@michael-harrison - Only on that Event that I worked on. Once out of MOCHA Pro there is this Control Array:

As the heavy lifting has already been done, what on Earth is the issue with the then VP handling an obvious Control Array within this OFX Control to produce adequate FPS? @michael-harrison Do you attempt to use this Control/s? Well, you obviously have to.

Depending on what I'm doing I preview in the Boris tool as much as I can and ignore the sluggish preview in VP.

@michael-harrison - Really? You put up with this? Well, I find this unacceptable.

I'll periodically do a targeted render to make sure I'll get the right results out of VP. It's not markedly different in AE though AE speeds up after the first playback due to the caching that it does.

@michael-harrison - And again, the hard work has already been done - why is Vegas Pro making such a struggle or meal out of this?

I think the pipeline in VP just isn't well optimized.

@michael-harrison - You think?!? And again, unacceptable.

Not sure if Magix or Boris needs to do the brunt of the work.

@michael-harrison - And here we lay, spent the dosh and nobody to pick up the Baton.

@michael-harrison - Thank you very much for reacting to my Post. I just wish I could get VegasCreativeSoftware to work with BORIS over this.

@Grazie "Really? You put up with this? Well, I find this unacceptable."

What's the alternative? I could learn a new NLE (and am slowly doing so) but I have enough work now that requires me to use the tools I already know that dropping VP wouldn't be reasonable. I am using AE for some of my workflow as it's notably faster in areas, but for cutting and layout, VP is my go-to tool.

Working around obstacles is a tried and true way of getting the work done.

If you have access to another tool such as AE, try doing your mocha work there and then import the finished clip into VP for the rest of your editing. For example, I had some recent work that had me using Flicker Fixer, Pixel Fixer, Unsharp, and multiple lens burs with mocha masks on the same clip. If I'd tried to do all that in VP I'd have shot myself. AE though worked quite a lot faster and working with the resulting clip in VP had me previewing at full speed.

"You think?!? And again, unacceptable."

And the alternative is? If you want to convince them to give me access to the source (2D&3D graphics programming was my life's blood for two decades) I'll see what I can do. I'm only kidding a little.

My understanding is that Vegas has a small team and they've got to pick and choose carefully what they work on. Regardless, they also have to satisfy the demands of their parent and it's clear to me that Magix is busy fragmenting their product lines and don't really know how they can succeed in the future.

@Grazie

The Render Module of the Mocha Pro Plug-in is slow on all the editing platforms I use, not just in Vegas. It is also slow in Premiere and After Effects.

This is because the editing platforms do not yet use the internal cache of the Mocha Pro Plugin to view the Tracked Layers + the selected Composition Module. This makes the editing platform need to Render the preview and this uses a lot of memory and processor, making the preview very slow.

But, If you do a new tracking in the selected Composition Module (in your case, the Remove Module), you can do a much faster rendering directly from the Mocha Pro Plugin.  

After that you can import the rendered video into Vegas and work with smooth playback.

See how I do it when I use the Insert Module. I believe that the Remove Module follows the same principle.

@joelsonforte.br - Thanks for your input on this, you’ve made the points I wished to explore and I shall respond, when I’ve calmed down 😉.

@Grazie

The Render Module of the Mocha Pro Plug-in is slow on all the editing platforms I use, not just in Vegas. It is also slow in Premiere and After Effects.

@joelsonforte.br - Oh is it? This is once back in VP and outside of the MOCHA Workspace - yes? The actual MP Workspace Remove happens truly rapidly, no complaints.

This is because the editing platforms do not yet use the internal cache of the Mocha Pro Plugin to view the Tracked Layers + the selected Composition Module. This makes the editing platform need to Render the preview and this uses a lot of memory and processor, making the preview very slow.

@joelsonforte.br - Then why sell a product as a Plugin that can't be Previewed back in the Host- here that's VP? Which company is waiting on who/whom? Magix on Boris or Boris on Magix?

But, If you do a new tracking in the selected Composition Module (in your case, the Remove Module), you can do a much faster rendering directly from the Mocha Pro Plugin.

@joelsonforte.br - OK, a few years back I'm starting to remember your advice on this. I'm confusing the work flow. Please show me the work flow you are suggesting.

After that you can import the rendered video into Vegas and work with smooth playback.

See how I do it when I use the Insert Module. I believe that the Remove Module follows the same principle.

@joelsonforte.br - Now I'm confusing myself?