welcome to the forum.

Quote ... I have GForce 840M Card and Intel i7 6600u processor... I try solutions from this topic: http://forum.cyberlink.com/forum/posts/list/45/46836.page
...

correction 27Oct2017; CL still supports GPGPU support. CyberLink Technology Hardware Acceleration but it's broke... GGRussell disabled intel gpu in the BIOS in order to kick in discrete video card. read this -> Here we go again... no option to enable NVidia high performance graphic card with Power Director 16

Quote

Quote Hi guys..After all, somehow other developers resolved this situation, if any - thur software is working with both the graphics adapters, Power Director 16 is not.

Power Director has never been compatible with Nvidia Optimus or MSHybrid mode. I went through all this over a year ago when I purchased a high end MSI laptop specifically to replace my desktop. I wanted something powerful enough to edit video. I tried ever suggestion and hack I could find and nothing worked. USers shouldn't have to figure out workings for software. I ended up just returning it and let the manufacturer know why.

I later purchased a Sager laptop (Clevo from Taiwan) which has an option in BIOS to disable MSHybrid mode. I have been very happy with it. I just boot with the nVidia GTX1060 and PD is happy with it.

plus right driver version. mine is currently 365.10 WHQL and works with PD12 & 14. hence my favorite phrases is that IF CL and nVidia was(were) married, they haven't slept in a same bed for years(after honeymoon)...

about your laptop... read this -> Lagging computer while editing and New PC for video editing; advice sought.

all else fails then -> PD11 crashes, PD16 crashes, same as it ever was



oh happy happy joy joy

PepsiMan

'garbage in garbage out' 'no bridge too far'

Yashica Electro 8 LD-6 Super 8mm
Asrock TaiChi X470, AMD R7 2700X, W7P 64, MSI GTX1060 6GB, Corsair 16GB/RAM
Dell XPS L702X i7-2860QM, W7P / W10P 64, Intel HD3000/nVidia GT 550M 1GB, Micron 16GB/RAM
Samsung Galaxy Note3/NX1

Hi

Is this defect resolved yet? I have come across quite a few incidents being logged in various forums/youtube etc but still seem to be an open issue.

It is not possible and advised to downgrade your graphics card drivers in order to get your video editing software working! Surely there is a way to get this fixed?

Thanks

Quote Hi

Is this defect resolved yet? I have come across quite a few incidents being logged in various forums/youtube etc but still seem to be an open issue.

It is not possible and advised to downgrade your graphics card drivers in order to get your video editing software working! Surely there is a way to get this fixed?

Thanks

I'm having issues as well - the worst part is, I had Powerdirector 14 doing HW acceleration fine using a GTX 1060 with latest drivers; latest Win 10 feature update failed to install, and the initial Microsoft tech support 'solution' corrupted my Windows installation, hence I had to reinstall and now can't remember the wizardry I was using to make the acceleration work

EDIT: The comfort being that I have had it work, I guess..

Quote


I'm having issues as well - the worst part is, I had Powerdirector 14 doing HW acceleration fine using a GTX 1060 with latest drivers; latest Win 10 feature update failed to install, and the initial Microsoft tech support 'solution' corrupted my Windows installation, hence I had to reinstall and now can't remember the wizardry I was using to make the acceleration work

EDIT: The comfort being that I have had it work, I guess..

I just installed a new GTX 1060 card 6GB, the only problem I find is that Power Director 16 doesn't like ASF files from Security camera systems, when you hit pause to edit the timeline jumps and skips, but this was present with the old GPU as well. Render time is also 4 times as long using PD 16 as compared to Version 13, which I kept because 16 is absolutely the worst garbage created, with no resolution to issues for over 2 years now!

Quote I'm having issues as well - the worst part is, I had Powerdirector 14 doing HW acceleration fine using a GTX 1060 with latest drivers; latest Win 10 feature update failed to install, and the initial Microsoft tech support 'solution' corrupted my Windows installation, hence I had to reinstall and now can't remember the wizardry I was using to make the acceleration work

EDIT: The comfort being that I have had it work, I guess..

Wolf_2293 I'm sorry you're having trouble. I can tell you though that there's no way PD14 will ever work with the current (v417.xx and above) nVidia drivers, because they're built for the newer version of their Software Design Kit (SDK), and PD16 and 17 had to be patched to use the new drivers.

PD14 is no longer supported, so there are only 2 ways for you to get back GPU access: go to the nVidia website and download the final version of the older style drivers (which is 411.70 from Sept 27, 2018 ); or upgrade to PD17.

EDIT: Removed incorrect reference of PD15 having support for new nVidia drivers.

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 installed a new GTX 1060 card 6GB, the only problem I find is that Power Director 16 doesn't like ASF files from Security camera systems, when you hit pause to edit the timeline jumps and skips, but this was present with the old GPU as well. Render time is also 4 times as long using PD 16 as compared to Version 13, which I kept because 16 is absolutely the worst garbage created, with no resolution to issues for over 2 years now!

BruceO: Your issue actually isn't related to this thread, so if you'd kindly review the Read Me Before Posting thread at the top of the PD16 forum index page and post the requested info in a new thread, we'd be happy to help you solve the ASF problem you're having.

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

Wolf_2293 I'm sorry you're having trouble. I can tell you though that there's no way PD14 will ever work with the current (v417.xx and above) nVidia drivers, because they're built for the newer version of their Software Design Kit (SDK), and PD15, 16 and 17 had to be patched to use the new drivers.

PD14 is no longer supported, so there are only 2 ways for you to get back GPU access: go to the nVidia website and download the final version of the older style drivers (which is 411.70 from Sept 27, 201; or upgrade to PD17.

Very sorry about that - you see, some of us aren't made of money and having to get a new version of our existing products, because a card manufacturer dare to update their drivers, is just plain dumb - much as I like the product itself, the support has been horrible; not exactly encouraging people to keep throwing money at it

Besides, I update my drivers regularly, and prior to 6th of January (before Windows died on me) my acceleration was working fine - it may be that it can't be solved from official side, but it was a user that sorted me out.

If I sound slightly displeased, while I understand a company has to make money to survive, surely you can understand that it's not within everyones ability to just buy, buy, buy...
Besides, that has been the official answer every time I've had issues with PD14: Buy latest version - I had my first issue when PD15 was released, yet I've managed to get the HW acceleration going through PD15 and 16.

Thankfully, my 1060 is more than powerful enough for my rendering needs, even without the acceleration; just a nuisance that it doesn't work and getting that same old cooperate answer is just getting tedious - smells too much of 'Help, Microsoft, my computer is on fire! - Just restart and it'll be fine'

Before dismissing this as just a heated rant, I want to clarify that I'm fully composed and in an amiable mood; as I said, I really like the product itself - it's the 'support' that's - hmmm - 'interesting'

Just to be clear, this is a user forum and I'm a fellow user, like you. Nobody on here except the moderator works for Cyberlink. This is certainly not Cyberlink technical support.

If you'd please look at my post again, you'll see that there's no reason you have to spend any money - but to get back HW acceleration you can't use the newest versions of the nVidia drivers. I spelled all of that out.

Despite your bold claims, I'm afraid that without using the 411.70 drivers, your 1060 is not being used by PD for producing in any way so the rendering that's occuring is due soley to your CPU. Many people get by without a dedicated GPU, and you're free to keep the new drivers and remain in the no-GPU group.

As for actual support, if you were to contact them, they would respond and try to get you running, even though there are 3 newer versions of PD. The thing Cyberlink doesn't do is to update older versions of software. Typically they'll support each version for two years, and in the case of the nVidia driver change, they went back 3 and patched PD15 as well.

Again, I'm giving you the ground truth about the nVidia situation, and I sincerely hope you'll find at least one of my suggestions helpful.

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, this is a user forum and I'm a fellow user, like you. Nobody on here except the moderator works for Cyberlink. This is certainly not Cyberlink technical support.

If you'd please look at my post again, you'll see that there's no reason you have to spend any money - but to get back HW acceleration you can't use the newest versions of the nVidia drivers. I spelled all of that out.

Despite your bold claims, I'm afraid that without using the 411.70 drivers, your 1060 is not being used by PD for producing in any way so the rendering that's occuring is due soley to your CPU. Many people get by without a dedicated GPU, and you're free to keep the new drivers and remain in the no-GPU group.

As for actual support, if you were to contact them, they would respond and try to get you running, even though there are 3 newer versions of PD. The thing Cyberlink doesn't do is to update older versions of software. Typically they'll support each version for two years, and in the case of the nVidia driver change, they went back 3 and patched PD15 as well.

Again, I'm giving you the ground truth about the nVidia situation, and I sincerely hope you'll find at least one of my suggestions helpful.

I see no point in taking this any further; I have absolutely no reason to lie to you, nor do I find your 'spelling out' comment appropiate - don't know how old you think I am, but I'm old enough to remember the time before there was anything remotely resembling a computer available for purchase - and I mean the 8bit era. Thanks for your advice, however little value it had - if I tell you something, it's not a 'bold claim', but a fact; I have a habit of only opening my mouth when I know what I'm talking about

Quote


I see no point in taking this any further; I have absolutely no reason to lie to you, nor do I find your 'spelling out' comment appropiate - don't know how old you think I am, but I'm old enough to remember the time before there was anything remotely resembling a computer available for purchase - and I mean the 8bit era. Thanks for your advice, however little value it had - if I tell you something, it's not a 'bold claim', but a fact; I have a habit of only opening my mouth when I know what I'm talking about

You know what? I may owe you an apology - if memory serves me, at my age your forget things , the reason I haven't had any issues with newer Nvidia drivers is due to the fact that I haven't been using parts of them for PD 14.
The fix that was suggested long ago was either relying on PD14 looking in its own folders first for .dll files, or overwriting certain .dll files in Windows; if the latter turns to be the solution, it's at own risk - need to dig out some more in the archives here, as it was from this site the advice was given.

Hope no hard feelings

Quote Wolf_2293 I'm sorry you're having trouble. I can tell you though that there's no way PD14 will ever work with the current (v417.xx and above) nVidia drivers, because they're built for the newer version of their Software Design Kit (SDK), and PD15, 16 and 17 had to be patched to use the new drivers.

Quote As for actual support, if you were to contact them, they would respond and try to get you running, even though there are 3 newer versions of PD. The thing Cyberlink doesn't do is to update older versions of software. Typically they'll support each version for two years, and in the case of the nVidia driver change, they went back 3 and patched PD15 as well.

optodata, can you provide me the link or thread for this referenced updated patched PD15 for compatibility to the post 417.xx Nvidia drivers which you reference multiple times is available? I've been unsuccessful in locating.

Jeff

Cyberlink did issue hotfix patches for the Intel drivers issue for the last 3 versions of PD: https://forum.cyberlink.com/forum/posts/list/77547.page . Perhaps it was this rather than for the nvidia driver.

Quote optodata, can you provide me the link or thread for this referenced updated patched PD15 for compatibility to the post 417.xx Nvidia drivers which you reference multiple times is available? I've been unsuccessful in locating.

Jeff

Tomasc has linked to the post I was referring to. I see that I've made a mistake in conflating the exception that CL made to go back 3 versions to patch PD15 (for the Produce Room crash) with the nVidia 416 driver issue as they were both happening at the same time.

I will go back and revise my statements. Thank you for pointing this out!

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

Tomasc has linked to the post I was referring to. I see that I've made a mistake in conflating the exception that CL made to go back 3 versions to patch PD15 (for the Produce Room crash) with the nVidia 416 driver issue as they were both happening at the same time.

I will go back and revise my statements. Thank you for pointing this out!

Okay, time for me to feel like a complete idiot; wouldn't be a first: Reinstalling the old drivers did in fact re-enable the HW acceleration, which sort of puzzles me - I rendered videos in late November last year, and am fairly sure I had updated drivers after the suggested driver version. Been a long time since I applied the fix to get things working, and I'm fairly sure it consisted of doing certain modifications that's not necessarily safe nor adviseable. As you're saying, the changes to the SDK is where the elephant roams, and I'm sure the 'fix' I used involved using parts of an older SDK version to trick PD into believing it was using older video drivers - maybe I remember wrong?

In any case, I do apologize for being an idiot, but I'd rather be wrong and have it working than be right and unable to use the substantially faster rendering

Quote ... Reinstalling the old drivers did in fact re-enable the HW acceleration, which sort of puzzles me - I rendered videos in late November last year, and am fairly sure I had updated drivers after the suggested driver version.

The first release that broke PD's HW access was 416.16, released on Oct 4, and as long as you (or your system, on its own) hadn't updated that driver, you would have been able to produce using your 1060 in November. It does make sense that your new Windows installation would have brought in the latest nVida drivers, which aren't compatible with PD14.

Quote In any case, I do apologize for being an idiot, but I'd rather be wrong and have it working than be right and unable to use the substantially faster rendering

Apology accepted, and I'm fully in agreement with you that the goal here is to get things working at their best. I also made some misstatements in my earlier post, and I'm happy to go back and set the record straight whenever I've made mistakes.

Happy editing

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°

Try different version of opencl.dll, this one works for me. This version may not working for you, try more. HTH.

Moderation Note: Active link to dll site removed.