Ok, we have restored it, since some users want to use it for reference purposes:

https://forum.cyberlink.com/forum/posts/list/77602.page

Cheers
PowerDirector Moderator

For customer support related issues, please contact:
- Customer service: https://membership.cyberlink.com/support/customer-services.do
- Technical support: https://membership.cyberlink.com/support/service/technical-support.do

Quote Ok, we have restored it, since some users want to use it for reference purposes:

https://forum.cyberlink.com/forum/posts/list/77602.page

Cheers
PowerDirector Moderator

Thanks, appreciate it. No real reason to hide was there, no forum violations in the post that I could see. I wanted my beta review comments concerning NVENC SDK updates which expose the new encoder improvements and features of Turing since a developer prerelease by Nvidia occurred a few days back. Eagerly await a PD beta patch to evaluate which natively supports Turing vs current state.

Jeff

I just updated my long-time i7-4770k + GTX 780 Ti system to an i9-9900K and RTX 2070.

In my first test, a 5 min HD 60p project that took 15 minutes to produce to H.264 with my old system took just 2:59 with the new one. Without the Turing chip, Intel's HD 630 QuickSync took 3:31 min.

The 8 core/16 thread CPU and embedded iGPU are almost 5x faster at producing than my old system, and they deliver 86% of the 2070 speed without any additional cost. I paid $500 more for the nVidia card, which I now see as a really steep price to pay for just a 14% improvement.

If PD isn't optimized for Turing yet, then it would be really nice to know that an improvement over this benchmark is possible.

I'm certainly not complaining about any of this amazing speed, but it's going to take a loonnnggg time to recoup the 2070's additional cost if I'm only shaving around 14% off my producing time.

If the developers can give PD access to the native Turing instructions and wring out even more performance, well I'm all for it!

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 I just updated my long-time i7-4770k + GTX 780 Ti system to an i9-9900K and RTX 2070.

In my first test, a 5 min HD 60p project that took 15 minutes to produce to H.264 with my old system took just 2:59 with the new one. Without the Turing chip, Intel's HD 630 QuickSync took 3:31 min.

The 8 core/16 thread CPU and embedded iGPU are almost 5x faster at producing than my old system, and they deliver 86% of the 2070 speed without any additional cost. I paid $500 more for the nVidia card, which I now see as a really steep price to pay for just a 14% improvement.

If PD isn't optimized for Turing yet, then it would be really nice to know that an improvement over this benchmark is possible.

I'm certainly not complaining about any of this amazing speed, but it's going to take a loonnnggg time to recoup the 2070's additional cost if I'm only shaving around 14% off my producing time.

If the developers can give PD access to the native Turing instructions and wring out even more performance, well I'm all for it!

For such a system, the Nvidia NVENC benefit would be most prevalent in H.265, not H.264, where it's probably 2.0-2.5x faster encode than the i9-9900k CPU encode. Value depends on needs.

Turing provides some other benefits vs speed, yet to see what CL exposes in PD.

Jeff

Quote For such a system, the Nvidia NVENC benefit would be most prevalent in H.265, not H.264, where it's probably 2.0-2.5x faster encode than the i9-9900k CPU encode. Value depends on needs.

Turing provides some other benefits vs speed, yet to see what CL exposes in PD.

Jeff

Your H.265 numbers were on the money during my first test of this same project (~10 min for the 630 and 3:31 for the 2070). However, that was with an Intel driver from August. Windows Update didn't have anything newer, but I download the current 6444 driver and that radically improved the QC performance.

In fact, it more than doubled it! The produce time was only 4:55, which means the Turing "only" outperforms QS by 40% - no longer anywhere near 2x. If the "true" H.265 performance is only going to occur with a native-mode driver, then that's going to be really, really fast.

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
Thanks, appreciate it. No real reason to hide was there, no forum violations in the post that I could see. I wanted my beta review comments concerning NVENC SDK updates which expose the new encoder improvements and features of Turing since a developer prerelease by Nvidia occurred a few days back. Eagerly await a PD beta patch to evaluate which natively supports Turing vs current state.

Jeff

I wonder if CL will ever release a PD17 patch that will take advantage of Turing native capability. All pieces have been in place for some time, nice Nvidia/OBS release here, https://www.nvidia.com/en-us/geforce/news/geforce-rtx-streaming/

Other free and paid editing products are now compatible too.

Jeff