Quote
We shouldn't have to go through all this and I complained about this issue several years ago so Cyberlink should be aware. They need to fix their software. This can also be an issue on desktops, but most desktop mobos have a way to only use the dGPU. No clue why most laptops can't.
Hi guys,
Just a small comment now as I am quite busy atm,
It seems that PD uses OpenCL interface to hardware, when available. You still need to trick it with NVidia profile to enable Optimus.
Once enabled, you typically have several OpenCL devices available:
-CPU device
-Intel Integrated graphics
-NVidia high performance card
Every device when connected to OpenCL interface is referred as "OpenCL platform".
And then, there is a generic openCL interface (IMHO) that connects to hardware specific platforms.
Each hardware platform is responsible for providing resources for calculation in hardware specific manner;
While generic OpenCL interface controls them all by means of unified OpenCL language.
It also provides control over hardware OpenCL devices, which in turn report bak their utilization and GFlops caps.
With this architecture, generic OpenCL provides task sharing between the hardware specific OpenCL platforms which in turn, assign the assined part of the job to their resources (cores and memory).
It also provides load balancing and profiling.
With this said, IMHO, True Velocity is just another name for that.
There is little Cyberlink can do about how OpenCL performs.
Note: not nesessarily this is the best option. For example, manually disabling software (CPU_ openCL platform on my system renders it more productive (15%) with replacing execution model to CPU c++ threaded code instead of OpenCL on the main processor; while two other platforms are still OpenCL controlled.
With OpenCL enabled on all three devices, none of them will peak up to 100. For example, CPU may only stay at 65-70%.
With OpenCL platform disabled on CPU, the CPU code peaks to 99-100%, and the other OpenCL devices are also more loaded (by 15-20%) compared to purely OpenCL configuration.
Finally, when you use OpenCL, real time performance anyway poor. Just imagine how many layers of abstraction, task splitting, controlling, balancing, asynchrous computing and profiling this baby adds. Hence, if you check the box, you may notice your preview is not continous or degrade or stops suddenly.
When you disable OpenCL, you benefit from Intel realtime sycronous processing (especially with Intl optimized effects), smooth previews but high render time...
That is why I encourage you to subscribe the petition to Cyberlink^
ADD SEPARATE OPENCL CHOICE FOR PREVIEW AND RENDER
So far Cyberlink ignores this...and I have to repeatedly check and uncheck switching between the modes.
My fortune:
- CPU at 99%
- Intel HD at 55%
- NVidia card at 45%
When rendering from 4K source to FHD target full color, full effect set (Intl optimized), some enchancing (levels) and packing that into MKV container with H.265 codec at high profile and quality at 11 Mbps.
So yes.. you can do that, if you want it badly.
P.S.: 2313 seems to be some 10% slower than 2258, still have to check on that.
VOTE!!!!