Build 187 version 21
Tried NVidia and Intel CPUs, various processors, various computers.
Tried with and without GPU acceleration (on both Intel and NVidia)
The INSTANT that I turn on any kind of luma or chroma key, I get single digit render speeds at any resolution using Magix AVC or HEVC.
I'm baffled. There is seemingly nothing other than "it's vegas" that makes this go slow.
If I set up the same chroma in Premiere or Resolv on the same hardware, the render flies.
What about using color corrector secondary to create the mask, is that any faster?
I don't see what is baffling- not all Fx are easy to process, and compositing multiple tracks is much more computationally intensive. Of course you'd keep GPU acceleration in in preferences/ video and if the Fx are CPU-limited you'd be better off with GPU encoding so the CPU isn't burdened with that, too.
For me it's all Project size dependant, (There's multiple chromakeys on the green screens + Charcoal to create the edge effect (Glow from Track motion), & at the bottom there's an assortment of AVC, HEVC & MOV/ProRes, I see no slow down when rendering through the different formats.)
HD 1920 x 1080 renders quite fast & steady
UHD 3840 x 2160 slows down by about ½ but is still steady & acceptably fast enough.
No, none of the above appear to apply. I'm using 21 with the brand new build 187.
It runs "normally" for about 10 seconds, then drops to a crawl, like it's run out of memory or exhausted a disk buffer.
This happens independent of PC, graphics card, or any settings you can think of (HEVC, GPU, etc).
It's just broken, and I cannot figure out what is wrong.
The instant I render without chroma, speeds are normal.
All it takes is literally a single element with chroma added -- only one track. And renders are single digit speed.
And like I said above, the same exact process (single track, single chroma) in Resolv or Premiere runs without issue.
As a followup, might have found a solution by setting up my chromakey in 1 project, then loading that project directly into another project (so it in effect frameserves). That renders without delay or slowdown.
So the issue isn't the chroma itself, but the processing that happens while rendering.
And yes, I've tried multiple different rendering formats. Same result.
This is not, it goes without saying, the way it's supposed to work, nor is it the way it's worked in the past.
I don't really see much of a difference, and no great change with CPU or GPU use, is your GPU or CPU maxing out with chromakey?