Here are a couple of suggestions:

Listening to your system isn't a very reliable way of understanding what's going on. Open up Task Manager, click on the Performance tab and scroll down to your GPU. Even when your CPU is running at 100%, your system may also be using your GPU almost as hard, like this:


I'm sure you know this, but I didn't see it in your description. Unless you have these choices checked at the bottom of the Produce window, PD won't use your GPU at all:


Also, if you have the "latest version" of nVidia's drivers (v416.xx) but you don't have the beta 2224 patch installed, PD can't access your GPU at all! So either install the patch or go back to the 411.70 drivers. There's a whole thread on just this issue!

As for the stuttering you've seen in your produced vids, I'd actually argue that's more likely to be caused by the GPU rather than be solved by using it. You can easily test that by unchecking the "Fast video ..." option and producing again.

YouTube/optodata

DS365 | Win11 Pro | Ryzen 9 3950X | RTX 4070 Ti | 32GB RAM | 10TB SSDs | 5K+4K HDR monitors

Canon Vixia GX10 (4K 60p) | HF G30 (HD 60p) | Yi Action+ 4K | 360Fly 4K 360°

[deleted]

[deleted]

[deleted]

[deleted]

[deleted]

Glad you seem to have gotten things worked out, and thanks for following up!

I have a couple thoughts on some of the things you wrote. One is that there was a misunderstanding where you thought I was asking you to use SVRT. In my graphic, SVRT was actually not selected because I had selected the HW encoder.

If SVRT is available but it's a poor match (meaning you've only got a few sections of unaltered source clips, or sections with a matching frame rate, for example), then as you've seen, PD may produce more slowly because the CPU will be doing all of the encoding for the non-SVRT sections as the GPU is explicitly disabled.

I think it's worth recording with CBR and see if PD will give you smoother produced videos, or maybe better SVRT profiles that might make that the faster producing option.

YouTube/optodata

DS365 | Win11 Pro | Ryzen 9 3950X | RTX 4070 Ti | 32GB RAM | 10TB SSDs | 5K+4K HDR monitors

Canon Vixia GX10 (4K 60p) | HF G30 (HD 60p) | Yi Action+ 4K | 360Fly 4K 360°

[deleted]

Quote Here are a couple of suggestions:

Listening to your system isn't a very reliable way of understanding what's going on. Open up Task Manager, click on the Performance tab and scroll down to your GPU. Even when your CPU is running at 100%, your system may also be using your GPU almost as hard, like this:


I'm sure you know this, but I didn't see it in your description. Unless you have these choices checked at the bottom of the Produce window, PD won't use your GPU at all:


Also, if you have the "latest version" of nVidia's drivers (v416.xx) but you don't have the beta 2224 patch installed, PD can't access your GPU at all! So either install the patch or go back to the 411.70 drivers. There's a whole thread on just this issue!

As for the stuttering you've seen in your produced vids, I'd actually argue that's more likely to be caused by the GPU rather than be solved by using it. You can easily test that by unchecking the "Fast video ..." option and producing again.

I have a GTX1060 and the Hardware Video Encoder option doesn't display under Fast Video Rendering. I Have SVRT and Intel Quick Sync Video as the options. My projects produce fine though. Once the full patch release is pushed out, rather than the Beta, I'll add it and see if PD17 starts to use my 1060. As my projects are only between 5 and 10 minutes long it's not a big deal thogh. Interestingly, when I use the Intel Quick Sync Video option during 'produce', my quality is the same, but my file size is doubled.

Quote I have a GTX1060 and the Hardware Video Encoder option doesn't display under Fast Video Rendering. I Have SVRT and Intel Quick Sync Video as the options. My projects produce fine though. Once the full patch release is pushed out, rather than the Beta, I'll add it and see if PD17 starts to use my 1060. As my projects are only between 5 and 10 minutes long it's not a big deal thogh. Interestingly, when I use the Intel Quick Sync Video option during 'produce', my quality is the same, but my file size is doubled.

TDK1044, from what youv'e writen, you have configured your desktop PC for iGPU usage on whatever Intel chip you have, so no, even with "official" PD17 patch release you will have no change in utilization of your GTX1060 as you are using QuickSync.

Thread here gives you a easy way to identify what GPU PD is using, https://forum.cyberlink.com/forum/posts/list/47907.page#post_box_250514


Jeff

Quote

TDK1044, from what youv'e writen, you have configured your desktop PC for iGPU usage on whatever Intel chip you have, so no, even with "official" PD17 patch release you will have no change in utilization of your GTX1060 as you are using QuickSync.

Thread here gives you a easy way to identify what GPU PD is using, https://forum.cyberlink.com/forum/posts/list/47907.page#post_box_250514


Jeff

Interesting. I didn’t configure it at all. My video games use the 1060. Not an issue for me though as my projects are all under ten minutes in duration. 😊

Quote
Thread here gives you a easy way to identify what GPU PD is using, https://forum.cyberlink.com/forum/posts/list/47907.page#post_box_250514
Jeff

I hadn't realized that the logos were "active" and tied to the machine hardware. Thanks for that excellent info!

YouTube/optodata

DS365 | Win11 Pro | Ryzen 9 3950X | RTX 4070 Ti | 32GB RAM | 10TB SSDs | 5K+4K HDR monitors

Canon Vixia GX10 (4K 60p) | HF G30 (HD 60p) | Yi Action+ 4K | 360Fly 4K 360°

Quote My video games use the 1060.

That's because games use a different part of your GPU chip (3D cores). Video decoding and encoding use a different, dedicated ASIC, embedded on the same chip.
That's why the "switcher" app doesn't recognize the video processing as 3D, to switch to the nVidia GPU.

lol. Gotta love cyberlink. So in PD16, people said don't sue AMD, it's broken for AMD, etc etc, but that it works great with someone's gtx 1060. So I then sell the unopened amd card and get a 1060, so now it doesn't work for the 1060. I'm probably going to just get a different program, as luckily I ahevn't bought any software yet. Nobody wants to spend on a gpu and then their programs not utilize them much, if any.

Quote lol. Gotta love cyberlink. So in PD16, people said don't sue AMD, it's broken for AMD, etc etc, but that it works great with someone's gtx 1060. So I then sell the unopened amd card and get a 1060, so now it doesn't work for the 1060. I'm probably going to just get a different program, as luckily I ahevn't bought any software yet. Nobody wants to spend on a gpu and then their programs not utilize them much, if any.

Just to be clear - there are no major issues with PD accessing and using a GTX 1060. There were two posters who were having problems in this thread. OP has resolved his issues and can utilize his 1060; TDK1044's dual GPU system is configured to use the iGPU instead.

Nothing should prevent you from installing PD17 and producing away. You just need to install the PD17 beta patch if you want to use the latest v4416.xx driver from nVidia, or use the v411.70 drivers until the full patch is released.

YouTube/optodata

DS365 | Win11 Pro | Ryzen 9 3950X | RTX 4070 Ti | 32GB RAM | 10TB SSDs | 5K+4K HDR monitors

Canon Vixia GX10 (4K 60p) | HF G30 (HD 60p) | Yi Action+ 4K | 360Fly 4K 360°

Quote

Just to be clear - there are no major issues with PD accessing and using a GTX 1060. There were two posters who were having problems in this thread. OP has resolved his issues and can utilize his 1060; TDK1044's dual GPU system is configured to use the iGPU instead.

Nothing should prevent you from installing PD17 and producing away. You just need to install the PD17 beta patch if you want to use the latest v4416.xx driver from nVidia, or use the v411.70 drivers until the full patch is released.

I agree completely. I'm not a techie at all. When it comes to computers, I'm Oddball from Kelly's Heroes......."I only ride 'em, I don't know what makes 'em work." My iGPU renders perfectly and quickly. That's all I need. I really like PD17.

ok, well that's good, if people are indeed generally able to get it to work fine. It seemed ot me like he still didn't sort it all out. And then I believe someone else said the quality has not been as good when using hardware encoding (unless I am mixing that up with some other topic elsewehre).

I originally was going to get an intel cpu and just use the igpu or a 1050 ti. But then i read over and over that you should have a fairly good gpu. So at this point I have an unopened 1060, but paid for a 1070 on a good amazon deal. I'm mostly trying to decide whether to keep the 1060 or 1070, so either way I need programs that utilize nvidia cards well.

I don't game on a pc, really, so I would normally think the 1060 is enough, but just "in case" I ever do, I thought I may be best with the 1070. i also read that the 1060 crashes in a popular video editing program for 8k footage, whereas everything above the 1060 does not. (not that I am going to use 8k footage in a program, but you never know what will be common a few years from now...)

I will defer to anything Jeff (JL_JL) has to say on the matter of PD and GPUs, but this chart shows that the 1070 has 2 hardware video encoders (NVENC), compared to a single one for the 1060.

Assuming PD can utilize both at the same time, you would see much faster producing times with the 1070.

YouTube/optodata

DS365 | Win11 Pro | Ryzen 9 3950X | RTX 4070 Ti | 32GB RAM | 10TB SSDs | 5K+4K HDR monitors

Canon Vixia GX10 (4K 60p) | HF G30 (HD 60p) | Yi Action+ 4K | 360Fly 4K 360°

Quote Assuming PD can utilize both at the same time, you would see much faster producing times with the 1070.

I doubt it. I think that's useful only for cases when two different streams of encoding are happening (because that's the max number allowed for a GTX card anyway).