Quote:
Thanks for the input Jeff- noted and updated.
Rob
If one understands the details of ticking a option, I think it's easier to understand if it will help a user with his particular timeline. Unfortunately, CL to me does a very poor job of explaining what they really implemented and applicability, the sales dept takes over and you just get fluff. The manual is terrible to aid resolution. End users need to try and resolve how it affects them. The Preferences OpenCL to me is what really what enables the use of the GPU as a general processor (GPGPU). From what I have seen, the CL wording in preferences is exactly that, "video effect". I think its all the same as what was presented here in the multiGPGPU.pdf
http://forum.cyberlink.com/forum/posts/list/25826.page
The attached pic shows the effects of user selections and what happens to load on various devices. It uses a basic timeline of the sample file copied on the timeline several times, trimmed to 2min, and then produced as a 1920x1080, 24Mbps file to have something to work with that is more typical of users video file properties. The first and last 2min clips have the Gaussian Blur (accelerated) or the TV Wall (non-accelerated) effects applied. The Gaussian Blur was selected as computationally it's a load. The three 2min chunks make it easy to identify in the load chart.
Summary of chart:
Run 1: Basic CPU and HD4000 HA encoding. Notice the high CPU load during the encoding of the first and last 2 min regions. Gaussian Blur puts on a significant load that is CPU even though the clip is HA in Produce.
Run 2: This run essentially shows the effect when OpenCL is activate in preferences and a accelerated effect is used in the timeline. During the encoding of the first and last 2 min of the timeline I get all 3 of my PU's active, in the middle 2min clip, I simply get the HD4000 and CPU active. Again it was HA in Produce.
Run 3 and 4: For a non accelerated effect in the timeline, OpenCL used in preferences has no effect, both runs match each other.
The other note of interest, the load in the middle 2 min section of all 4 runs is essentially identical as it should be. For this unmodified section in all 4 runs the same exact processing by the CPU (25%) and HD4000 (49%) needs to be done.
The OpenCL option in preferences can even be used by those that like CPU encoding, if ticked, any accelerated effects used in the timeline will get the GPGPU features provided by OpenCL. So if the user has a AMD CPU and a Nvidia GTX470, the GTX470 GPU will be used as a general processor to aid encoding the effects in the timeline that are accelerated. The GPU will be used as a general processor (GPGPU).
The above is how I understand the current OpenCL implementation in PD11 and PD12. Can or could it do more, based on what I know, certainly, maybe CL will expose more in general encoding capability in future releases.
Jeff
|
Filename |
OpenCL3.png |
|
Description |
OpenCL effects |
Filesize |
142 Kbytes
|
Downloaded: |
101 time(s) |
This message was edited 1 time. Last update was at Mar 03. 2014 20:35