Thank you. So my (USD 4000) system is not enough for video editing...Vegas: congratulations.
 

PS: while my system LAGGING (on preview) then my Ryzen processor 16 threads usage ist UNDER 40%, memory UNDER 20%, GTX1080TI processor UNDER 35% - memory UNDER 20%. So Vegas what resources use? Like a Commodore 64....

You think I insult your system, when it is really your source? And maybe settings?

I bow in envy to your wonderful system!

Proxy. It's in the FAQ. Along with other good things that will help you.

Edit
OP is not looking for help but only want to expire his frustrations with sniping at a good program.

....while my system LAGGING (on preview) then my computer usage ist lower than 30%. What did I buy 70%?

someone buys a Ferrari that can only go over 100 miles if four people push it and it is on a slope.

I am sad that I have spent so much on the system and not thank him.


.....vegasaur users manual say:

..." For example, you can use proxies when you edit a project on a laptop or on a computer with limited processing power.". So my computer with ROg VII/Ryzen 2700x and GTX1080TI is a limited processing power .... Whoaaaa

nvm my deleted post. Good luck.

What did I buy 70%?

The unseen, hidden dark power.

Your system load consists of way much more things than CPU/GPU load.

On your screencap I see 10 videotracks and the scrollbar makes me suspect at least 5 additional.

Did you check other graphs too? Like disk utilization, Compute#, Copy# and other graphs on GPU?

Not just pure general usage percent which windows calculates as an average of other graphs.

I would try to create proxies, with which Vegas can work way much more efficient. For editing when you prefer framarate, use the preview quality. Above that (good, best) only if you want to finetune something in small detail. Because: if you have proxies, Vegas uses them instead of the original video automatically, if the preview is just "preview". Otherwise Vegas uses the original video streams.

And a question: how fast can you drive with a Ferrari through the desert, like Paris - Dakar rally? Where there's no highway...

Please try to create those proxies!

klt: Thank you...

So if i create proxies, then also lagging...

I use BCC Boris Effects...If disable, then no lag...

So FX lag: without FX: no lag.

 

klt: Thank you...

 

So if i create proxies, then also lagging...

I use BCC Boris Effects...If disable, then no lag...

So FX lag: without FX: no lag.

You should have said from the beginning that you are using 3rd party plugins. BCC is especially resource hungry... please complain to BCC.

Because vegas pro internal fx-s poor. Like chroma key...
Ok, i complain to BCC.:)

Because vegas pro internal fx-s poor. Like chroma key...
Ok, i complain to BCC.:)

Have you tried the Secondary Color Corrector for Chroma Keying? You may get better results with it. Also, are you working in 8bit or 32bit Full?

Thank you for reply.
im not try secondary color corrector... is it good?

Im working 8 bit. What different are 32 bit?

Thank you for reply.
im not try secondary color corrector... is it good?

 

Im working 8 bit. What different are 32 bit?

The SCC can give you better results depending on your source footage. 32bit is required for 10bit source footage; if you don’t have that stick with 8bit.

If install secondary GTX1080TI (via SLI) in my motherboard, then preview lag decrease? Or i will wait for vegas 17, maybe they'll fix that "old" preview "engine"? Thank you!

Vegas does not support SLI nor CrossFire. Also, I just noticed that your footage is 422, you stated 1920x1080 ProRes 422 mov. Depending on how these files were created, from a camera or otherwise, I would transcode it to SONY XAVC-I using Sony's free Catalyst Browse software as that will play a lot better in Vegas.

Thank you OldSmoke!

I now download the software...

can you recommend a "good setting" in XAVC-I?
Many thanks!

Catalyst Browse has predefined templates and I usually use the Sony XAVC-I with the correct pixel dimensions. Make sure you don't add color correction during the render process; I suggest to play around with it with small/short clips.