Announcement: Our new CyberLink Feedback Forum has arrived! Please transfer to our new forum to provide your feedback or to start a new discussion. The content on this CyberLink Community forum is now read only, but will continue to be available as a user resource. Thanks!
CyberLink Community Forum
where the experts meet
| Advanced Search >
PowerDirector Hardware Acceleration and export profile fixes
JackJ [Avatar]
Newbie Joined: Apr 28, 2019 12:18 Messages: 2 Offline
[Post New]
These 2 issues come up often - seems like a sticky would be useful laughing

I have had both of these issues a number of times over the years.

=======================
I don't remember the original post for this, but I've used this method several times over the years... PD12-PD16

....here it is, thanks JL_JL
https://forum.cyberlink.com/forum/posts/list/47025.page#post_box_244166

---
When the encoding processes has an abnormal termination, a previous produce profile may become unavailable/corrupted.
What I think occurs is that if PD for some reason had some type of unique encoding error for a particular format
and it sets a flag in windows registry.
Once done, anytime one try’s the same task, you get this perhaps unwarranted error.
If your system should be capable of producing the format in question, one needs to reset the windows registry key back to 0
from the imposed value of 1 for that particular format.
Edit windows registry at your own risk!
With regedit migrate to HKEY_CURRENT_USER\Software\Cyberlink\CES_FunctionLogger\Data and see if any values are still set to 1 with PD not loaded.
PD13 still works as it uses a different key value vs PD14 for XAVC-S at least for Nvidia. All those values should essentially be zero.
For me with Nvidia PD13 uses value:
NVKEPLER_UNKNOWN_FMT[H264,AAC]_3840x2160p
while PD14 uses:
NVKEPLER_MPEG4_XAVC[H264,AAC]_3840x2160p
for the same XAVC S 3840x2160/60p 60Mbps hence my guess the reason PD13 still works.

==========================

Thanks to browniee112 for this fix.
Original post is here:
https://forum.cyberlink.com/forum/posts/list/64906.page


If hardware acceleration checkbox is not available for production though it should be:
(I just fixed this again on PD 16)

HOW TO:
1) (original suggestion, not required) uninstall and reinstall powerdirector
2) (suggested) update your nvidia driver
3) Downlaod Nvidia Inspector (http://www.guru3d.com/files-details/nvidia-inspector-download.html)
4) Open nvidia inspector and click on the screwdriver icon near the "driver version" label
5) In the dropdown menu, choose "Cyberlink Power Director" (exactly)
6) Set this property:
Do not display this profile in the Control Panel = CPL_HIDDEN_PROFILE_DISABLED
Enable application for Optimus = SHIM_RENDERING_MODE_ENABLE
Optimus flags for enabled applications = SHIM_MCCOMPAT_OVERRIDE_BIT
Shim Rendering Mode Options per application for Optimus = SHIM_RENDERING_OPTIONS_DEFAULT_RENDERING_MODE
7) Click on Apply changes and close Nvidia Inspector
Open Powerdirector
9) Go to preferences and then hardware acceleration
10) Check "use opencl" and "use hardware decoding" (or something similar, i don't have english powerdirector;
if you can't check those option then something went wrong with the previous steps)
11) restart Powerdirector

This message was edited 3 times. Last update was at Apr 28. 2019 21:04

Powered by JForum 2.1.8 © JForum Team