Although it's hardware encoding, it still requires cpu. If you don't have enough cpu you constrain the hardware encoder. Having said that Vegas Pro is not is not as good as other software when utalising hardware encoding. This shows the difference in GPU use between Davinci Resolve and VegasPro with a simple transcode
Vegas Pro
Resolve
Also you can see that Resolve uses a massive amount of CUDA GPU processing, whereas Vegas uses CPU instead
Don't know exactly what you mean, but at my laptop from signature I render a 1 minute project in VPro 15 of FHD 50p AVCHD files to a Magix AVC Nvenc FHD 65 fps in 59 sec. Look
"Where" does it show 65 fps? Do you say that is the encoding speed? The video frame Rate? The preview speed? The project frame rate? A screenshot would certainly help in the absence of a considered description.
Start here before requesting help. Section C is required for support:
@Musicvid - Yes. Also, @Kaito22, there isn’t any SONY VEGAS, and not since 2016 when the German software company bought the whole range from SONY. Where do you get 65 FPS from? Odd?
my vegas shows fps when encoding but don't see it in your picture. you are converting frame rates, harder on computer and nvenc
I'm very curious where you see the velocity of encoding in Vegas. Can you give a screenshot. I see only from frame 0 till the last frame of the project where the encoder during encoding is and thats on my screenshot o because the encoding is ready and than the cursor jumps back to that frame. The counting in red below the frames depends only of the preview setting that is being used and has nothing to do with the encoding itself.
i LOAD 1080p 30fps video and i nvenc at 1080p30fps no filters it is h264 in and out. it is not standard yes to do only but filters confuse matter of situation. picture of here 65fps standard
OK now I get it. I never use that extension of SEMW. To me it looks very fast, that is 2,23 x realtime. Without that GPU help (so only MainConcept codec with CPU) it goes 18-19fps= 0,62 x realtime.
So, without providing any source properties, or an original sample for anyone to test, or any machine specs, you are asking if 65 fps as reported by a third-party extension is good enough?
Well, I say you are doing just fine indeed. Certainly you are responding on par with the bulk of new users here. I can gather from your choice to use hardware h264, that you are interested primarily in encoder speed, and less on quality.
In order to expect continuing support here, refer to the link already provided.