Thu Jan 21, 2021 1:51 pm
Adding this here as it affects v17 stream as well as v16
viewtopic.php?f=21&t=128126&p=697032#p697032
**Others running v17 stream have identified the same behaviour
Did a quick search and didn't see any thread on this before.
Rendering out a few projects with burn-in for others to review I was hitting about 50-55 fps rendering to 1080p/24.
The exact same clips with the exact same MP4/h265(Nvidia) settings with data burn-in turned off saw render speed jump to 95fps.
Both CPU and GPU utilization were significantly lower when burn-in is enabled and subsequently jump up when burn-in is disabled. It's as if when burn-in is enabled the GPU seems to be ignored or disabled and the entire render action is CPU-based. But even then, the CPU is not fully taxed. Nothing is, really. CPU, GPU, HDD(source or target) as well as system memory are all nowhere near max load.
If this is not a known issue then be aware that your test renders are going to take almost twice as long to spit out but your finals won't.
viewtopic.php?f=21&t=128126&p=697032#p697032
**Others running v17 stream have identified the same behaviour
Did a quick search and didn't see any thread on this before.
Rendering out a few projects with burn-in for others to review I was hitting about 50-55 fps rendering to 1080p/24.
The exact same clips with the exact same MP4/h265(Nvidia) settings with data burn-in turned off saw render speed jump to 95fps.
Both CPU and GPU utilization were significantly lower when burn-in is enabled and subsequently jump up when burn-in is disabled. It's as if when burn-in is enabled the GPU seems to be ignored or disabled and the entire render action is CPU-based. But even then, the CPU is not fully taxed. Nothing is, really. CPU, GPU, HDD(source or target) as well as system memory are all nowhere near max load.
If this is not a known issue then be aware that your test renders are going to take almost twice as long to spit out but your finals won't.