You don't say whether the region of which you're building the RAM preview is actually using the Twixtor plug-in. I'll assume that you merely have it installed but aren't explicitly using it anywhere in your project. I'll also assume that you have Vegas' own GPU acceleration turned on.

Maybe turning the Twixtor GPU acceleration off also turns Vegas' GPU acceleration off? I could see that happening if both of these were flipping the same flag in the GFX driver to "listen" for render requests. For example.

Rob

Region had the TWX6. I was testing it.

VEGAS GPU is On.

For TWX6 GPU to turn OFF Vegas GPU I'd have had to restart Vegas. So it wasn't that.

Grazie

Region had the TWX6. I was testing it.

Sounds like you are saying that building the RAM preview, of a twixtor affected region is faster when twixtor GPU usage is on versus off. I would expect this to be true since twixtor should hopefully be faster when it uses GPU.

Am I misunderstanding something? I think I am.

Grazie says turning OFF twixtor GPU makes it twice as slow than when turning ON twixtor GPU .
I say turning ON twixtor GPU makes it twice as fast compared to turning OFF twixtor GPU .
And indeed the meaning of this 6.0 version is speeding the twixtor by means of adding the GPU feature ( ON ) in twixtor .

My vegas pro GPU is permanently turned OFF in all my workstations and turning ON the twixtor GPU feature makes twixtor work fast(er).
Did some quick tests in the trial version of twixtor and it looks great .
( have to read the pdf user guide ( installed when installing the plug ) carefully
to maximise the performance of the plug in vegas pro )

Region had the TWX6. I was testing it.

Then I think I'm not understanding what the snag is. It sounds like you're saying that the plugin renders faster using the GPU than it does when it can only use the CPU. To me, this seems like the way it ought to work. Is the issue that you're surprised that it's 100% faster rather than 10%?

Rob

Rob, no "snag" - as such.

I was/am surprised that the Build RAM Preview is made faster with the TX6 GPU engaged. 'cos I was under the impression that Plugs that are GPU enabled COULDN'T make use of their GPU functionality when going to Build RAM Preview, as Build RAM Preview was a control from the CPU. Now in TX6 I have definite PROOF that at least this 3rd Party Plug gets to or is allowed to send its stream INTO the Build RAM Preview function of Vegas. If this IS the case then Re:Vision and SCS have done some Smart Moves!

"Snag" - no . . . Awareness of something newer happening? Yes! - Oh yes, that and the "Green" frames being able to be spoken of indicates that we have a "warning" sign that there is a GPU failure going on.

Again Rob, no snag - just sheer delight!

Grazie

Now I understand. Thanks Grazie.

Your idea of what goes into a RAM Preview is a little different from mine, but since SCS has never published anything like a white paper to describe it we're both groping around inside a black box. The Riddle inside an Enigma.

My impression has long been that RAM Preview (and also cached frames) consists of the frames rendered to the preview window. They are uncompressed frames but limited to the size and quality of the preview window. So, you get what you can see in the preview, which would include the results of any plugin along the way. That's my impression of it, anyway.

From your description, it sounds like the Twixtor plugin really benefits from using the GPU, especially if it really renders twice as fast. That's great, and I'm sure that sort of performance gain is what people would want to see every time the GPU comes into play.

Rob

Oh yes...

G

Now in TX6 I have definite PROOF that at least this 3rd Party Plug gets to or is allowed to send its stream INTO the Build RAM Preview function of Vegas. If this IS the case then Re:Vision and SCS have done some Smart Moves!


Vegas really has no idea what any plug-in does. It gives a frame to the plug-in and gets something possibly modified back. Vegas cannot really stop a plug-in from using GPU, CPU or little gnomes. The plug-in code does what it does. This is no different than playback, and no different than render as.

The video engine renders a sequence of frames, 1-2-3-4, from your source and edits. So what do you do with that those frames.
Shift+B...save the frames in RAM for later playback.
Normal playback...draw them in the preview window(s).
Render as...send the frames to the file encoder.

There is no reason to do anything different for those various possibilities.

Note that Vegas always caches frames it has rendered for playback in the unused preview RAM. This is like Shift+B but on the fly. If you have not used Shift+B, then that is all of preview RAM.

I am sure we all have noticed that when looping a sequence that does not play full fps that after a pass or a few it does play fully. So long as your loop size can fit in the available preview RAM setting size.