Okie dokie benchmark numbers galore, looking at CPU vs. GPU and also power draw, sound levels, audio waveform indexing speeds, etc:
@TheRhino, I'm looking forward to seeing Multi-Gig network hardware coming down in cost, being able to run 10gb in my home office and 2.5gb throughout the house using the CAT5 in the walls would be very nice but seems the market isn't quite there yet.
@eikira, Very interesting, will check it out, I totally do get NVENC artifact problems occasionally, even with the standardly addressable quality settings cranked up.
My 10G network cost <$350 to connect (3) Workstations and a QNap NAS.
$135 MikroTik 5-Port Desktop Switch: https://www.amazon.com/gp/product/B07HYKQFWD
A while back I posted my setup: https://www.vegascreativesoftware.info/us/forum/affordable-10g-network-for-small-studios--115799/
@eikira, Very interesting, will check it out, I totally do get NVENC artifact problems occasionally, even with the standardly addressable quality settings cranked up.
i found out if i remain the same GOP or at least the keyframe interval blocking and artifacts are more or less gone (of course if i chose a reasonable bitrate)
If we're talking just the encoding part, I.E. Mainconcept vs. NVENC, the latter still delivers roughly 2x the throughput. This is with NVENC cranked up to full HQ settings (Profile = High, Preset = High quality, RC Mode = VBR - high quality, bit rate 40Mb avg/50Mb max), because without doing that I get noticeable visual artifacts which the MC encoder never has.
On the Video Processing end of the rendering pipeline, I do not enable GPU support, because my relatively flat projects don't benefit much from it and so I can render multiple videos at the same time. Does enabling GPU support for video processing impact the MC vs. NV question above? I doubt it but haven't definitively tested it, will try and report back...
i cant praise voukoder enough. you can tweak NVENC on a broad range in voukoder to eleminate artifacts etc. (setting specific GOP and so on). and it utilizes the gpu much stronger as the vegas internal GPU profiles.
have you checked it out? www.voukoder.org, its just a time saver and still retaining the picture quality. i would not want to miss this anymore.
any suggestion for settings in voukoder for nvidia HEVC? to keep quality best with smallest file size/LONGEST render time as it renders so quick anyway....thank you
Okie dokie benchmark numbers galore, looking at CPU vs. GPU and also power draw, sound levels, audio waveform indexing speeds, etc:
@CarlM Around 8:45 on your video you mentioned that you cannot run (2) instances of Vegas if your have GPU acceleration turned-on. On all of my Intel systems I can run 2-3 render instances and get faster results vs. batch-rendering one at a time. I do it all the time so my clients can receive a 4K intermediate, 4K HEVC, 1080p MP4, etc. rendered from the original source files. Others with AMD systems appear to be able to run more than one instances, so maybe we can hear from them...
On my 9900K / VEGA 64 workstation, (1) 2 hour 4K project takes about 2 hours to render to the same intermediate. If I open another instance of Vegas & render it to 4K HEVC, both finish in about 2.5-3.0 hours. If I open a 3rd instance & render to 1080p MP4, all (3) renders finish in 3-4 hours - depending on the complexity of the project. With (3) renders going, my CPU is maxed-out, but more importantly, so is my RAM & my GPU usage is above 50%...
For small projects I will just render all (3) output files the client requested while I eat lunch, etc. For larger projects, I just copy the final VEG to another workstation where I already have a copy of the source files (which is good for redundancy/backup reasons too...) This 2nd system is also tied-up while it copies the final renders to a USB 3.0 external drive provided by the client. I'd rather not attach client-provided drives to my main rig even though I always format them before dropping files to them...
By having (2) fast workstations vs. one pricey high-end / server-class system I feel I get more done in the same time. Again, this is mainly due to the fact that Vegas only utilizes the resources of (1) external GPU plus the internal Intel iGPU / QSV...
